Alan Lloyd
Datacraft - Australia

========

Addressing - Goals

  o  To provide harmonisation between ISO NSAPs and IPv4 and
     IPv6 addresses.

  o  To permit ISO to administer some of the IP address block.

  o  To provide a network design approach that ENABLES address
     convergence and migration to IPv6.

========

Addressing - Requirements

  o  To enable 20 byte NSAPs to be carried in IPv6 without
     squashing into 16.

  o  To have compatible address forms in IPv6 and CLNP networks.

  o  To have IPv6 addresses carried as ISO NSAPs.

========

Addressing - Mechanisms

  o  20 byte NSAPs in IPv6.

     -  Carried with a FP of NSAP and the IPv6 address 
        format = length + NSAP address

     -  Where length <= 14, NSAP in remaining IPv6 14 bytes.

     -  Where length > 14, NSAP fragment in options (e.g., end
        to end).

========

Addressing - Mechanisms

  o  IPv6 as a NSAP for CLNP.

     -  Carried with an BSI assigned ICD for ISOC and supplemented
        with the IPv6 16-byte address.

========

Addressing - Mechanisms

  o  Internet NSAPs.

     -  Compatible in both the CLNP and Internet environment (i.e.,
        top byte (FP and AFI) are the same).

     -  Implemented as block of IPv6 addresses assigned to ISO.

     -  Two NSAP forms (I) = Internet.

        o  ICD(I) 16 bytes
        
        o  DCC(I) 16 bytes

========

Not Recommended

  o  Nested addresses.  Don't.

  o  E.g., do not put a native IPv6 address into a 16-byte NSAP
     with an Internet ICD.

========

Migration - Ideas

  o  Consolidate 20 byte NSAPs into Internet NSAPS.

  o  "Nationalise" IP4 addresses via gateways to the IPv6 BiggerNet.

  o  Change gatewayed NatlP4 addresses to National IPv6 forms.

========

Addressing - Actions

  o  IETF - agree to option for NSAP fragment.

  o  IANA - agree to an ISO address block.

  o  ISO - agree to Internet NSAP forms.

========

Please Agree

Then we can get on with the IP6 - Bigger Internet migration plan.

Thank you.