---
oid: "1.3.6.1.2.1.10.166.4.1.3.2.1.5"
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) mplsLdpPeerTransportAddr(5)}"
description: "mplsLdpPeerTransportAddr 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.5`

```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) mplsLdpPeerTransportAddr(5)}
```

### Description

```asn1
mplsLdpPeerTransportAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Internet address advertised by the peer
in the Hello Message or the Hello source address.
The type of this address is specified by the
value of the mplsLdpPeerTransportAddrType
object."
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)
