1998
DOI: 10.17487/rfc2332
|View full text |Cite
|
Sign up to set email alerts
|

NBMA Next Hop Resolution Protocol (NHRP)

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
54
0
1

Year Published

1998
1998
2003
2003

Publication Types

Select...
3
3
2

Relationship

2
6

Authors

Journals

citations
Cited by 91 publications
(55 citation statements)
references
References 12 publications
0
54
0
1
Order By: Relevance
“…The NHRP Protocol, RFC 2332 [17], Section 5.2.4.4 discusses security. There is an authentication option which should be utilized to authenticate the source and also provide data integrity to the NHRP payload.…”
Section: Securitymentioning
confidence: 99%
See 2 more Smart Citations
“…The NHRP Protocol, RFC 2332 [17], Section 5.2.4.4 discusses security. There is an authentication option which should be utilized to authenticate the source and also provide data integrity to the NHRP payload.…”
Section: Securitymentioning
confidence: 99%
“…In particular, it describes managed objects for the Next Hop Resolution Protocol (NHRP) as defined in RFC 2332 [17].…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation
“…All NHSs belonging to a Logical IP Subnet (LIS) [1] are said to belong to a Server Group (SG). An SG is identified by, not surprisingly, its SGID which is contained in a field in all SCSP packets.…”
Section: Overviewmentioning
confidence: 99%
“…Using different mar$afn (Address Family) values in the fixed header of MARS control messages allows MARS entities to indicate they are carrying other types of NBMA addresses (as done in NHRP [3]). As for NHRP, the interpretation of the 'sub-address' fields shall be in the context of the address family selected (which means it will often simply be null).…”
Section: Generalising the Mars Modelmentioning
confidence: 99%