…tocol families supported by the SSH implementation on loopback addresses only ([RFC3330] and [RFC3513]). o "127.0.0.1" and "::1" indicate listening on the loopback interfaces for IPv4 and IPv6, respectively. Note that the client can still filter connections based on information p…

…he document is structured by address types. The document format is similar to [ RFC3330 ]. Some tips about filtering are given, but are not mandatory to implement. The addresses listed in this document must not be hard-coded into implementations. 2 . Address Blocks 2.1 . Node-Sco…

…ocol families supported by the SSH implementation on loopback addresses only ([ RFC3330 ] and [ RFC3513 ]). o "127.0.0.1" and "::1" indicate listening on the loopback interfaces for IPv4 and IPv6, respectively. Note that the client can still filter connections based on informatio…

…e past. However, this block did not appear in the list of special prefixes in [ RFC3330 ] or its successors, and the block is therefore not reserved for any special purpose. The block can be used for regular address assignments with caution. 6 . Security Considerations This docum…

…The document is structured by address types. The document format is similar to [RFC3330]. Some tips about filtering are given, but are not mandatory to implement. The addresses listed in this document must not be hard-coded into implementations. 2. Address Blocks 2.1. Node-Scoped…

…he document is structured by address types. The document format is similar to [ RFC3330 ]. Some tips about filtering are given, but are not mandatory to implement. The addresses listed in this document must not be hard-coded into implementations. 2 . Address Blocks 2.1 . Node-Sco…

…e past. However, this block did not appear in the list of special prefixes in [ RFC3330 ] or its successors, and the block is therefore not reserved for any special purpose. The block can be used for regular address assignments with caution. 6 . Security Considerations This docum…