Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"mplsTeP2mpTunnelDestSrcSubGroupOrigin",
"OBJECT-TYPE",
"SYNTAX",
"InetAddress",
"(",
"SIZE",
"(",
"0",
"|",
"4",
"|",
"16",
")",
")",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"The TE Router ID (reachable and stable IP address) of the originator of the P2MP sub-group as received on a Path message by a transit or egress LSR. This object is interpreted in the context of mplsTeP2mpTunnelDestSrcSubGroupOriginType. The value of the sub-group originator used on outgoing Path messages is found in mplsTeP2mpTunnelDestSubGroupOrigin and is copied from this object unless this LSR is responsible for changing the sub-group ID. At an ingress LSR there is no received Path message. mplsTeP2mpTunnelDestSrcSubGroupOriginType should return unknown(0), and this object should return a zero-length string.\"",
"REFERENCE",
"\"RFC 4875 - Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs), R. Aggarwal, D. Papadimitriou, and S. Yasukawa, May 2007.\"",
"::=",
"{",
"mplsTeP2mpTunnelDestEntry",
"2",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"InetAddress",
[
"octetStringSubType",
[
[
0
],
[
4
],
[
16
]
]
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The TE Router ID (reachable and stable IP address) of the originator of the P2MP sub-group as received on a Path message by a transit or egress LSR. This object is interpreted in the context of mplsTeP2mpTunnelDestSrcSubGroupOriginType. The value of the sub-group originator used on outgoing Path messages is found in mplsTeP2mpTunnelDestSubGroupOrigin and is copied from this object unless this LSR is responsible for changing the sub-group ID. At an ingress LSR there is no received Path message. mplsTeP2mpTunnelDestSrcSubGroupOriginType should return unknown(0), and this object should return a zero-length string."
],
[
"REFERENCE",
"RFC 4875 - Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs), R. Aggarwal, D. Papadimitriou, and S. Yasukawa, May 2007."
],
null,
null,
null
]
}