---
oid: "1.3.6.1.2.1.10.166.4.1.3.2.1.4"
asn1-notation: "{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) transmission(10) mplsStdMIB(166) mplsLdpStdMIB(4) mplsLdpObjects(1) mplsLdpSessionObjects(3) mplsLdpPeerTable(2) mplsLdpPeerEntry(1) mplsLdpPeerTransportAddrType(4)}"
description: "mplsLdpPeerTransportAddrType OBJECT-TYPE"
classification: "MIB object for network management"
last-modified: "2020-02-07"
---

## OID : `1.3.6.1.2.1.10.166.4.1.3.2.1.4`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) transmission(10) mplsStdMIB(166) mplsLdpStdMIB(4) mplsLdpObjects(1) mplsLdpSessionObjects(3) mplsLdpPeerTable(2) mplsLdpPeerEntry(1) mplsLdpPeerTransportAddrType(4)}
```

### Description

```asn1
mplsLdpPeerTransportAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of the Internet address for the
mplsLdpPeerTransportAddr object. The LDP
specification describes this as being either
an IPv4 Transport Address or IPv6 Transport
Address which is used in opening the LDP session's
TCP connection, or if the optional TLV is not
present, then this is the IPv4/IPv6 source
address for the UPD packet carrying the Hellos.
This object specifies how the value of the
mplsLdpPeerTransportAddr object should be
interpreted."
REFERENCE
"RFC3036, LDP Specification, Section 2.5.2
Transport Connection Establishment and
Section 3.5.2.1 Hello Message Procedures."
```

**Classification**: MIB object for network management

### Supplementary information

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

### Child OIDs

No child OID

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