…, "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 3. Relationship to Other Standards The method specified in this document is orthogonal to the use of temporary addresses [RFC4941], since it is meant to improve the security and privacy prop…

…ative except sections explicitly marked as non-normative, examples, and notes. [RFC2119] Examples in this specification are introduced with the words “for example” or are set apart from the normative text with class="example" , like this: This is an example of an informative exam…

… and SHOULD NOT in this document are to be interpreted as described in BCP 14 [ RFC2119 ] [ RFC8174 ] when, and only when, they appear in all capitals, as shown here. This document contains examples that contain JSON and JSON-LD content. Some of these examples contain characters …

…ative except sections explicitly marked as non-normative, examples, and notes. [RFC2119] Examples in this specification are introduced with the words "for example" or are set apart from the normative text with class="example" , like this: This is an example of an informative exam…

…, "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 3. Protocol Updates Discarding the NCE after three packets spaced one second apart is only needed when an alternative neighbor is available, such as an additional default router or discardin…

…ative except sections explicitly marked as non-normative, examples, and notes. [RFC2119] Examples in this specification are introduced with the words “for example” or are set apart from the normative text with class="example" , like this: This is an example of an informative exam…

…nd "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [ RFC2119 ]. 2 . The ':seconds' Parameter The purpose of the ":seconds" parameter is to specify the minimum time interval (in seconds) between consecutive auto-replies to a given sender. The ":seconds" …

… "MAY", and "OPTIONAL" in this document are to be interpreted as described in [ RFC2119 ]. 3 . EdDSA Algorithm EdDSA is a digital signature system with 11 parameters. The generic EdDSA digital signature system with its 11 input parameters is not intended to be implemented directl…

…nd "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [ RFC2119 ]. 2 . BCP 47 Required Information Language tags, as defined by [ BCP47 ], are useful for identifying the language of content. They are also used as locale identifiers (or can be mapped to loc…

…, "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 2. Notation The notation in this document includes: c ciphertext representative, an integer between 0 and n-1 C ciphertext, an octet string d RSA private exponent d_i additional factor r_i's…

… "MAY", and "OPTIONAL" in this document are to be interpreted as described in [ RFC2119 ]. 3 . Terminology In addition to the terminology defined in [ RFC3315 ], [ RFC3633 ], and [ RFC7227 ], the following terminology is used in this document: Identity Association (IA): Throughou…

… "MAY", and "OPTIONAL" in this document are to be interpreted as described in [ RFC2119 ]. The data types boolean, byte, uint32, uint64, string, and mpint are to be interpreted in this document as described in [ RFC4251 ]. The size of a set of elliptic curve domain parameters on …

…ST , and SHOULD in this document are to be interpreted as described in BCP 14 [ RFC2119 ] [ RFC8174 ] when, and only when, they appear in all capitals, as shown here. 7. Acknowledgments The editors would like to thank Chris Poole, Cyril Concolato, David Singer, Jer Noble, Jerry S…

…nd " OPTIONAL " in this document are to be interpreted as described in BCP 14 [ RFC2119 ] [ RFC8174 ] when, and only when, they appear in all capitals, as shown here. ¶ According to the allocation and assignment data published by the Regional Internet Registries (RIRs) (see [ NRO…

…nd " OPTIONAL " in this document are to be interpreted as described in BCP 14 [ RFC2119 ] [ RFC8174 ] when, and only when, they appear in all capitals, as shown here. ¶ [ RFC8754 ] defines the Segment List of the SRH as a contiguous array of 128-bit IPv6 addresses; further, it st…