---
oid: "1.3.6.1.2.1.10.246.1.2.1.12"
short-description: "pwID OBJECT-TYPE"
last-modified: "2020-01-16"
parent-oid: "1.3.6.1.2.1.10.246.1.2.1"
---

## OID: `1.3.6.1.2.1.10.246.1.2.1.12`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) transmission(10) pwStdMIB(246) pwObjects(1) pwTable(2) pwEntry(1) pwID(12)}
```

### Description

```asn1
pwID OBJECT-TYPE
SYNTAX PwIDType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Pseudowire identifier.
If the pwOwner object is 'pwIdFecSignaling' or
'l2tpControlProtocol', then this object is signaled in the
outgoing PW ID field within the 'Virtual Circuit FEC
Element'. For other values of pwOwner, this object is not
signaled and it MAY be set to zero.
For implementations that support the pwIndexMappingTable,
a non-zero value is RECOMMENDED, even if this
identifier is not signaled. This is so that reverse
mappings can be provided by pwIndexMappingTable and
pwPeerMappingTable. It is therefore RECOMMENDED that the
value of this pwID be unique (or if pwPeerAddrType is not
'unknown', at least [pwType, pwID, pwPeerAddrType, pwPeerAddr]
is unique.)"
REFERENCE
"Martini, et al, 'Pseudowire Setup and Maintenance using
the Label Distribution Protocol', RFC 4447."
```

**Classification:** MIB object for network management

### Supplementary information

Automatically extracted from IETF [RFC 5601](https://www.rfc-editor.org/rfc/rfc5601.html).

### Child OIDs

No child OID

### Terms of Use

[Terms of use](https://oid-base.com/disclaimer.htm.md)

**Note to implementers:**: The OID repository is constantly updated but does not necessarily store the latest (or most accurate) version of this formal description. For an implementation, it is recommended to search the web for a more recent description. If this is the case, please update the above description.