2011
DOI: 10.17487/rfc6233
|View full text |Cite
|
Sign up to set email alerts
|

IS-IS Registry Extension for Purges

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
3
0

Year Published

2011
2011
2017
2017

Publication Types

Select...
3

Relationship

3
0

Authors

Journals

citations
Cited by 3 publications
(3 citation statements)
references
References 4 publications
0
3
0
Order By: Relevance
“…When an LSP purge is initiated, the IID-TLV MUST be retained, but the remainder of the body of the LSP SHOULD be removed. The purge procedure is described in [RFC6233] and [RFC6232].…”
Section: Instance Identifier Tlvmentioning
confidence: 99%
“…When an LSP purge is initiated, the IID-TLV MUST be retained, but the remainder of the body of the LSP SHOULD be removed. The purge procedure is described in [RFC6233] and [RFC6232].…”
Section: Instance Identifier Tlvmentioning
confidence: 99%
“…More interactions between the POI TLV, the Dynamic hostname TLV, and the Authentication TLV are described in [RFC6233].…”
Section: Security Considerationsmentioning
confidence: 99%
“…Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. The "IS-IS TLV Codepoints" registry was created by [RFC3563] and extended by [RFC6233]. The assignment policy for the registry is "Expert Review" as defined in [RFC5226].…”
mentioning
confidence: 99%