OID repository
OID Repository
https://oid-base.com
Display OID:
 
Action itemiso(1) Action itemidentified-organization(3) Action itemdod(6) Action iteminternet(1) Action itemprivate(4) Action itementerprise(1) Action item2011 Action itemhuaweiMgmt(5) Action itemhwDatacomm(25) Action itemhwMcast(149) Action itemhwIpMcastMib(1) Action itemhwIpMcastMibObjects(1) Action itemhwIpMcast(1) Action itemhwIpMcastBoundaryTable(7) Action itemhwIpMcastBoundaryEntry(1)   Navigating the OID tree
hwIpMcastBoundaryAddress(3)
 
Separation line
 
OID description

   
OID: (ASN.1 notation)
(dot notation)
(OID-IRI notation)

Description:

hwIpMcastBoundaryAddress OBJECT-TYPE
SYNTAX InetAddress (SIZE (0|4|8|16|20))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The group address which, when combined with the
corresponding value of hwIpMcastBoundaryAddressPrefixLength,
identifies the group range for which the scoped boundary
exists. Scoped IPv4 multicast address ranges must be
prefixed by 239.0.0.0/4. Scoped IPv6 multicast address
ranges are FF0x::/16, where x is a valid RFC 4291 multicast
scope.
An IPv6 address prefixed by FF1x::/16 is a non-permanently-
assigned address. An IPv6 address prefixed by FF3x::/16 is
a unicast-prefix-based multicast addresses. A zone boundary
for FF0x::/16 implies an identical boundary for these other
prefixes. No separate FF1x::/16 or FF3x::/16 entries exist
in this table.
This address object is only significant up to
hwIpMcastBoundaryAddressPrefixLength bits. The remainder of
the address bits are zero. This is especially important for
this index field, which is part of the index of this entry.
Any non-zero bits would signify an entirely different
entry.
For addresses of type ipv4z or ipv6z, the appended zone
index is significant even though it lies beyond the prefix
length. Zone index zero is not valid in this table."
REFERENCE
"RFC 2365, RFC 3306 section 4, RFC 4291 section 2.7"


 
Short URL for this page:

Disclaimer: The owner of this site does not warrant or assume any liability or responsibility for the accuracy, completeness, or usefulness of any information available on this page (for more information, please read the complete disclaimer).
All rights reserved © 2007-2024
Parent OID: hwIpMcastBoundaryEntry(1) First sibling OID: hwIpMcastBoundaryIfIndex(1) Previous sibling OID: hwIpMcastBoundaryAddressType(2) Next sibling OID: hwIpMcastBoundaryAddressPrefixLength(4) Last sibling OID: hwIpMcastBoundaryStorageType(9)
Separation line
OID helper Webmaster Bullet 3 May 2024 Bullet Page top