Hello, all. After some guidance from Carlos and Wassim, I am posting this message here.
My name is Saleem Bhatti, and I work on ILNP: RFCs 6740-6748, all "Experimental" status. ILNP is an Identifier-Locator, end-to-end addressing architecture that uses IPv6 directly. Lots more information on ILNP can be found at: https://ilnp.cs.st-andrews.ac.uk/ I have some recent updates to the original ILNP RFCs, based on some years of implementation work here at the University of St Andrews (Scotland, UK), plus testing / experiments at IETF Hackathon events over the last couple of years. Links to the new drafts are below. I would be grateful for your help in progressing these new drafts. I am not looking to progress these for "Standards" status, just to have them available as "Experimental" status, as are the current RFCs for ILNP. For now, I have submitted the drafts on the "Independent" track, so that they are visible. The original RFCs were progressed through the Routing Research Group (RRG) of the IRTF, which has now concluded. The drafts linked below are actually to do with addressing and IPv6 (rather than routing), so I hope that they are of interest to this community. I will request a slot to present these documents to you all during an intarea session at IETF126/Vienna in July, but I am happy to receive any comments or queries by email in the meantime. Also, I will be at RIPE92/Edinburgh during the coming week (18-22 May), so I would be delighted to talk to anyone if you are in Edinburgh. And, of course, I will also be at IETF126/Vienna, including the Hackathon on 18-19 July with ILNP, where I will be happy to have a chat with anyone during that week. Cheers, --/Saleem # ILNP textual representations https://datatracker.ietf.org/doc/draft-bhatti-ilnp-textual-representations/ ## Abstract The Identifier Locator Network Protocol (ILNP) for IPv6 is described in Experimental RFCs 6740-6744. This document describes how values for ILNP data-types SHOULD be represented in textual form. These data-types are: the Locator (L64), the Node Identifier (NID), and the Identifier-Locator Vector (I-LV). The notation for the textual representation is defined formally. Use-cases are provided as examples of real world usage. This document updates RFC6740, RFC6741, RFC6742. # ILNP usage by IPv6 applications https://datatracker.ietf.org/doc/draft-bhatti-ilnp-ip6-apps/ ## Abstract The Identifier Locator Network Protocol (ILNP) for IPv6 is described in Experimental RFCs 6740-6744. ILNP uses a different architecture to IPv6 but is implemented to work with IPv6. This document describes how unmodified IPv6 applications running on an ILNP-capable node can make use of ILNP. This document updates RFC6740, RFC6741, RFC6748. # ILNP addressing using Preference values https://datatracker.ietf.org/doc/draft-bhatti-ilnp-preference/ ## Abstract The Identifier Locator Network Protocol (ILNP) for IPv6 is described in Experimental RFCs 6740-6744. This document clarifies how addressing in ILNP makes use of Preference values with Locator (L64) and Node Identifier (NID) values. This includes the way that Preference values are used for forming Identifier-Locator Vector (I-LV) values, and selecting I-LVs for use. This document updates RFC6740, RFC6741, RFC6742, RFC6748. # Use of the ILNP Nonce Destination Option Header https://datatracker.ietf.org/doc/draft-bhatti-ilnp-nonce/ ## Abstract The Identifier Locator Network Protocol (ILNP) for IPv6 is described in Experimental RFCs 6740-6744. ILNP packets for IPv6 are distinguished from normal IPv6 packets by the presence of the Nonce Destination Option Header (aka Nonce Header), as defined in RFC6744. This document clarifies the use of the Nonce Header for ILNP. This document updates RFC6740, RFC6741, RFC6744. _______________________________________________ Int-area mailing list -- [email protected] To unsubscribe send an email to [email protected]
