SHIM6 WG                                                     E. Nordmark
Internet-Draft                                          Sun Microsystems
Expires: March 31, 5, 2006                                    September 27, 2005

                   Level 3 multihoming shim protocol
                     draft-ietf-shim6-proto-00.txt
                     draft-ietf-shim6-proto-01.txt

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on March 31, 5, 2006.

Copyright Notice

   Copyright (C) The Internet Society (2005).

Abstract

   The SHIM6 working group is exploring a layer 3 shim approach for
   providing locator agility below the transport protocols, so that
   multihoming can be provided for IPv6 with failover and load spreading
   properties, without assuming that a multihomed site will have a
   provider independent IPv6 address which is announced in the global
   IPv6 routing table.  The hosts in a site which has multiple provider
   allocated IPv6 address prefixes, will use the shim6 protocol
   specified in this document to setup state with peer hosts, so that
   the state can later be used to failover to a different locator pair,
   should the original one stop working.

   This document picks a particular approach to such a protocol and
   tries to flush out a bunch of details, with the hope that the WG can
   better understand the details in this proposal as well as discovering
   and understanding alternative designs that might be better.  Thus
   this proposal is my no means cast in stone as the direction; quite to
   the contrary it is a depth first exploration of the design space.

Table of Contents

   1.   Introduction . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.1  Placement of the shim  Goals  . . . . . . . . . . . . . . . . . . .   4
   2.   Terminology . . . . . . .   4
     1.2  Non-Goals  . . . . . . . . . . . . . . . . .   5
     2.1  Definitions . . . . . . .   5
     1.3  Locators as Upper-layer Identifiers  . . . . . . . . . . .   5
     1.4  IP Multicast . . . . .   5
     2.2  Notational Conventions . . . . . . . . . . . . . . . . . .   6
   3.   Assumptions
     1.5  Renumbering Implications . . . . . . . . . . . . . . . . .   6
     1.6  Placement of the shim  . . . . . . .   7
   4.   Protocol Overview . . . . . . . . . . .   7
   2.   Terminology  . . . . . . . . . . . .   8
     4.1  Context Tags and Use of Flow Label . . . . . . . . . . . .   9
     4.2  Protocol type overloading
     2.1  Definitions  . . . . . . . . . . . . . . . .  10
     4.3  Securing shim6 . . . . . . .   9
     2.2  Notational Conventions . . . . . . . . . . . . . . .  11
     4.4  Overview of Shim Control Messages . . .  10
   3.   Assumptions  . . . . . . . . .  11
   5.   Message Formats . . . . . . . . . . . . . . .  11
   4.   Protocol Overview  . . . . . . .  14
     5.1  Common Shim6 header . . . . . . . . . . . . . .  11
     4.1  Context Tags . . . . .  14
     5.2  I1 Message Format . . . . . . . . . . . . . . . . . .  13
     4.2  Securing shim6 . .  15
     5.3  R1 Message Format . . . . . . . . . . . . . . . . . . . .  16
     5.4  I2 Message Format  14
     4.3  Overview of Shim Control Messages  . . . . . . . . . . . .  14
   5.   Message Formats  . . . . . . . .  17
     5.5  R2 Message Format . . . . . . . . . . . . . .  15
     5.1  Payload Message Format . . . . . .  19
     5.6  No Context Error Message Format . . . . . . . . . . . .  15
     5.2  Common Shim6 Control header  .  20
     5.7  Locator List Update Message Format . . . . . . . . . . . .  21
     5.8  Locator List Update Acknowledgement . .  16
     5.3  I1 Message Format  . . . .  22
     5.9  Rehome Request Message Format . . . . . . . . . . . . . .  23
     5.10   Rehome Acknowledgement . .  17
     5.4  R1 Message Format  . . . . . . . . .  23
     5.11   Reachability Probe Message Format . . . . . . . . . . .  23
     5.12   Reachability Probe Reply  18
     5.5  I2 Message Format  . . . . . . . .  24
     5.13   Payload Message Format . . . . . . . . . . . . .  19
     5.6  R2 Message Format  . . . .  25
     5.14   Keepalive Message Format . . . . . . . . . . . . . . . .  26
     5.15   Locator Pair Test  21
     5.7  No Context Error Message Format  . . . . . . . . . . . .  27
     5.16   Locator Pair Test Reply .  22
     5.8  Update Request Message Format  . . . . . . . . .  28
     5.17   Context Locator Pair Explore Message Format . . . . .  23
     5.9  Update Acknowledgement Message Format  .  29
   6.   Option Formats . . . . . . . . .  24
     5.10   Reachability Probe Message Format  . . . . . . . . . . .  24
     5.11   Reachability Reply Message Format  . . .  31
     6.1  Validator Option Format . . . . . . . .  25
     5.12   Keepalive Message Format . . . . . . . . .  32
     6.2 . . . . . . .  26
     5.13   Context Locator List Option Pair Explore Message Format  . . . . . .  27
     5.14   Option Formats . . . . . . . . . .  32
     6.3 . . . . . . . . . . .  28
       5.14.1   Validator Option Format  . . . . . . . . . . . . . .  29
       5.14.2   Locator Preferences List Option Format . . . . . . . . . . . .  33
     6.4  CGA Parameter Data Structure .  30
       5.14.3   Locator Preferences Option Format  . . . . . . . .  34
     6.5 .  31
       5.14.4   CGA Signature Parameter Data Structure Option Format . . . . .  32
       5.14.5   CGA Signature Option Format  . . . . . . . . . . . .  35
     6.6  33
       5.14.6   ULID Pair Option Format  . . . . . . . . . . . . . . . . .  35
     6.7  33
       5.14.7   Packet In Error Option Format  . . . . . . . . . . . . . .  36
     6.8  34
       5.14.8   Explorer Results Option Format . . . . . . . . . . . . . .  36
   7.  34
   6.   Conceptual Model of a Host . . . . . . . . . . . . . . . . .  38
     7.1  35
     6.1  Conceptual Data Structures . . . . . . . . . . . . . . . .  38
   8.  36
   7.   Establishing Host Pair Contexts  . . . . . . . . . . . . . .  40
     8.1  Sending I1 messages  36
     7.1  Normal context establishment . . . . . . . . . . . . . . .  37
     7.2  Concurrent context establishment . . . . . . .  40
     8.2  Receiving I1 messages . . . . . .  37
     7.3  Context recovery . . . . . . . . . . . .  40
     8.3  Receiving R1 . . . . . . . . .  38
     7.4  Context confusion  . . . . . . . . . . . . . . . . . . . .  39
     7.5  Sending I1 messages  . . . . . . . . . . . . . . . . . . .  40
     8.4  Retransmitting
     7.6  Receiving I1 messages  . . . . . . . . . . . . . . . . . .  40
     8.5
     7.7  Receiving I2 R1 messages  . . . . . . . . . . . . . . . . . .  40
     8.6  41
     7.8  Retransmitting I2 messages . . . . . . . . . . . . . . . .  40
     8.7  Concurrent context establishment  41
     7.9  Receiving I2 messages  . . . . . . . . . . . . .  40
   9. . . . . .  41
     7.10   Receiving R2 messages  . . . . . . . . . . . . . . . . .  42
   8.   No Such Content Errors . . . . . . . . . . . . . . . . . . .  41
   10.  42
   9.   Handling ICMP Error Messages . . . . . . . . . . . . . . . .  42
   11.  Taredown
   10.  Teardown of the Host Pair Context  . . . . . . . . . . . . .  43
   12.
   11.  Updating the Locator Pairs . . . . . . . . . . . . . . . . .  44
   13.  43
   12.  Various Probe Mechanisms . . . . . . . . . . . . . . . . . .  45
   14.  43
   13.  Rehoming to a Different Locator Pair . . . . . . . . . . . .  46
   15.  43
   14.  Payload Packets before a Switch  . . . . . . . . . . . . . .  47
   16.  43
   15.  Payload Packets after a Switch . . . . . . . . . . . . . . .  48
   17.  44
   16.  Open Issues  . . . . . . . . . . . . . . . . . . . . . . . .  50
   18.  45
   17.  Design Alternatives  . . . . . . . . . . . . . . . . . . . .  52
     18.1  46
     17.1   State Cleanup  . . . . . . . . . . . . . . . . . . . . .  52
     18.2   Not Overloading the Flow Label  46
     17.2   Detecting Context Loss . . . . . . . . . . . . .  52
     18.3   Detecting Context Loss . . . .  46
   18.  Implications Elsewhere . . . . . . . . . . . . . . . .  53
   19.  Implications Elsewhere . . .  47
   19.  Security Considerations  . . . . . . . . . . . . . . . . . .  55  48
   20.  Security  IANA Considerations  . . . . . . . . . . . . . . . . . .  57 . .  48
   21.  Acknowledgements  Change Log . . . . . . . . . . . . . . . . . . . . . .  58 . . .  49
   22.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . .  49
   23.  References . . . . . . . . . . . . . . . . . . . . . . . . .  59
     22.1  49
     23.1   Normative References . . . . . . . . . . . . . . . . . .  59
     22.2  49
     23.2   Informative References . . . . . . . . . . . . . . . . .  59  50
        Author's Address . . . . . . . . . . . . . . . . . . . . . .  60  51
        Intellectual Property and Copyright Statements . . . . . . .  61  52

1.  Introduction

   The SHIM6 working group, and the MULTI6 WG that preceded it, is
   exploring a layer 3 shim approach for providing locator agility below
   the transport protocols, so that multihoming can be provided for IPv6
   with failover and load spreading properties, properties [13], without assuming
   that a multihomed site will have a provider independent IPv6 address
   which is announced in the global IPv6 routing table.  The hosts in a
   site which has multiple provider allocated IPv6 address prefixes,
   will use the shim6 protocol specified in this document to setup state
   with peer hosts, so that the state can later be used to failover to a
   different locator pair, should the original one stop working.

   This document takes the outlines contained in [16] [21] and [15] [20] and
   expands to an actual proposed protocol.

   We assume that redirection attacks are prevented using the mechanism
   specified in HBA [4]. [5].

   The WG mailing list is discussing the scheme used for reachability
   detection [5]. [6].  The schemes that are being discussed are Context
   Unreachability Detection (CUD) or Force Bidirectional communication
   Detection (FBD).  This document doesn't discuss the tradeoffs between
   the two, but it does suggest a set of keepalive and probe messages
   that are sufficient to handle both.  Once the WG has decided which
   approach to take, we can remove the unneeded messages.

   There is a related but slightly separate issue of how the hosts can
   find which of the locator pairs is working after a failure.  This is
   discussed in [6]. [7].  We don't yet know how these details will be done,
   but this draft specifies a separate "Explore" message as a
   placeholder for such a protocol mechanism.

1.1  Placement of the shim

   TBD: Copy material from [16].

2.  Terminology

   This document uses the terms MUST, SHOULD, RECOMMENDED, MAY, SHOULD
   NOT and MUST NOT defined in RFC 2119 [7].  Goals

   The terms defined in RFC
   2460 [1] are also used.

2.1  Definitions

   This document introduces the following terms (taken from [16]): goals for this approach is to:
   o  Preserve established communications through failures, for example,
      TCP connections and application communications using UDP.
   o  Have no impact on upper layer protocol (ULP)
                       A protocol layer immediately above IP.  Examples
                       are transport protocols such as TCP in general and UDP,
                       control protocols such as ICMP, routing on
      transport protocols
                       such as OSPF, in particular.
   o  Address the security threats in [16] through a separate document
      [5], and internet or lower-layer
                       protocols being "tunneled" over (i.e.,
                       encapsulated in) IP such as IPX, AppleTalk, or IP
                       itself.

   interface           A node's attachment techniques described in this document.
   o  No extra roundtrip for setup; deferred setup.
   o  Take advantage of multiple locators/addresses for load spreading
      so that different sets of communication to a link.

   address             An IP layer name host (e.g., different
      connections) might use different locators of the host.

1.2  Non-Goals

   The assumption is that contains both topological
                       significance and acts as a unique identifier for
                       an interface. 128 bits.  This document only uses the "address" term in problem we are trying to solve is site
   multihoming, with the case where it isn't
                       specific whether ability to have the set of site locator
   prefixes change over time due to site renumbering.  Further, we
   assume that such changes to the set of locator prefixes can be
   relatively slow and managed; slow enough to allow updates to the DNS
   to propagate.  But it is not a locator or goal to try to make communication
   survive a identifier.

   locator             An IP layer topological name for an interface or renumbering event (which causes all the locators of a host
   to change to a new set of interfaces. 128 bits.  The locators are
                       carried in the IP address fields locators).  This proposal does not attempt
   to solve, perhaps related, problems such as the packets
                       traverse the network.

   identifier          An IP layer name for host multihoming or host
   mobility.

   This proposal also does not try to provide an IP layer endpoint (stack
                       name in [18]).  The transport endpoint name is identifier.  Even
   though such a
                       function of the transport protocol and concept would
                       typically include be useful to ULPs and applications,
   especially if the IP identifier plus management burden for such a port
                       number.
                       NOTE: This proposal does name space was zero
   and there was an efficient yet secure mechanism to map from
   identifiers to locators, such a name space isn't necessary (and
   furthermore doesn't seem to help) to solve the multihoming problem.

1.3  Locators as Upper-layer Identifiers

   Central to this approach is to not specify any introduce a new form
                       of IP layer identifier, identifier name
   space but still separates the
                       identifying and locating properties instead use one of the IP
                       addresses. locators as the upper-layer identifier (ULID)
                       An IP locator which has been selected for
                       communication with a peer to be used by ID,
   while allowing the upper
                       layer protocol. 128 bits.  This is locators used for
                       pseudo-header checksum computation and connection
                       identification in the ULP.  Different sets of
                       communication address fields to a host (e.g., different
                       connections) might use different ULIDs change over
   time in order response to enable load spreading.

                       Since the ULID is just one failures of using the IP locators/
                       addresses of original locator.

   This implies that the node, there ULID selection is no need for a
                       separate name space and allocation mechanisms.

   address field       The source and destination performed as today's default
   address fields in the
                       IPv6 header.  As IPv6 is currently  selection as specified this
                       fields carry "addresses".  If identifiers in [11].  Underneath, and
                       locators are separated these fields will contain
                       locators for packets on the wire.

   FQDN                Fully Qualified Domain Name

   Host-pair context   The state that
   transparently, the multihoming shim maintains for
                       a particular peer.  The peer is identified by one
                       or more ULIDs.

2.2  Notational Conventions

   A, B, selects working locator pairs
   with the initial locator pair being the ULID pair.  When
   communication fails the shim can test and C are hosts.  X select alternate locators.
   A subsequent section discusses the issues when the selected ULID is a potentially malicious host.

   FQDN(A)
   not initially working hence there is a need to switch locators up
   front.

   Using one of the domain name for A.

   Ls(A) is locators as the locator set ULID has certain benefits for A,
   applications which consists of have long-lived session state, or performs
   callbacks or referrals, because both the locators L1(A),
   L2(A), ...  Ln(A).

   ULID(A) is an upper-layer ID FQDN and the 128-bit ULID
   work as handles for A. In this proposal, ULID(A) the applications.  However, using a single 128-
   bit ULID doesn't provide seamless communication when that locator is
   always one member
   unreachable.  See [17] for further discussion of A's locator set.

   This document also makes use the application
   implications.

   There has been some discussion of internal conceptual variables to
   describe protocol behavior and external variables that an
   implementation must allow system administrators to change.  The
   specific variable names, how their values change, and how their
   settings influence protocol behavior are provided to demonstrate
   protocol behavior.  An implementation is not required to have them in
   the exact form described here, so long using non-routable locators, such
   as its external behavior is
   consistent with that described unique-local addresses [15], as ULIDs in this document.  See Section 7 for a
   description of the conceptual data structures.

3.  Assumptions

   The general approach of a level3 shim as well as multihoming solution.
   While this specific
   proposal makes the following assumptions:

   o  When there document doesn't specify all aspects of this, it is ingress filtering in the ISPs,
   believed that the use of all
      {source, destination} locator pairs will cause approach can be extended to handle such a case.

   For example, the packets protocol already needs to exit
      using different ISPs so handle ULIDs that all exit ISPs are not
   initially reachable.  Thus the same mechanism can be tried.  Since
      there might be only one destination locator, handle ULIDs that
   are permanently unreachable from outside their site.  The issue
   becomes how to make the protocol perform well when the peer
      supports shim6 but ULID is not multihomed,
   reachable, for instance, avoiding any timeout and retries in this implies that the
      selection of the exit ISP should be related
   case.  In addition one would need to understand how the source address ULAs would be
   entered in the packets.

   o  Even without ingress filtering, there is the assumption that if
      the host tries all {source, destination} locator pairs, that it
      has done DNS to avoid a good enough job of performance impact on existing, non-
   shim6 aware, IPv6 hosts potentially trying to find a working path communicate to the
      peer.  Since we want
   (unreachable) ULA.

1.4  IP Multicast

   IP Multicast requires that the protocol to provide benefits even if the
      peer has IP source address field contain a single locator, this seems to imply
   topologically correct locator for interface that is used to send the
   packet, since IP multicast routing uses both the choice of source locator needs address and
   the destination group to somehow affect determine where to forward the exit path from packet.
   (This isn't much different than the
      site.

4.  Protocol Overview

   The shim6 protocol operates situation with widely implemented
   ingress filtering [9] for unicast.)

   While in several phases over time.  The
   following sequence illustrates theory it would be possible to apply the concepts:

   o  An application on host A decides shim re-mapping of
   the IP address fields between ULIDs and locators, the fact that all
   the multicast receivers would need to contact B using some upper-
      layer protocol. know the mapping to perform,
   makes such an approach difficult in practice.  Thus it makes sense to
   have multicast ULPs operate directly on locators and not use the
   shim.  This results is quite a natural fit for protocols which use RTP [12],
   since RTP already has an explicit identifier in the ULP on A sending packets to
      B. We call this form of the initial contact.  Assuming SSRC
   field in the RTP headers.  Thus the actual IP addresses
      selected by Default Address Selection [9] work, then there is no
      action by address fields are not
   important to the shim at application.

1.5  Renumbering Implications

   As stated above, this point in time.  Any shim context
      establishment can be deferred until later.

   o  Some heuristic on A or B (or both) determine that it might make
      sense approach does not try to make this communication robust against locator failures.
      For instance, this heuristic
   survive renumbering.  However, the fact that a ULID might be used
   with a different locator over time open up the possibility that more than 50 packets
      have been sent
   communication between two ULIDs might continue to work after one or received.
   both of those ULIDs are no longer reachable as locators, for example
   due to a renumbering event.  This makes opens up the shim initiate possibility that the
      4-way context establishment exchange.

      As a result of this exchange,
   ULID (or at least the prefix on which it is based) is reassigned to
   another site while it is still being used (with another locator) for
   existing communication.

   Worst case we could end up with two separate hosts using the same
   ULID while both A and B will know a list of
      locators them are communicating with the same host.

   This potential source for each other.

   o  Communication continues without confusion can be avoided if we require that
   any change for the ULP packets.
      In addition, there might communication using a ULID must be some messages exchanged between the
      shim sub-layers for (un)reachability detection.

   o  At some point in time something fails.  Depending on terminated when the approach ULID
   becomes invalid (due to reachability detection, there the underlying prefix becoming invalid).

   However, this might be an overkill.  Even when an IPv6 prefix is
   retired and reassigned to some advise from the
      ULP, or the shim (un)reachability detection might discover that other site, there is still a problem.

      At this point very
   small probability that another host in time one or both ends of that site picks the communication need
      to explore same 128
   bit address (whether using DHCPv6, stateless address
   autoconfiguration, or picking a random interface ID [10]).  Should
   the different alternate locator pairs until identical address be used by another host, then there still
   wouldn't be a working
      pair is found, and rehome to using problem until that pair.

   o  Once a working alternative locator pair has been found, host attempts to communicate with
   the shim
      will rewrite same host with which the packets on transmit, and tag initial user of the packets with a
      shim context tag, and send them on IPv6 address was
   communicating.

1.6  Placement of the wire. shim

                            -----------------------
                            | Transport Protocols |
                            -----------------------

             ------ ------- -------------- -------------     IP endpoint
             | AH | | ESP | | Frag/reass | | Dest opts |     sub-layer
             ------ ------- -------------- -------------

                         ---------------------
                         | shim6 shim layer |
                         ---------------------

                                ------                      IP routing
                                | IP |                      sub-layer
                                ------

                         Figure 1: Protocol stack

   The receiver will
      use proposal uses an multihoming shim layer within the <Source Locator, Destination Locator, Context Tag> to find IP layer,
   i.e., below the context state which will indicate which addresses ULPs, as shown in Figure 1, in order to place provide ULP
   independence.  The multihoming shim layer behaves as if it is
   associated with an extension header, which would be ordered
   immediately after any hop-by-hop options in the IPv6 header before passing packet.  However,
   when the packet up to locator pair is the ULP.  The
      result ULID pair there is no data that from needs to
   be carried in an extension header, thus none is needed in that case.

   Layering AH and ESP above the perspective multihoming shim means that IPsec can
   be made to be unaware of locator changes the ULP same way that transport
   protocols can be unaware.  Thus the packet passes
      unmodified end-to-end, IPsec security associations
   remain stable even though the IP routing infrastructure
      sends the packet locators are changing.  The MOBIKE WG
   is looking at ways to have IPsec security associations survive even
   though the IP addresses changes, which is a different locator.

   o  The shim (un)reachability detection will monitor approach.

   Layering the new locator
      pair as it monitored the original locator pair, so that subsequent
      failures can be detected.

   o  When fragmentation header above the multihoming shim thinks that the context state is no longer used, it
      can garbage collect makes
   reassembly robust in the state; case that there is no coordination necessary
      with the peer host before the state is removed.  There is an error
      message defined to be able to signal when there broken multi-path routing
   which results in using different paths, hence potentially different
   source locators, for different fragments.  Thus, effectively the
   multihoming shim layer is no context
      state, placed between the IP endpoint sublayer,
   which can be used to detect handles fragmentation, reassembly, and recover from both premature
      garbage collection, as well as complete state loss (crash IPsec, and
      reboot) of the IP
   routing sublayer, which on a peer. host selects which default router to use
   etc.

   Applications and upper layer protocols use ULIDs which the shim6
   layer will map to/from different locators.  The data packets in shim6 are carried completely unmodified as long
   as layer maintains
   state, called host-pair context, per ULID pairs (that is, applies to
   all ULP connections between the ULID pair pair) in order to perform this
   mapping.  The mapping is used as performed consistently at the locator pair.  After a switch sender and the
   receiver, thus from the perspective of the upper layer protocols,
   packets appear to a
   different locator pair be sent using ULIDs from end to end, even though
   the packets are "tagged" so that travel through the receiver
   can always determine network containing locators in the context to which they belong.  For commonly
   used IP protocols this is done
   address fields, and even though those locators might be changed by using a different value in
   the Flow
   Label field, that is, there transmitting shim6 layer.

   The context state in this approach is no additional header added to the
   packets.  But for other IP protocol types there maintained per remote ULID i.e.
   approximately per peer host, and not at any finer granularity.  In
   particular, it is an extra 8 byte
   header inserted, which carries independent of the next header value.

4.1  Context Tags ULPs and Use of Flow Label

   A context between any ULP connections.
   However, the forking capability enables shim-aware ULPs to hosts is actually use more
   than one locator pair at a context between two ULIDs. time for an single ULID pair.

   ----------------------------          ----------------------------
   | Sender A                 |          | Receiver B               |
   |                          |          |                          |
   |     ULP                  |          |     ULP                  |
   |      | src ULID(A)=L1(A) |          |      ^                   |
   |      | dst ULID(B)=L1(B) |          |      | src ULID(A)=L1(A) |
   |      v                   |          |      | dst ULID(B)=L1(B) |
   |   multihoming shim       |          |   multihoming shim       |
   |      | src L2(A)         |          |      ^                   |
   |      | dst L3(B)         |          |      | src L2(A)         |
   |      v                   |          |      | dst L3(B)         |
   |      IP                  |          |      IP                  |
   ----------------------------          ----------------------------
          |                                     ^
          ------- cloud with some routers -------

                  Figure 2: Mapping with changed locators

   The context is identified by a pair result of context tags.  Each end gets
   to allocate a context tag, and once the context this consistent mapping is established, the
   shim6 control messages contain that there is no impact on
   the context tag ULPs.  In particular, there is no impact on pseudo-header
   checksums and connection identification.

   Conceptually one could view this approach as if both ULIDs and
   locators are being present in every packet, but with a header
   compression mechanism applied that removes the receiver of need for the message allocated.  Thus at a minimum ULIDs
   once the combination of <peer
   ULID, local ULID, local context> tag MUST uniquely identify one
   context. state has been established.  In addition, order for the non-shim6 messages, which we call payload packets,
   will not contain receiver to
   recreate a packet with the correct ULIDs after there might be a failure.  This introduces need to
   include some "compression tag" in the
   requirement that data packets.  This would serve
   to indicate the <peer locator, local locator, local correct context tag>
   MUST to use for decompression when the
   locator pair in the packet is insufficient to uniquely identify the
   context.  Since

2.  Terminology

   This document uses the peer's set of locators
   might be dynamic the simplest form of unique allocation of the local
   context tag is to pick a number that is unique on the host.  Hosts
   which serve multiple ULIDs using disjoint sets of locators can
   maintain the context tag allocation per such disjoint set.

   As an optimization, to ensure that payload packets, even after the
   locators have been switched from being the original ones, do not
   require an extra shim extension header, the proposal uses the Flow
   Label field terms MUST, SHOULD, RECOMMENDED, MAY, SHOULD
   NOT and MUST NOT defined in RFC 2119 [1].  The terms defined in RFC
   2460 [2] are also used.

2.1  Definitions

   This document introduces the IPv6 header to carry the context tag for common following terms (taken from [21]):
   upper layer protocol (ULP)
                       A protocol layer immediately above IP.  Examples
                       are transport protocols such as TCP and UDP.  This works UDP,
                       control protocols such as follows:

   o  The allocation ICMP, routing protocols
                       such as OSPF, and usage of the flow label during the initial
      communication is unchanged.  Thus the TCP, UDP, etc packets are
      sent with a flow label which is allocated according internet or lower-layer
                       protocols being "tunneled" over (i.e.,
                       encapsulated in) IP such as IPX, AppleTalk, or IP
                       itself.
   interface           A node's attachment to [11].

   o  When the context is created, each endpoint picks an unused context
      tag based on the constraints above, which is also not used a link.
   address             An IP layer name that contains both topological
                       significance and acts as a
      flow label unique identifier for
                       an interface. 128 bits.  This document only uses
                       the set of locators.

   o  The context tag is used by "address" term in the shim to refer to the shim state in
      the control messages (such as probes, and locator updates.

   o  The payload traffic (TCP, UDP, etc.) continue to flow unchanged.

   o  Should there be case where it isn't
                       specific whether it is a need to switch to locator or a different identifier.
   locator pair, then
      the TCP, UDP, etc packets will be sent using             An IP layer topological name for an alternate locator
      pair, and with interface or
                       a flow label that is set of interfaces. 128 bits.  The locators are
                       carried in the same IP address fields as the (20 bit)
      context tag.

   The mechanism packets
                       traverse the network.
   identifier          An IP layer name for detecting an IP layer endpoint (stack
                       name in [23]).  The transport endpoint name is a loss
                       function of context state at the peer that
   is currently proposed in this document assumes that transport protocol and would
                       typically include the receiver can
   tell IP identifier plus a port
                       number.
                       NOTE: This proposal does not specify any new form
                       of IP layer identifier, but still separates the packets that need
                       identifying and locating properties of the IP
                       addresses.
   upper-layer identifier (ULID)
                       An IP locator rewriting, even after it which has lost
   all state (e.g., due to been selected for
                       communication with a crash followed peer to be used by the upper
                       layer protocol. 128 bits.  This is used for
                       pseudo-header checksum computation and connection
                       identification in the ULP.  Different sets of
                       communication to a reboot).  The next
   section specifies how this can be done.

   Note that host (e.g., different
                       connections) might use different ULIDs in order
                       to enable load spreading.

                       Since the ULID is just one of the IP locators/
                       addresses of the node, there is no need for a single context to have more than one
                       separate name space and allocation mechanisms.
   address field       The source and destination address fields in the
                       IPv6 header.  As IPv6 is currently specified this
                       fields carry "addresses".  If identifiers and
                       locators are separated these fields will contain
                       locators for packets on the wire.
   FQDN                Fully Qualified Domain Name
   Host-pair context tag; whether   The state that the locator pair multihoming shim maintains for
                       a particular peer.  The context is <A1, B2>, <A1, B3> or <A2,
   B3> for a ULID
                       pair, as is identified by a context tag for each
                       direction.
   Context tag         Each end of the same context allocates a context tag
                       for the context.  This is used in the flow label field.  Only the to uniquely
                       associate both received control packets and
                       payload packets using with the original <A1, B1> shim6 Payload extension
                       header as belonging to the context.
   Current locator pair use Each end of the flow
   label (which context has a current locator
                       pair which is used to send packets to be peer.
                       The two ends might use different than the locator pairs
                       though.
   Default context tag).

   Whether we overload     At the flow label field to carry sending end, the context tag or
   not, any protocol (such as RSVP or NSIS) which signals information
   about flows from shim uses the host stack to devices in ULID pair
                       (passed down from the path, need ULP) to be
   made aware of find the locator agility introduced by a layer 3 shim, so context
                       for that the signaling pair.  Thus, normally, a host can be performed have
                       at most one context for a ULID pair.  We call
                       this the locator pairs "default context".
   Context forking     A mechanism which allows ULPs that are
   currently being used.

4.2  Protocol type overloading

   The mechanism for detecting a loss aware of context state at the peer that
   is currently proposed
                       multiple locators to use separate contexts for
                       the same ULID pair, in this document assumes that order to be able use
                       different locator pairs for different
                       communication to the receiver can
   tell same ULID.  Context forking
                       causes more than just the packets that need locator rewriting, even after it has lost
   all state (e.g., due default context to be
                       created for a crash followed by ULID pair.

2.2  Notational Conventions

   A, B, and C are hosts.  X is a reboot).  There potentially malicious host.

   FQDN(A) is an
   alternative to detection the domain name for A.

   Ls(A) is the locator set for A, which consists of lost state outlined in Section 18.

   The idea the locators L1(A),
   L2(A), ...  Ln(A).

   ULID(A) is an upper-layer ID for A. In this proposal, ULID(A) is
   always one member of A's locator set.

   This document also makes use of internal conceptual variables to steal a partial bit from the
   describe protocol type fields behavior and external variables that an
   implementation must allow system administrators to change.  The
   specific variable names, how their values change, and how their
   settings influence protocol behavior are used provided to demonstrate
   protocol behavior.  An implementation is not required to have them in
   the Next Header values, exact form described here, so long as its external behavior is
   consistent with that described in this document.  See Section 6 for a
   description of the common upper layer
   protocols can be identified.

   For example:

   o  TCP has protocol 6; TCP using alternate locators has protocol P. conceptual data structures.

3.  Assumptions

   The general approach of a level3 shim as well as this specific
   proposal makes the following assumptions:
   o  UDP has protocol 17; TCP using alternate locators has protocol
      P+1.

   o  ICMPv6 has protocol 58; ICMPv6 using alternate locators has
      protocol P+2.

   o  SCTP has protocol 132; SCTP using alternate locators has protocol
      P+3.

   o  DCCP has protocol ??; DCCP using alternate locators has protocol
      P+4.

   o  ESP has protocol 50; ESP using alternate locators has protocol
      P+5.

   o  AH has protocol 51; AH using alternate locators has protocol P+6.

   o  FRAG has protocol 44; FRAG  When there is ingress filtering in the ISPs, that the use of all
      <source, destination> locator pairs will cause the packets to exit
      using alternate locators has protocol
      P+7.

   Thus with 7 or different ISPs so additional protocol field values we that all exit ISPs can do a
   reasonable job of overloading be tried.  Since
      there might be only one destination locator, when the flow label field and get detection
   of lost context state.

4.3  Securing peer
      supports shim6

   The mechanisms are secured using a combination of techniques:

   o  The HBA technique [4] for validating but is not multihomed, this implies that the locators to prevent an
      attacker from redirecting
      selection of the packet stream exit ISP should be related to somewhere else.

   o  Requiring a Reachability Probe+Reply before a new locator is used
      as the destination, source address
      in order to prevent 3rd party flooding
      attacks.

   o  The first message does not create any state on the responder.
      Essentially a 3-way exchange packets.
   o  Even without ingress filtering, there is required before the responder
      creates any state.  This means assumption that a state-based DoS attack
      (trying to use up all of memory on if
      the responder) at least
      provides an IPv6 address host tries all <source, destination> locator pairs, that it
      has done a good enough job of trying to find a working path to the attacker was using.

   o  The context establishment messages use nonces
      peer.  Since we want the protocol to prevent replay
      attacks.

4.4  Overview provide benefits even if the
      peer has a single locator, this seems to imply that the choice of Shim Control Messages
      source locator needs to somehow affect the exit path from the
      site.

4.  Protocol Overview

   The shim context establishment is accomplished shim6 protocol operates in several phases over time.  The
   following sequence illustrates the concepts:
   o  An application on host A decides to contact B using four messages;
   I1, R1, I2, R2.  Normally they are sent some upper-
      layer protocol.  This results in that order from initiator
   and responder, respectively.  Should both ends attempt the ULP on A sending packets to set up
   context state at
      B. We call this the same time (for initial contact.  Assuming the same ULID pair), IP addresses
      selected by Default Address Selection [11] work, then their
   I1 messages might cross in flight, and result in an immediate R2
   message.  [The names of these messages are borrowed from HIP [17].]

   There is a No Contex error message defined, when a control or payload
   packet arrives and there is no matching context state at
      action by the
   receiver.  When such a message is received, it will result shim at this point in the
   destruction of the time.  Any shim context and a re-establishment.

   The peers' lists of locators are normally exchanged as part of the
   context
      establishment exchange.  But the set of locators might can be
   dynamic.  For deferred until later.
   o  Some heuristic on A or B (or both) determine that it might make
      sense to make this reason there is a Locator List Update message and
   acknowledgement.

   Even though the list of locators is fixed, a host might determine
   that some preferences might have changed. communication robust against locator failures.
      For instance, it this heuristic might
   determine be that there is more than 50 packets
      have been sent or received.  This makes the shim initiate the
      4-way context establishment exchange.

      As a locally visible failure that implies that
   some locator(s) are no longer usable.  Currently result of this mechanism has a
   separate message pair (Rehome Request exchange, both A and acknowledgement), but
   perhaps this can be encoded using the Locator List Update message
   pair with B will know a preference option and no change to the list of locators.

   At least two approaches (CUD and FBD) have been discussed
      locators for each other.

      If the
   shim (un)reachability detection [5].  This document attempt context establishment exchange fails, the initiator will
      then know that the other end does not support shim6, and will
      revert to define
   messages standard unicast behavior for both cases; once the WG has picked an approach we can
   delete session.
   o  Communication continues without any unneeded messages.

   The CUD change for the ULP packets.
      In addition, there might be some messages exchanged between the
      shim sub-layers for (un)reachability detection.
   o  At some point in time something fails.  Depending on the approach uses a probe message and acknowledgement, which can
      to reachability detection, there might be suppressed e.g. using positive some advise from the ULP.  This message
   pair also seems needed to verify that
      ULP, or the host shim (un)reachability detection might discover that
      there is indeed present at a
   new locator before the data stream is redirected to that locator, problem.

      At this point in
   order to prevent 3rd party DoS attacks.

   The FBD approach uses time one or both ends of the communication need
      to explore the different alternate locator pairs until a keepalive message, which working
      pair is sent when found, and rehome to using that pair.
   o  Once a host
   has received packets from the peer, but the ULP working alternative locator pair has not given been found, the
   host an opportunity to send any payload packet to shim
      will rewrite the peer.

   The above probe packets on transmit, and keepalive messages assume we have tag the packets with
      shim6 Payload message as an established
   host-pair context.  However, communication might fail during extension header, which contains the
   initial
      receiver's context (that is, when tag.  The receiver will use the application or transport protocol
   is trying <Source
      Locator, Destination Locator, Context Tag> to setup some communication).  If we want find the shim to be
   able context
      state which will indicate which addresses to optimize discovering a working locator pair place in that case, we
   need a mechanism the IPv6
      header before passing the packet up to test the reachability of locators independent ULP.  The result is
      that from the perspective of
   some context.  We define a locator pair test message and
   acknowledgement for this purpose, the ULP the packet passes unmodified
      end-to-end, even though it isn't yet clear
   whether we need such a thing.

   Finally, when the context is established and there is a failure there
   needs IP routing infrastructure sends the
      packet to be a way to explore different locator.
   o  The shim (un)reachability detection will monitor the set of new locator pairs to efficiently
   find a working pair.  We define an explore message
      pair as a placeholder it monitored the original locator pair, so that subsequent
      failures can be detected.
   o  In addition to failures detected based on end-to-end observations,
      one endpoint might be know for some mechanism in certain that one or more of its
      locators is not working.  For instance, the network interface
      might have failed or gone down (at layer 2), or an IPv6 address
      might have become invalid.  In such cases the host can signal its
      peer that this space [6].

5.  Message Formats

   The shim6 messages are all carried using address is no longer recommended to try.  Thus this
      triggers something similar to a new IP protocol number TBD
   [to be assigned by IANA].  The shim6 messages have failure handling in that a common header,
   defined below, with some fixed fields, followed by type specific
   fields.

5.1  Common Shim6 header new,
      working locator pair must be found.

      The common part Working Group has discussed whether or not hosts can express
      other forms of locator preferences.  If this is the header has case, a next header and header extension
   length field change
      in the preferences can be signaled to the peer, which is consistent with might make
      the other IPv6 extension
   headers, even if peer choose to try a different locator pair.  Thus, this can
      also be treated similarly to a failure.
   o  When the next header value shim thinks that the context state is only used for data payload
   which no longer used, it
      can garbage collect the state; there is carried no coordination necessary
      with a shim6 header on the front.

   The shim6 headers must be a multiple of 8 octets, hence peer host before the minimum
   size state is 8 octets.

   The common message header removed.  There is as follows:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Next Header  |  Hdr Ext Len  |         Checksum              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |                                               |
   +-+-+-+-+-+-+-+-+                                               |
   |                    Type specific format                       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:

   Next Header:   8-bit selector.  Normally set an error
      message defined to NO_NXT_HDR (59).
                  Indicates the next header value for the shim6 payload
                  messages.

   Hdr Ext Len:   8-bit unsigned integer.  Length of the shim6 header in
                  8-octet units, not including the first 8 octets.

   Checksum:      16-bit unsigned integer.  The checksum be able to signal when there is the 16-bit
                  one's complement of the one's complement sum no context
      state, which can be used to detect and recover from both premature
      garbage collection, as well as complete state loss (crash and
      reboot) of the
                  entire shim6 header message starting with the a peer.

   The ULP packets in shim6
                  next header field, and ending are carried completely unmodified as long as indicated by
   the Hdr
                  Ext Len. Thus when there ULID pair is used as the locator pair.  After a payload following switch to a
   different locator pair the packets are "tagged" with a shim6
   extension header, so that the payload is NOT included in receiver can always determine the shim6
                  checksum.

   Type:          8-bit unsigned integer.  Identifies
   context to which they belong.  This is accomplished by including an
   8-octet "shim payload" extension header before the actual message
                  from (extension)
   headers that are processed by the IP endpoint sublayer and ULPs.

4.1  Context Tags

   A context between two hosts is actually a context between two ULIDs.
   The context is identified by a pair of context tags.  Each end gets
   to allocate a context tag, and once the context is established, the
   shim6 control messages contain the context tag that the receiver of
   the message allocated.  Thus at a minimum the combination of <peer
   ULID, local ULID, local context> tag MUST uniquely identify one
   context.

   In addition, the non-shim6 messages, which we call payload packets,
   will not contain the ULIDs after a failure.  This introduces the
   requirement that the <peer locator, local locator, local context tag>
   MUST uniquely identify the context.  Since the peer's set of locators
   might be dynamic the simplest form of unique allocation of the local
   context tag is to pick a number that is unique on the host.  Hosts
   which serve multiple ULIDs using disjoint sets of locators can
   maintain the context tag allocation per such disjoint set.

   The mechanism for detecting a loss of context state at the peer that
   is currently proposed in this document assumes that the receiver can
   tell the packets that need locator rewriting, even after it has lost
   all state (e.g., due to a crash followed by a reboot).

   Even though we do not overload the flow label field to carry the
   context tag, any protocol (such as RSVP or NSIS) which signals
   information about flows from the host stack to devices in the path,
   need to be made aware of the locator agility introduced by a layer 3
   shim, so that the signaling can be performed for the locator pairs
   that are currently being used.

   TBD: add forking - multiple contexts between ULID pairs, default
   context, etc

4.2  Securing shim6

   The mechanisms are secured using a combination of techniques:
   o  The HBA technique [5] for validating the locators to prevent an
      attacker from redirecting the packet stream to somewhere else.
   o  Requiring a Reachability Probe+Reply before a new locator is used
      as the destination, in order to prevent 3rd party flooding
      attacks.
   o  The first message does not create any state on the responder.
      Essentially a 3-way exchange is required before the responder
      creates any state.  This means that a state-based DoS attack
      (trying to use up all of memory on the responder) at least
      provides an IPv6 address that the attacker was using.
   o  The context establishment messages use nonces to prevent replay
      attacks.

4.3  Overview of Shim Control Messages

   The shim context establishment is accomplished using four messages;
   I1, R1, I2, R2.  Normally they are sent in that order from initiator
   and responder, respectively.  Should both ends attempt to set up
   context state at the same time (for the same ULID pair), then their
   I1 messages might cross in flight, and result in an immediate R2
   message.  [The names of these messages are borrowed from HIP [22].]

   There is a No Context error message defined, when a control or
   payload packet arrives and there is no matching context state at the
   receiver.  When such a message is received, it will result in the
   destruction of the shim context and a re-establishment.

   The peers' lists of locators are normally exchanged as part of the
   context establishment exchange.  But the set of locators might be
   dynamic.  For this reason there is a Locator List Update message and
   acknowledgement.

   Even though the list of locators is fixed, a host might determine
   that some preferences might have changed.  For instance, it might
   determine that there is a locally visible failure that implies that
   some locator(s) are no longer usable.  Currently this mechanism has a
   separate message pair (Rehome Request and acknowledgement), but
   perhaps this can be encoded using the Locator List Update message
   pair with a preference option and no change to the list of locators.

   At least two approaches (CUD and FBD) have been discussed for the
   shim (un)reachability detection [6].  This document attempt to define
   messages for both cases; once the WG has picked an approach we can
   delete any unneeded messages.

   The CUD approach uses a probe message and acknowledgement, which can
   be suppressed e.g. using positive advise from the ULP.  This message
   pair also seems needed to verify that the host is indeed present at a
   new locator before the data stream is redirected to that locator, in
   order to prevent 3rd party DoS attacks.

   The FBD approach uses a keepalive message, which is sent when a host
   has received packets from the peer, but the ULP has not given the
   host an opportunity to send any payload packet to the peer.

   The above probe and keepalive messages assume we have an established
   host-pair context.  However, communication might fail during the
   initial context (that is, when the application or transport protocol
   is trying to setup some communication).  If we want the shim to be
   able to optimize discovering a working locator pair in that case, we
   need a mechanism to test the reachability of locators independent of
   some context.  We define a locator pair test message and
   acknowledgement for this purpose, even though it isn't yet clear
   whether we need such a thing.

   Finally, when the context is established and there is a failure there
   needs to be a way to explore the set of locator pairs to efficiently
   find a working pair.  We define an explore message as a place holder
   for some mechanism in this space [7].

5.  Message Formats

   The shim6 messages are all carried using a new IP protocol number TBD
   [to be assigned by IANA].  The shim6 messages have a common header,
   defined below, with some fixed fields, followed by type specific
   fields.

5.1  Payload Message Format

   The payload message is used to carry ULP packets where the receiver
   must replace the content of the source and or destination fields in
   the IPv6 header before passing the packet to the ULP.  Thus this
   extension header is included when the locators pair that is used is
   not the same as the ULID pair.

   Since the shim is placed between the IP endpoint sub-layer and the IP
   routing sub-layer in the host, the shim header will be placed before
   any endpoint extension headers (fragmentation headers, destination
   options header, AH, ESP), but after any routing related headers (hop-
   by-hop extensions header, routing header, a destinations options
   header which precedes a routing header).  When tunneling is used,
   whether IP-in-IP tunneling or the special form of tunneling that
   Mobile IPv6 uses (with Home Address Options and Routing header type
   2), there is a choice whether the shim applies inside the tunnel or
   outside the tunnel, which effects the location of the shim6 header.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Next Header  |       0       |1|       Reserved              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                      Receiver Context Tag                     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:
   Next Header:   The payload which follows this header.
   Hdr Ext Len:   0 (since the header is 8 octets).
   Reserved:      Reserved for future use.  Zero on transmit.  MUST be
                  ignored on receipt.
   Receiver Context Tag: 32-bit unsigned integer.  Allocated by the
                  receiver for use to identify the context (together
                  with the source and destination locators).

5.2  Common Shim6 Control header

   The common part of the header has a next header and header extension
   length field which is consistent with the other IPv6 extension
   headers, even if the next header value is always "NO NEXT HEADER" for
   the control messages; only the payload messages use the Next Header
   field.

   The shim6 headers must be a multiple of 8 octets, hence the minimum
   size is 8 octets.

   The common message header is as follows:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Next Header  |  Hdr Ext Len  |0|     Type    |Type specific|0|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |            Checksum           |                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                               |
   |                    Type specific format                       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:

   Next Header:   8-bit selector.  Normally set to NO_NXT_HDR (59).
                  Indicates the next header value for the shim6 payload
                  messages.
   Hdr Ext Len:   8-bit unsigned integer.  Length of the shim6 header in
                  8-octet units, not including the first 8 octets.
   Type:          7-bit unsigned integer.  Identifies the actual message
                  from the table below.
   0:             A single bit (set to zero) which allows shim6 and HIP
                  to have a common header format yet telling shim6 and
                  HIP messages apart.
   Checksum:      16-bit unsigned integer.  The checksum is the 16-bit
                  one's complement of the one's complement sum of the
                  entire shim6 header message starting with the shim6
                  next header field, and ending as indicated by the Hdr
                  Ext Len. Thus when there is a payload following the
                  shim6 header, the payload is NOT included in the shim6
                  checksum.

  +------------+-----------------------------------------------------+
  | Type Value |                       Message                       |
  +------------+-----------------------------------------------------+
  |      1     | I1 (first establishment message from the initiator) |
  |      2     | R1 (first establishment message from the responder) |
  |      3     |  I2 (2nd establishment message from the initiator)  |
  |      4     |  R2 (2nd establishment message from the responder)  |
  |      5     |                   No Context Error                  |
  |      6     |                    Update Request                   |
  |      7     |                Update Acknowledgement               |
  |      8     |                  Reachability Probe                 |
  |      9     |                  Reachability Reply                 |
  |     10     |                      Keepalive                      |
  |     11     |             Context Locator Pair Explore            |
  +------------+-----------------------------------------------------+

                                  Table 1

5.3  I1 Message Format

   The I1 message is the first message in the context establishment
   exchange.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       59      |  Hdr Ext Len  |0|  Type = 1   |   Reserved1 |0|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |            Checksum           |           Reserved2           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  Initiator Context Tag                        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                    Initiator Nonce                            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                         Options                               +
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:
   Next Header:   NO_NXT_HDR (59).
   Type:          1
   Reserved1:     7-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.
   Reserved2:     16-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.
   Initiator Context Tag: 32-bit field.  The Context Tag the initiator
                  has allocated for the context.
   Initiator Nonce: 32-bit unsigned integer.  A random number picked by
                  the initiator which the responder will return in the
                  R1 message.

   The following options are allowed in the message:
   ULID pair:     TBD Do we need to carry the ULIDs, or assume they are
                  the same as the address fields in the IPv6 header?
                  Depends on how we handle failures during initial
                  contact.

5.4  R1 Message Format

   The R1 message is the second message in the context establishment
   exchange.  The responder sends this in response to an I1 message,
   without creating any state specific to the initiator.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       59      |  Hdr Ext Len  |0|  Type = 2   |   Reserved1 |0|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |            Checksum           |           Reserved2           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                    Initiator Nonce                            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                    Responder Nonce                            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                         Options                               +
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:
   Next Header:   NO_NXT_HDR (59).
   Type:          2
   Reserved1:     7-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.
   Reserved2:     16-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.
   Initiator Nonce: 32-bit unsigned integer.  Copied from the table below.

  +------------+-----------------------------------------------------+
  | Type Value |                       Message                       |
  +------------+-----------------------------------------------------+
  |      1     | I1 (first
                  message.
   Responder Nonce: 32-bit unsigned integer.  A number picked by the
                  responder which the initiator will return in the I2
                  message.

   The following options are allowed in the message:
   Responder Validator: Variable length option.  Typically a hash
                  generated by the responder, which the responder uses
                  together with the Responder Nonce value to verify that
                  an I2 message is indeed sent in response to a R1
                  message, and that the parameters in the I2 message are
                  the same as those in the I1 message.

5.5  I2 Message Format

   The I2 message is the third message in the context establishment
   exchange.  The initiator sends this in response to a R1 message,
   after checking the Initiator Nonce, etc.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       59      |  Hdr Ext Len  |0|  Type = 3   |   Reserved1 |0|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |            Checksum           |           Reserved2           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  Initiator Context Tag                        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                    Initiator Nonce                            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                    Responder Nonce                            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                         Options                               +
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:
   Next Header:   NO_NXT_HDR (59).
   Type:          3
   Reserved1:     7-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.
   Reserved2:     16-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.
   Initiator Context Tag: 32-bit field.  The Context Tag the initiator
                  has allocated for the context.
   Initiator Nonce: 32-bit unsigned integer.  A random number picked by
                  the initiator which the responder will return in the
                  R2 message.
   Responder Nonce: 32-bit unsigned integer.  Copied from the R1
                  message.

   The following options are allowed in the message:
   Responder Validator: Variable length option.  Just a copy of the
                  Validator option in the R1 message.
   ULID pair:     TBD Do we need to carry the ULIDs, or assume they are
                  the same as the address fields in the IPv6 header?
   Locator list:  Optionally sent when the initiator immediately wants
                  to tell the responder its list of locators.  When it
                  is sent, the necessary HBA/CGA information for
                  validating the locator list MUST also be included.
   Locator Preferences: Optionally sent when the locators don't all have
                  equal preference.

   CGA Parameter Data Structure: Included when the locator list is
                  included so the receiver can verify the locator list.
   CGA Signature: Included when the some of the locators in the list use
                  CGA (and not HBA) for validation.

5.6  R2 Message Format

   The R2 message is the fourth message in the context establishment
   exchange.  The responder sends this in response to an I2 message.
   The R2 message from is also used when both hosts send I1 messages at the initiator)
   same time and the I1 messages cross in flight.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       59      |  Hdr Ext Len  |0|  Type = 4   |   Reserved1 |0|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |            Checksum           |           Reserved2           |      2
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | R1 (first                  Responder Context Tag                        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                    Initiator Nonce                            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                         Options                               +
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:
   Next Header:   NO_NXT_HDR (59).
   Type:          4
   Reserved1:     7-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.
   Reserved2:     16-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.
   Responder Context Tag: 32-bit field.  The Context Tag the responder
                  has allocated for the context.
   Initiator Nonce: 32-bit unsigned integer.  Copied from the I2
                  message.

   The following options are allowed in the message:
   Locator List:  Optionally sent when the responder immediately wants
                  to tell the initiator its list of locators.  When it
                  is sent, the necessary HBA/CGA information for
                  validating the locator list MUST also be included.

   Locator Preferences: Optionally sent when the locators don't all have
                  equal preference.
   CGA Parameter Data Structure: Included when the locator list is
                  included and the PDS was not included in the context
                  establishment messages, so the receiver can verify the
                  locator list.
   CGA Signature: Included when the some of the locators in the list use
                  CGA (and not HBA) for validation.

5.7  No Context Error Message Format

   Should a host receive a packet with a shim Payload message from or shim6
   control message, such a a locator update, and the responder) |
  |            |                                                     |
  |      3     |  I2 (2nd establishment message from host does not have
   any context state for the initiator)  |
  |            |                                                     |
  |      4     |  R2 (2nd establishment message from locators (in the responder)  |
  |            |                                                     |
  |      5     | IPv6 source and
   destination fields) and the context tag, then it will generate a No
   Context Error                  |
  |            |                                                     |
  | Error.  The error includes the packet that was received,
   subject to the packet not exceeding 1280 octets.

    0                   1                   2                   3
    0 1 2 3 4 5 6     |                 Locator List Update                 |
  |            |                                                     |
  | 7     |         Locator List Update Acknowledgement         |
  |            |                                                     |
  | 8     |                    Rehome Request                   |
  |            |                                                     |
  | 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                Rehome Acknowledgement               |
  |            |                                                     |
  |     10     |                  Reachability Probe                 |
  |            |                                                     |
  |     11     |               Reachability Probe Reply              |
  |            |                                                     |
  |     12     |                       Payload                       |
  |            |                                                     |
  |     13     |                      Keepalive                      |
  |            |                                                     |
  |     14     |                  Locator Pair Test                  |
  |            |       59      |  Hdr Ext Len  |0|  Type = 5   |     15   Reserved1 |0|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |               Locator Pair Test Reply            Checksum           |           Reserved2           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                         Options                               +
   |     16                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:
   Next Header:   NO_NXT_HDR (59).
   Type:          5
   Reserved1:     7-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.
   Reserved2:     16-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.

   The following options are allowed in the message:
   Packet in Error: Variable length option containing the IPv6 packet
                  that was in error, starting with the IPv6 header, and
                  normally containing the full packet.  If the resulting
                  No Context Locator pair explore            |
  +------------+-----------------------------------------------------+

                                  Table 1

5.2  I1 Error message would exceed 1280 octets, the
                  Packet In Error option will not include the full
                  packet in error in order to limit the error to 1280
                  octets.

5.8  Update Request Message Format

   The I1 message Update Request Message is used to update either the list or
   locators, the locator preferences, and both.  When the list of
   locators is updated, the first message in also contains the option(s)
   necessary for HBA/CGA to secure this.  The basic sanity check that
   prevents off-path attackers from generating bogus updates is the
   context establishment
   exchange. tag in the message.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       59      |  Hdr Ext Len  |0|  Type = 6   |         Checksum              |   Reserved1 |0|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       1            Checksum           | Res           Reserved2           |      Initiator
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                   Receiver Context Tag                        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  Initiator                    Request Nonce                              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                         Options                               +
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:
   Next Header:   NO_NXT_HDR (59).
   Type:          1

   Res:           4-bit          6
   Reserved1:     7-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.

   Initiator
   Reserved2:     16-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.
   Receiver Context Tag: 20-bit 32-bit field.  The Context Tag the initiator receiver has
                  allocated for the context.

   Initiator
   Request Nonce: 32-bit unsigned integer.  A random number picked by
                  the initiator which the responder peer will return in the
                  R1
                  acknowledgement message.

   The following options are allowed in the message:

   ULID pair:     TBD Do we need to carry
   Locator List:  The list of the ULIDs, or assume they are senders (new) locators.  The locators
                  might be unchanged and only the same as preferences have
                  changed.
   Locator Preferences: Optionally sent when the address fields in locators don't all have
                  equal preference.

   CGA Signature: Included when the IPv6 header?
                  Depends on how we handle failures during initial
                  contact.

5.3  R1 Message Format

   The R1 message is some of the second message locators in the context establishment
   exchange.  The responder sends this list use
                  CGA (and not HBA) for validation.

5.9  Update Acknowledgement Message Format

   This message is sent in response to an I1 message,
   without creating a Update Request message.  It
   implies that the Update Request has been received, and that any state specific to new
   locators in the initiator. Update Request can now be used as the source locators
   of packets.  But it does not imply that the (new) locators have been
   verified and will be used as a destination, since the host might
   defer the verification of a locator until it is used as a
   destination.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       59      |  Hdr Ext Len  |0|  Type = 7   |         Checksum              |   Reserved1 |0|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       2            Checksum           |                Reserved           Reserved2           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  Initiator Nonce                   Receiver Context Tag                        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  Responder                      Request Nonce                            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                         Options                               +
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:
   Next Header:   NO_NXT_HDR (59).
   Type:          2

   Reserved:      24-bit          7
   Reserved1:     7-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.

   Initiator Nonce:
   Reserved2:     16-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.
   Receiver Context Tag: 32-bit unsigned integer.  Copied from field.  The Context Tag the I1
                  message.

   Responder receiver has
                  allocated for the context.
   Request Nonce: 32-bit unsigned integer.  A number picked by the
                  initiator which the initiator will return in  Copied from the I2 Update
                  Request message.

   The following

   No options are allowed in the message:

   Responder Validator: Variable length mandatory option.  Typically currently defined for this message.

5.10  Reachability Probe Message Format

   The Reachability Probe message is used to prevent 3rd party DoS
   attacks, and can also be used to verify whether a
                  hash generated by context is
   reachable at a given locator should that be needed for the responder, which general
   reachability detection mechanism (e.g., if we pick the responder CUD mechanism
   where one end sends probes and expects a reply).

   Before a host uses together with a locator for the Responder Nonce value peer that is different than the
   ULID, it needs to verify that an I2 message the peer is indeed sent in response to present at that
   locator by sending a R1
                  message, Context Verify and that the parameters in the I2 receiving an acknowledgement.
   This message are includes the same ULID pair as well as those in the I1 message.

5.4  I2 Message Format

   The I2 message is context tag, so
   that the third message in peer can indeed verify that it has that ULID and that the
   context establishment
   exchange.  The initiator sends this in response to a R1 message,
   after checking the Initiator Nonce, etc. tag is correct.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       59      |  Hdr Ext Len  |0|  Type = 8   |         Checksum              |   Reserved1 |0|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       3       | Res            Checksum           |      Initiator Context Tag           Reserved2           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  Initiator Nonce                   Receiver Context Tag                        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  Responder                      Request Nonce                            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                         Options                               +
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:
   Next Header:   NO_NXT_HDR (59).
   Type:          3

   Res:           4-bit          8
   Reserved1:     7-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.

   Initiator Context Tag: 20-bit
   Reserved2:     16-bit field.  The Context Tag the initiator
                  has allocated for the context

   Initiator Nonce: 32-bit unsigned integer.  A random number picked by
                  the initiator which the responder will return in the
                  R2 message.

   Responder Nonce: 32-bit unsigned integer.  Copied from the R1
                  message.

   The following options are allowed in the message:

   Responder Validator: Variable length mandatory option.  Copied from
                  the Validator in the R1 message.

   ULID pair:     TBD Do we need to carry the ULIDs, or assume they are
                  the same as the address fields in the IPv6 header?

   Locator list:  Optionally sent when the initiator immediately wants
                  to tell the responder its list of locators.  When it
                  is sent, the necessary HBA/CGA information  Reserved for
                  validating the locator list future use.  Zero on
                  transmit.  MUST also be included.

   Locator Preferences: Optionally sent when the locators don't all have
                  equal preference.

   CGA Parameter Data Structure: Included when the locator list is
                  included so ignored on receipt.
   Receiver Context Tag: 32-bit field.  The Context Tag the receiver can verify has
                  allocated for the locator list.

   CGA Signature: Included when context.
   Request Nonce: 32-bit unsigned integer.  A random number picked by
                  the some of initiator which the locators responder will return in the list use
                  CGA (and not HBA) for validation.

5.5  R2 Message Format
                  acknowledgement message.

   The R2 message is the fourth message following options are allowed in the context establishment
   exchange. message:
   ULID pair:     The responder sends this ULID pair that is being probed.

5.11  Reachability Reply Message Format

   This is sent in response to an I2 a Reachability Probe message.
   The R2 message is also used when both hosts send I1 messages at  Although,
   if the
   same time and receiver of the I1 messages cross in flight. Reachability Probe does not have a matching
   context it will send a No Context Error message.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       59      |  Hdr Ext Len  |0|  Type = 9   |         Checksum              |   Reserved1 |0|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       4            Checksum           | Res           Reserved2           |      Responder
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                   Receiver Context Tag                        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  Initiator                      Request Nonce                            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                         Options                               +
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:
   Next Header:   NO_NXT_HDR (59).
   Type:          4

   Res:           4-bit          9
   Reserved1:     7-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.

   Responder
   Reserved2:     16-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.
   Receiver Context Tag: 20-bit 32-bit field.  The Context Tag the responder
                  has allocated for the context

   Initiator Nonce: 32-bit unsigned integer.  Copied from the I2
                  message.

   The following options are allowed in the message:

   Locator List:  Optionally sent when the responder immediately wants
                  to tell the initiator its list of locators.  When it
                  is sent, the necessary HBA/CGA information for
                  validating the locator list MUST also be included.

   Locator Preferences: Optionally sent when the locators don't all have
                  equal preference.

   CGA Parameter Data Structure: Included when the locator list is
                  included so the receiver can verify the locator list.

   CGA Signature: Included when receiver has
                  allocated for the some of context.
   Request Nonce: 32-bit unsigned integer.  Copied from the locators request
                  message.

   The following options are allowed in the list use
                  CGA (and not HBA) for validation.

5.6  No Context Error message:
   ULID pair:     The ULID pair that is being probed.  Copied from the
                  Probe message.

5.12  Keepalive Message Format

   Should a host receive a packet (payload packet or shim6 control

   The keepalive message such a a locator update) and the host does not have any
   context state for the locators (in the IPv6 source and destination
   fields) and would be used if we decide to do the context tag, then it will generate Force
   Bidirectional communication as a No Context
   Error.  The error includes the packet that was received, subject way to get verification that the packet
   locator pair continues to work.  If we are not exceeding 1280 octets. going to do FBD we
   probably will not need this message.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       59      |  Hdr Ext Len  |0|  Type = 10  |   Reserved1 |0|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |            Checksum           |           Reserved2           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       5                   Receiver Context Tag                        |                Reserved
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                      Request Nonce                            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                         Options                               +
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:
   Next Header:   NO_NXT_HDR (59).
   Type:          5

   Reserved:      24-bit          10
   Reserved1:     7-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.
   Reserved2:     16-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.
   Receiver Context Tag: 32-bit field.  The following options are allowed in the message:

   Packet in Error: Variable length mandatory option containing the IPv6
                  packet that was in error, starting with the IPv6
                  header, and normally containing the full packet.  If
                  the resulting No Context Error message would exceed
                  1280 octets, the Packet In Error option will not
                  include Tag the full packet in error in order to limit receiver has
                  allocated for the
                  error to 1280 octets.

5.7 context.
   Request Nonce: 32-bit unsigned integer.  Copied from the Reachability
                  Probe message.

   No options are currently defined for this message.

5.13  Context Locator List Update Pair Explore Message Format

   The Locator List Update (LLU) Message contains

   This is a complete replacement
   of placeholder for the senders protocol mechanism outlined in [7].
   The idea behind that mechanism is to be able to handle the case when
   one locator list, pair works in from A to B, and the options necessary for HBA/CGA another locator pair works
   from B to
   secure this. A, but there is no locator pair which works in both
   directions.  The basic sanity check protocol mechanism is that prevents off-path attackers
   from generating bogus updates as A is the context tag sending explore
   messages to B, B will observe which locator pairs it has received
   from and report that back in the message. explore messages it is sending to A.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       59      |  Hdr Ext Len  |0|  Type = 11  |         Checksum              |   Reserved1 |0|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       6       | Res     Sequence Number           |      Initiator Context Tag         Checksum              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                    Request Nonce                   Receiver Context Tag                        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                         Options                               +
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:
   Next Header:   NO_NXT_HDR (59).
   Type:          6

   Res:           4-bit          11
   Reserved1:     7-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.

   Initiator
   Sequence Number: 16-bit unsigned integer.  Used to determine which
                  messages have been received by the peer.
   Receiver Context Tag: 20-bit 32-bit field.  The Context Tag the initiator receiver has
                  allocated for the context.

   Request Nonce: 32-bit unsigned integer.  A random number picked by
                  the initiator which the responder will return in the
                  acknowledgement message.

   The following options are allowed in the message:

   Locator List:  The list
   Explorer Results: Indication of what Explorer messages the sender has
                  recently received from the peer.

5.14  Option Formats

   All of the TLV parameters have a length (including Type and Length
   fields) which is a multiple of 8 bytes.  When needed, padding MUST be
   added to the end of the parameter so that the total length becomes a
   multiple of 8 bytes.  This rule ensures proper alignment of data.  If
   padding is added, the Length field MUST NOT include the senders (new) locators.  The locators
                  might padding.  Any
   added padding bytes MUST be unchanged and only the preferences have
                  changed.

   Locator Preferences: Optionally sent when zeroed by the locators don't all have
                  equal preference.

   CGA Parameter Data Structure: Included so sender, and their values
   SHOULD NOT be checked by the receiver can verify receiver.

   Consequently, the
                  locator list.

   CGA Signature: Included when Length field indicates the some length of the locators in Contents
   field (in bytes).  The total length of the list use
                  CGA (and not HBA) for validation.

5.8  Locator List Update Acknowledgement Message Format

   This message TLV parameter (including
   Type, Length, Contents, and Padding) is sent in response related to a LLU message. the Length field
   according to the following formula:

   Total Length = 11 + Length - (Length + 3) % 8;
    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      59       |  Hdr Ext Len  |         Checksum              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       7       | Res |      Responder Context Tag             Type            |C|             Length            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                    Request Nonce                              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                                                               |
   /                          Contents                             /
   /                                               +-+-+-+-+-+-+-+-+
   |
   +                         Options                               +                                               |    Padding    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:

   Next Header:   NO_NXT_HDR (59).
   Type:          7

   Res:           4-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.

   Initiator Context Tag: 20-bit field.  The Context Tag the responder
                  has allocated for the context.

   Request Nonce: 32-bit unsigned integer.  Copied from          15-bit identifier of the LLU message. type of option.  The following options are allowed
                  defined in the message:

   TBD any options?:

5.9  Rehome Request Message Format

   TBD Is there any use to have a separate Rehome pair of messages?  The
   sender can indicates its new knowledge of one of its locators (such
   as it no longer working) using the LLU message.  Would it be useful
   to this document are below.
   C:             Critical.  One if this parameter is critical, and MUST
                  be able to specify just failure or preference changes without
   listing the actual locators?  This would require that recognized by the locator
   list is ordered so that a Rehome Request can refer to recipient, zero otherwise.  An
                  implementation might view the locators C bit as part of the
                  Type field, by
   some short index.

   Perhaps multiplying the type values in this functionality can be accomplished
                  specification by sending a Locator
   Update message and only including new Locator Preferences, without
   including any two.
   Length:        Length of the Contents, in bytes.
   Contents:      Parameter specific, defined by Type.
   Padding:       Padding, 0-7 bytes, added if needed.

                +------------------------------+------+
                |          Option Name         | Type |
                +------------------------------+------+
                |           Validator          |   1  |
                |         Locator List option?  If so, we don't need a separate
   message.

5.10  Rehome Acknowledgement Message Format

   TBD: See above.

5.11  Reachability Probe Message         |   2  |
                |      Locator Preferences     |   3  |
                | CGA Parameter Data Structure |   4  |
                |         CGA Signature        |   5  |
                |           ULID Pair          |   6  |
                |        Packet In Error       |   7  |
                |       Explorer Results       |   8  |
                +------------------------------+------+

                                  Table 2

5.14.1  Validator Option Format

   The Reachability Probe message is used responder can choose exactly what input uses to prevent 3rd party DoS
   attacks, compute the
   validator, and what one-way function (MD5, SHA1) it uses, as long as
   the responder can also be used to verify whether a context is
   reachable at a given locator should that be needed for the general
   reachability detection mechanism (e.g., if we pick validator it receives back in the CUD mechanism
   where
   I2 message is indeed one end sends probes that 1) it computed, 2) it computed for the
   particular context, and expects 3) that it isn't a reply).

   Before replayed I2 message.

   One way for the responder to do this is to maintain a host uses single secret
   (S) and a locator running counter for the peer that is different than Responder Nonce.  For each I1
   message, the responder can then increase the
   ULID, it needs to verify that counter, use the peer is indeed present at that
   locator by sending a Context Verify counter
   value as the responder nonce, and receiving an acknowledgement.
   This message includes use the ULID pair as well following information as
   input to the context tag, so
   that one-way function:
   o  The the peer can indeed verify that it has that ULID and that secret S
   o  That Responder Nonce
   o  The Initiator Context Tag from the
   context tag is correct. I1 message
   o  The ULIDs from the I1 message
   o  The locators from the I1 message (strictly only needed if they are
      different from the ULIDs)

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      59       |  Hdr Ext Len  |         Checksum              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      10       | Res |       Receiver Context Tag              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                    Request Nonce           Type = 1          |0|            Length             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                         Options                               +
   |                                                               |
   ~                           Validator                           ~
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:

   Next Header:   NO_NXT_HDR (59).

   Type:          10

   Res:           4-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.

   Receiver Context Tag: 20-bit field.  The Context Tag the peer has
                  allocated for
   Validator:     Variable length content whose interpretation is local
                  to the context.

   Request Nonce: 32-bit unsigned integer.  A random number picked by responder.

5.14.2  Locator List Option Format

   The Locator List Option is used to carry all the initiator which locators of the responder will return in
   sender.  Note that the
                  acknowledgement message.

   The following options are allowed in order of the message:

   ULID pair:     The ULID pair that is being probed.

5.12  Reachability Probe Reply Message Format

   This locators is sent in response important, since the
   Locator Preferences and the Explorer message refers to a Reachability Probe message.  Although,
   if the receiver locators
   by using the index in the list.

   Note that we carry all the locators in this option even though some
   of them can be created automatically from the RT does not have a matching context it will
   send a No Context Error message. CGA Parameter Data
   Structure.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      59       |  Hdr Ext Len  |         Checksum              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      11       | Res |       Receiver Context Tag           Type = 2          |0|            Length             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                    Request Nonce                     Locator List Generation                   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Num Locators |
   +                         Options                               +            N Octets of Verification Method    |
   +-+-+-+-+-+-+-+-+                                               |
   ~                                                               ~
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ~                     Locators 1 through N                      ~
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   Fields:

   Next Header:   NO_NXT_HDR (59).

   Type:          11

   Res:           4-bit field.  Reserved
   Locator List Generation: 32-bit unsigned integer.  Indicates a
                  generation number which is increased by one for future use.  Zero on
                  transmit.  MUST be ignored on receipt.

   Receiver Context Tag: 20-bit field.  The Context Tag each
                  new locator list.  This is used to ensure that the peer has
                  allocated for
                  index in the context.

   Request Nonce: 32-bit Locator Preferences and Explorer results
                  refer to the right version of the locator list.
   Num Locators:  8-bit unsigned integer.  Copied from the request
                  message.  The following options number of locators that
                  are allowed included in the message:

   ULID pair: option.  We call this number "N"
                  below.
   Verification Method: N octets.  The ULID pair that is being probed.  Copied from i'th octet specifies the
                  Probe message.

5.13  Payload Message
                  verification method for the i'th locator.
   Locators:      N 128-bit locators.

   The defined verification methods are:

                          +-------+----------+
                          | Value |  Method  |
                          +-------+----------+
                          |   0   | Reserved |
                          |   1   |    HBA   |
                          |   2   |    CGA   |
                          | 3-255 | Reserved |
                          +-------+----------+

                                  Table 3

5.14.3  Locator Preferences Option Format

   The payload message is used for payload which do not Locator Preferences option can have some flags to indicate
   whether or not a
   designated "foo-inside-shim6" protocol type, as specified in
   Section 4.2.

   Since the shim locator is placed between known to work.  In addition, the IP endpoint sub-layer sender
   can include a notion of preferences.  It might make sense to define
   "preferences" as a combination of priority and weight the IP
   routing sub-layer in the host, same way
   that DNS SRV records has such information.  The priority would
   provide a way to rank the shim header will be placed before
   any endpoint extension headers (fragmentation headers, destination
   options header, AH, ESP), but after any routing related headers (hop-
   by-hop extensions header, routing header, locators, and within a destinations options
   header which precedes given priority, the
   weight would provide a routing header).  When tunneling is used,
   whether IP-in-IP tunneling or way to do some load sharing.  See [8] for how
   SRV defines the special form interaction of tunneling that
   Mobile IPv6 uses (with Home Address Options priority and Routing header type
   2), there weight.

   The minimum notion of preferences we need is to be able to indicate
   that a choice whether locator is "dead".  We can handle this using a single octet
   flag for each locator.

   We can extend that by carrying a larger "element" for each locator.
   This document presently also defines 2-octet and 3-octet elements,
   and we can add more information by having even larger elements if
   need be.

   The locators are not included in the shim applies inside preference list.  Instead, the tunnel or
   outside
   first element refers to locator that was in the tunnel, which effects first element in the
   Locator List option.  The generation number carried in this option
   and the Locator List option is used to verify that they refer to the location
   same version of the shim6 header. locator list.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Next Header           Type = 3          |0|            Length             |       0
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |         Checksum                     Locator List Generation                   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      12  Element Len  |  Element[1]   ...             |  Element[2]   |                Reserved
   |  ...          |  Element[3]   ...             |    ...        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+               |
   ~                              ...                              ~
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:

   Next Header:   The payload
   Locator List Generation: 32-bit unsigned integer.  Indicates a
                  generation number for the locator list to which follows this header.

   Hdr Ext the
                  elements should apply.
   Element Len:   0 (since   8-bit unsigned integer.  The length in octets of each
                  element.  This draft defines the header cases when the length
                  is 8 octets).

   Checksum:      The checksum 1, 2, or 3.
   Element[i]:    A field with a number of octets defined by the 8 octets.

   Type:          12

   Reserved:      Reserved Element
                  Len field.  Provides preferences for future the i'th locator
                  in the Locator List option that is in use.  Zero on transmit.  MUST

   When the Element length equals one, then the element consists of only
   a flags field.  The set of flags is TBD: Assume there will be
                  ignored on receipt.

5.14  Keepalive Message two
   initially: BROKEN and TEMPORARY.  The intent of the latter is to
   allow the distinction between more stable addresses and less stable
   addresses when shim6 is combined with IP mobility, when we might have
   more stable home locators, and less stable care-of-locators.

   When the Element length equals two, the the element consists of a 1
   octet flags field followed by a 1 octet priority field.  The priority
   has the same semantics as the priority in DNS SRV records.

   When the Element length equals three, the the element consists of a 1
   octet flags field followed by a 1 octet priority field, and a 1 octet
   weight field.  The weight has the same semantics as the weight in DNS
   SRV records.

5.14.4  CGA Parameter Data Structure Option Format

   The keepalive message would be

   This option contains the CGA parameter data structure (hereafter
   called the PDS).  When HBA is used if we decide to do validate the Force
   Bidirectional communication as a way to get verification that locators, the
   locator pair continues PDS
   contains the HBA multiprefix extension.  When CGA is used to work.  If we are not going validate
   the locators, in addition to do FBD we
   probably the CGA PDS, the signature will not need this message. to
   be included as a CGA Signature option.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      59       |  Hdr Ext Len  |         Checksum              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      13       | Res |         Receiver Context Tag           Type = 4          |0|            Length             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                         Options                               +
   |                                                               |
   ~                   CGA Parameter Data Structure                ~
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:

   Next Header:   NO_NXT_HDR (59).

   Type:          13

   Res:           4-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.

   Receiver Context Tag: 20-bit field.  The Context Tag the peer has
                  allocated for the context.

   The following options are allowed in the message:

   TBD any options?:

5.15  Locator Pair Test Message Format

   The above Reachability Probe message probes a context.  This message
   just probes a locator.  If we are going to handle failure during
   initial contact using the shim, then the shim needs to be able to
   find out what locators are working (and that they correspond to a
   desirable ULID) without assuming there is a context setup, and
   without knowing the actual ULID.  The latter is needed so that we can
   handle the case when the AAAA RRset contains any combination of
   multiple hosts and multiple IP addresses
   CGA Parameter Data Structure: Variable length content.  Content
                  defined in [5].

5.14.5  CGA Signature Option Format

   When CGA is used for a given host.  Having
   the responder send back the ULID that corresponds to a particular
   locator allows validation of one or more of the initiator to take locators in the AAAA RRset and determine
   which IPv6 addresses therein are for different hosts.

   Once we understand how
   PDS, then the shim will be involved message in locator failures
   during initial contact, then we can determine whether we question will need to contain this
   mechanism, and whether it can be overloaded on the Probe Message
   (e.g., by making the Receiver Context tag optional in the
   Reachability Probe message). option.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      59       |  Hdr Ext Len  |         Checksum              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      14       |                Reserved                       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                    Request Nonce                              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                    Target ULID                                +
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                         Options                               +
   |           Type = 5          |0|            Length             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:

   Next Header:   NO_NXT_HDR (59).

   Type:          14

   Reserved:      24-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.

   Request Nonce: 32-bit unsigned integer.  A random number picked by
                  the sender which the target will return in the reply
                  message.

   Target ULID:   128-bit IPv6 address.

   The following options are allowed
   CGA Signature: Variable length content.  Content defined in the message:

   TBD any options?:

5.16  Locator [5].

5.14.6  ULID Pair Test Reply Message Option Format

   If a host receives a Locator Pair Test message, and the Target ULID
   is one of its IP addresses, then it will send

   It isn't clear whether we need this reply.

   TBD: If ULID doesn't match, does it just ignore the test message?  Or
   send some error?

   TBD: Should the responder instead return its ULID, so that it is
   easier option.  It depends whether we
   want to be able to setup a context for the sender a ULID pair when that ULID
   pair can't be used to determine which of communicate.  Thus the IPv6 addresses from in the DNS correspond to different hosts vs. different locators for
   context establishment would not be the
   same host? ULIDs.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      59       |  Hdr Ext Len  |         Checksum              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      15       |                Reserved                       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                    Request Nonce           Type = 2          |0|            Length             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                    Target                         Sender ULID                           +
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                         Options                        Receiver ULID                          +
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:

   Next Header:   NO_NXT_HDR (59).

   Type:          15
   Reserved:      24-bit      48-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.

   Request Nonce: 32-bit unsigned integer.  Copied from the test
                  message.

   Target
   Sender ULID:   A 128-bit IPv6 address.  Copied from the test message.
                  TBD: Or should the host be able to fill this in to
                  make it easier for the peer to determine
   Receiver ULID: A 128-bit IPv6 address.

5.14.7  Packet In Error Option Format

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           Type = 7          |0|            Length             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ~           IPv6 header, shim6/TCP/UDP header, etc              ~
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:
   Packet:        A variable length field which
                  locators refer to contains the same host?

   The following options are allowed packet in
                  error starting with the message:

   TBD any options?:

5.17  Context Locator Pair Explore Message IPv6 header.

5.14.8  Explorer Results Option Format

   TBD: This is a placeholder for the protocol mechanism outlined in [6].
   The idea behind that mechanism is to be able to handle the case when
   one locator pair works in from A needs to B, indicate which explorer messages (sequence
   numbers, source and another locator pair works
   from B destination locators?) that have been recently
   received, in order to A, but detect which locator pairs work when there is
   no locator pair which works in both directions.  The protocol mechanism is that as A is sending explore
   packets to B, B will observe which locator pairs  When indicating
   locators it has received from
   and report makes sense to use the offset in the Locator List (that
   was carries in the Locator List option), since this takes less space
   than including the locators themselves.

   TBD: add that back data and other shim control messages are included in explore packets it is sending to A.
   the learned results.

   p
    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      59       |  Hdr Ext Len  |         Checksum           Type = 8          |0|            Length             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      16       | Res |       Receiver Context Tag                Sender Locator List Generation                 |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                   Sequence Number               Receiver Locator List Generation                |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                         Options                               +
   |                                                               |
   ~                         Explorer Results                      ~
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:

   Next Header:   NO_NXT_HDR (59).

   Type:          16

   Res:           4-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.

   Receiver Context Tag: 20-bit field.
   Sender Locator List Generation: The Context Tag the peer has
                  allocated generation number for the context.

   Sequence Number: 32-bit unsigned integer.  Used
                  sender's locator list to determine which
                  packets have been received by the peer. indices below
                  refer.
   Receiver Locator List Generation: The following options are allowed in generation number for the message:
                  receiver's locator list to which the indices below
                  refer.
   Explorer Results: Indication This field contains a list of what Explorer messages elements, where each
                  element indicates one locator pair for which the
                  sender of the option has recently received from the peer.

6.  Option Formats a message.
                  Each result occupies 32 bits.  The options follow list should be
                  ordered so that the same layout as in RFC 2461 [2].  Thus they all most recently heard locator pairs
                  are a multiple of 8 octets. first.  SHOULD NOT include locator pairs that were
                  last received more than some number of seconds ago.
   p
    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |    Length Sender Index  |              ... Receiver Index|        Sequence Number        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ~                              ...                              ~
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:

   Type:
   Sender Index:  8-bit identifier of the type of option. unsigned Integer.  The options
                  defined in this document are below.

   Length: Index is relative to the
                  sender's locator list.
   Receiver Index: 8-bit unsigned integer. Integer.  The length Index is relative to the
                  receiver locator list.
   Sequence Number: 16-bit unsigned Integer.  The Sequence number of the option
                  (including
                  explorer message in which the type and length fields) locator pair < sender
                  index, receiver index> was last heard.  If this
                  locator pair was last heard in units a message other than an
                  Explore message, then this number is zero.

6.  Conceptual Model of 8
                  octets. a Host

   This section describes a conceptual model of one possible data
   structure organization that hosts will maintain for the purposes of
   shim6.  The value 0 described organization is invalid.  Nodes MUST silently
                  discard an ND packet provided to facilitate the
   explanation of how the shim6 protocol should behave.  This document
   does not mandate that contains an option implementations adhere to this model as long as
   their external behavior is consistent with
                  length zero.

                +------------------------------+------+
                |          Option Name         | Type |
                +------------------------------+------+
                |           Validator          |   1  |
                |                              |      |
                |         Locator List         |   2  |
                |                              |      |
                |      Locator Preferences     |   3  |
                |                              |      |
                | CGA Parameter Data Structure |   4  |
                |                              |      |
                |         CGA Signature        |   5  |
                |                              |      |
                |           ULID Pair          |   6  |
                |                              |      |
                |        Packet In Error       |   7  |
                |                              |      |
                |       Explorer Results       |   8  |
                +------------------------------+------+

                                  Table 2 that described in this
   document.

6.1  Validator Option Format  Conceptual Data Structures

   The key conceptual data structure for the shim6 protocol is the host
   pair context.  This is a data structures which contains the following
   information:
   o  The responder can choose exactly what input uses peer ULID; ULID(peer)
   o  The local ULID; ULID(local)
   o  The list of peer locators, with their preferences; Ls(peer)
   o  For each peer locator, a bit whether it has been validated using
      HBA, and a bit whether the locator has been probed to compute verify that
      the
   validator, and what one-way function (MD5, SHA1) it uses, ULID is present at that location.
   o  The preferred peer locator - used as long destination; Lp(peer)
   o  The set of local locators and the preferences; Ls(local)
   o  The preferred local locator - used as source; Lp(local)
   o  The context tag used to transmit control messages and ULP packets
      - allocated by the reponder can verify peer; CT(peer)
   o  The context to expect in received control messages and extension
      headers - allocated by the local host; CT(local)
   o  Reachability state for the locator pairs.
   o  During pair exploration, information about the explore messages
      that have been sent and received.

   The receiver finds the validator context by looking it receives back up using <Source
   Locator, Destination Locator, CT(local)>, where the context tag is in
   the I2 shim header.  The sender needs to be able to find the context
   state when a ULP packet is indeed one that 1) it computed, 2) it computed for passed down from the
   particular context, and 3) ULP.  In that it isn't a replayed I2 message.

   One way for case
   the lookup key is the pair of ULIDs.

7.  Establishing Host Pair Contexts

   Host pair contexts are established using a 4-way exchange, which
   allows the responder to do avoid creating state on the first packet.  As
   part of this is to maintain exchange each end allocates a single secret
   (S) context tag, and a running counter for the Responder Nonce.  For each I1
   message, the responder can then increase the counter, use the counter
   value as the responder nonce, it shares
   this context tag and use its set of locators with the following information as
   input peer.

   In some cases the 4-way exchange is not necessary, for instance when
   both ends try to setup the one-way function:

   o  The context at the secret S

   o  That Responder Nonce

   o  The Initiator Context Tag same time, or when
   recovering from a context that has been garbage collected or lost at
   one of the I1 message

   o hosts.

7.1  Normal context establishment

   The ULIDs from the I1 normal context establishment consists of a 4 message

   o  The locators from exchange in
   the order of I1, R1, I2, R2.

        Initiator                          Responder

              ------------- I1 message (strictly only needed if they are
      different from the ULIDs)

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |   Type = 1    |    Length     |                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                               |
   ~                           Validator                           ~
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:

   Validator:     Variable length content whose interpretation is local -------------->

              <------------ R1 ---------------

              ------------- I2 -------------->

              <------------ R2 ---------------

                                 Figure 26

7.2  Concurrent context establishment

   When both ends try to initiate a context for the responder.

6.2  Locator List Option Format

   The Locator List Option is used to carry all same ULID pair, then
   we might end up with crossing I1 messages, or since the locators of no state is
   created when receiving the
   sender.  Note I1, a host might send a I1 after having
   sent a R1 message.

   Since a host remembers that it has sent an I1, it can respond to an
   I1 from the order of peer (for the locators is important, same ULID), with a R2.

        Initiator                          Responder

              -\
                ---\
                    ---\                  /---
                        --- I1 ---\   /---
                                   ---\
                       /--- I1 ---/    ---\
                  /---                     -->
              <---

              -\
                ---\
                    ---\                  /---
                        --- R2 ---\   /---
                                   ---\
                       /--- R2 ---/    ---\
                  /---                     -->
              <---
                                 Figure 27

   If a host has received an I1 and sent an R1, then a ULP can trigger
   it to send an I1 message itself, since it doesn't retain any state
   when receiving the
   Locator Preferences and I1 message.  Thus while one end is sending an I1
   the Explorer packet refers other is sending an I2.

        Initiator                          Responder

              -\
                ---\
                    ---\
                        --- I1 ---\
                                   ---\
                                       ---\
                                           -->

                                          /---
                                      /---
                                   ---
                       /--- R1--/
                  /---
              <---

              -\
                ---\
                    ---\                  /---
                        --- I2---\   /---
                                   ---\
                       /--- I1 ---/    ---\
                  /---                     -->
              <---

              -\
                ---\
                    ---\                  /---
                        --- R2 ---\   /---
                                   ---\
                       /--- R2 ---/    ---\
                  /---                     -->
              <---

                                 Figure 28

7.3  Context recovery

   Due to the locators by garbage collection, we can end up with one end having and
   using the index in context state, and the list.

   TBD: Do we other end not having any state.  We
   need this when all the locators are contained in the PDS?
    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |   Type = 2    |    Length     |                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                               |
   |                           Reserveds                           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ~                            Locators                           ~
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:

   Reserved:      48-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.

   Locators:      A variable number of 128-bit locators.  The number of
                  locators present can to be determined by the option
                  length field.

6.3  Locator Preferences Option Format

   The Locator Preferences option able to recover this state at the end that has lost it,
   before we can have some flags use it.

   This need can arise in two cases:
      The communication is working using the ULID pair as the locator
      pair, but a problem arises, and the end that has retained the
      context state decides to indicate
   whether or not explore alternate locator pairs.
      The communication is working using a locator pair that is known to work. not the
      ULID pair, hence the ULP packets sent from a peer that has
      retained the context state use the shim payload header.
   In addition, both cases the sender
   can include result is that the peer without state receives a notion of preferences.  It might make sense
   shim message for which it has to define
   "preferences" as a combination context for the <source locator,
   destination locator, context tag>.

   In both of priority those case we can recover the context by having the node
   which doesn't have a context state, send back an R1bis [TBD] message,
   and weight have this complete a recover with a I2 and R2 message.

   If one end has garbage collected or lost the context state, it might
   try to create the context state (for the same way
   that DNS SRV records has such information. ULID pair), by sending
   an I1 message.  The priority would
   provide a way to rank peer can simply reply with an R2 message in this
   case.

7.4  Context confusion

   Since each end might garbage collect the locators, context state we can have
   the case when one end has retained the context state and within a given priority, tries to use
   it, while the other end has lost the state.  We discussed this in the
   previous section on recovery.  But for the same reasons, when one
   host retains context tag X for ULID pair <A1, B1>, the
   weight would provide a way to do some load sharing.  See [8] other end
   might end up allocating that context tag for how
   SRV defines another ULID pair, e.g.,
   <A3, B1> between the interaction of priority and weight.

   As of same hosts.  In this draft case we define can not use the preferences
   recovery mechanisms since there needs to include three 8-bit
   fields: a priority, a weight, and 8-bits be separate context tags for
   the two ULID pairs.

   This type of flags.  The intent "confusion" can be observed in two cases (assuming it is
   A that has retained the TBD flags can  carry information such as "this locator is
   not working", state and "this locator is temporary".  The latter allows
   making the distinction between more stable addresses B has dropped it):
      B decides to create a context for ULID pair <A3, B1&gt, and less stable
   addresses when shim6 is combined with IP mobility, when we might have
   more stable home locators,
      allocates X as its context tag for this, and less stable care-of-locators.

   The locators are not included in the preference list.  Instead, the
   first element refers sends an I1 to locator that was in the first element in the
   Locator List option.  This assumes that the Locator List option is
   stable.  See Section 17.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |   Type = 3    |    Length     |     Pri[1]    |  Weight[1]    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |   Flags[1]    |    Pri[2]     |  Weight[2]    |   Flags[2]    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ~                              ...                              ~
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:

   Pri[i]:        8-bit unsigned integer.  The Priority associated with A.
      A decides to create a context for ULID pair <A3, B1&gt, and starts
      the i'th locator in exchange by sending I1 to B. When B receives the Locator List option I2 message,
      it allocates X as the context tag for this context.
   In both cases, A can detect that B has allocated X for ULID pair <A3,
   B1&gt even though that A still X as CT(peer) for ULID pair <A1,
   B1&gt.  Thus A can detect that B must have lost the context for <A1,
   B1&gt.

   The solution to this issue is in
                  use.

   Weight[i]:     8-bit unsigned integer. TBD.  The Weight associated with
                  the i'th locator in know possibilities are:
      Have A forcibly destroy the Locator List option context for <A1, B1&gt, so that is in
                  use.

   Flags[i]:      8-bit unsigned integer.  The flags associated with it can
      accept the
                  i'th locator in new context for <A3, B1&gt.
      Have A accept the Locator List option that is in
                  use.

   The set of flags is TBD: Assume there context for <A3, B1&gt, forget about the old
      context, but initiate a new (replacement) context for <A1, B1&gt
      by sending an I1 message.  That I1 through R2 exchange will be two initially: BROKEN
   and TEMPORARY.

6.4  CGA Parameter Data Structure Option Format

   This option contains make B
      allocate a new context tag for <A1, B1&gt.
      Avoid the CGA parameter data structure (hereafter
   called problem by changing the PDS).  When HBA is used to validate context tag allocation so that A
      and B allocates half of the locators, bits (16 each) of the PDS
   contains context tags, so
      that even if one end looses state, the HBA multiprefix extension. peer can make sure that the
      context tags for each context are unique.

7.5  Sending I1 messages

   When CGA is used the shim layer decides to setup a context for a ULID pair, it
   starts by allocating and initializing the context state for its end.
   As part of this it assigns its context tag to validate the locators, context.  Then it
   can send an I1 message.

   If the host does not receive an I2 or R2 message in addition response to the CGA PDS, the signature will need
   I1 message, then it needs to
   be included as retransmit the I1 message.  The
   retransmissions should use a CGA Signature option.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |   Type = 4    |    Length     |                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                               |
   ~                   CGA Parameter Data Structure                ~
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:

   CGA Parameter Data Structure: Variable length content.  Content
                  defined in [4].

6.5  CGA Signature Option Format

   When CGA is used retransmission timer with binary
   exponential backoff to avoid creating congestion issues for validation of one or more the
   network when lots of hosts perform this.

   If, after several retransmissions, there is no response, then most
   likely the locators in peer does not implement the
   PDS, then shim6 protocol, or there could
   be a firewall that blocks the message in question will need to contain this option.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |   Type = 5    |    Length     |                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                               |
   ~                           CGA Signature                       ~
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:

   CGA Signature: Variable length content.  Content defined in [4].

6.6  ULID Pair Option Format

   It isn't clear whether we need protocol.  In this option.  It depends whether we
   want case it makes sense
   for the host to be able remember to setup not try again to establish a host pair
   context with that ULID.  However, any such negative caching should
   retained for a ULID pair when that ULID
   pair can't limit time; a few minutes would be used appropriate, to communicate.  Thus the IPv6 addresses in
   allow things to recover should the
   context establishment would host not be reachable at all when
   the ULIDs.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |   Type = 6    |    Length     |                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                               |
   |                           Reserveds                           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                         Sender ULID                           +
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                        Receiver shim tries to establish the context.

   If the host receives an ICMP error with "payload type unknown" and
   the included packet is the I1 packet it just sent, then this is a
   more reliable indication that the peer ULID                          +
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:

   Reserved:      48-bit field.  Reserved for future use.  Zero on
                  transmit.  MUST be ignored on receipt.

   Sender ULID:   A 128-bit IPv6 address.

   Receiver ULID: A 128-bit IPv6 address.

6.7  Packet In Error Option Format

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |   Type = 7    |    Length     |                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                               |
   |                           Reserveds                           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ~           IPv6 header, shim6/TCP/UDP header, etc              ~
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:

   Reserved:      48-bit field.  Reserved does not implement shim6.

7.6  Receiving I1 messages

   If the host looks up a context for future use.  Zero on
                  transmit.  MUST be ignored on receipt.

   Packet:        A variable length field which contains the packet in
                  error starting with ULID pair and the IPv6 header.

6.8  Explorer Results Option Format

   TBD: This peer's (not
   its) context tag.  If it finds such a context, the it needs to indicate which explorer packets (sequence numbers,
   source and destination locators) verify
   that have been recently received, the locators in
   order to detect which the message are in fact part of the locator pairs work sets
   that are recorded in the existing context state.  If this is not the
   case, then the I1 message MUST be silently ignored.  (This can only
   happen when there is no locator an ULID pair option in the I1 message.)  If the
   locators are ok, then the host can respond with an R2 message as if
   it had received an I2 message and not an I1 message.

   If there is no existing context state, then the host forms a verifier
   and sends this back to the peer in an I2 message.  No state is
   created on the host in this case.

7.7  Receiving R1 messages

   When the host receives an R1 message, it verifies that the nonce
   matches what it sent in the I1 message, and that it has context state
   for the ULID pair.  It then sends an I2 message, which works includes the
   verifier option that was in the R1 message.  The I2 message also
   includes A's locator list and the CGA parameter set.  If CGA (and not
   HBA) is used to verify the locator list, then A also signs things and
   includes a CGA signature option.

   The host may receive an R1[bis] TBD message that was not sent in both directions.  When indicating locators it
   makes sense
   response to an I1 message but instead sent as a result of context
   recovery.  The difference between an R1bis and an R1 message is that
   the former use the offset in context tag of the Locator List (that was carries
   in responder???  TBD how there are
   handled and whether they are identical to an R1.

7.8  Retransmitting I2 messages

   If the LLU option), initiator does not receive an R2 message after sending an I2
   message it MAY retransmit the I2 message.  But since this takes less space than including the
   locators themselves.
   p
    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |   Type = 8    |    Length     |              TBD              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ~                              ...                              ~
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:

   TBD:

7.  Conceptual Model of a Host

   This section describes verifier
   option might have a conceptual model of one possible data
   structure organization limited lifetime, that hosts will maintain for is, the purposes of
   shim6.  The described organization is provided peer might reject
   verifier options that are too old to facilitate avoid replay attacks, the
   explanation of how
   initiator SHOULD fall back to retransmitting the shim6 protocol should behave.  This document
   does not mandate that implementations adhere I1 message when
   there is no response to this model as long as
   their external behavior one or a few I2 messages.

7.9  Receiving I2 messages

   The responder checks that the nonce and the verifier option is
   consistent with that described what it might have sent in this
   document.

7.1  Conceptual Data Structures

   The key conceptual data structure for a recent R1 message (by
   verifying the shim6 protocol hash it computed.)  If this is ok, then the host checks
   if it already has context state for the ULID pair context.  This is a data structures which contains and the following
   information:

   o  The peer ULID; ULID(peer)

   o  The local ULID; ULID(local)

   o  The list of peer locators, with their preferences; Ls(peer)

   o  For each peer locator, a bit whether CT(peer).
   If it has been validated using
      HBA, and such state, the I2 message was probably a bit whether retransmission.
   In this case the host sends an R2 message.

   If there is no context state, the responder allocates a context tag
   (CT(local)) and creates the context state for the context.  It
   records the peer's locator has been probed to set as well as its own locator set in the
   context.  It MAY verify that the ULID is present peers locator set at this point in time,
   but the requirement is that location.

   o  The preferred peer a locator - used as destination; Lp(peer)

   o MUST be verified before the
   host starts sending packets to that locator, thus the host MAY defer
   the verification until later.

   The set of local host forms an R2 message with its locators and its context tag,
   and includes the necessary options so that the peer can verify the
   locators.

   R2 messages are never retransmitted.  If the R2 message is lost, then
   the initiator will retransmit either the I2 or I1 message.  Either
   retransmission will cause the responder to find the preferences; Ls(local)

   o  The preferred local locator - used as source; Lp(local)

   o  The context tag used state and
   respond with an R2 message.

7.10  Receiving R2 messages

   The initiator can receive an R2 message in response to transmit packets - allocated by either an I1
   or an I2 message, but the handling of the peer;
      CT(peer)

   o  The context to expect R2 is the same in received packets - allocated by both
   cases.  The host first verifies that the local
      host; CT(local)

   o  Reachability state for nonce is the locator pairs.

   o  During pair exploration, information about same as the explore packets
      that have been one
   it sent and received.

   The receiver finds (in the context by looking I1 or I2 message).  If it up using <Source
   Locator, Destination Locator, CT(local)>, where doesn't match, the context tag R2
   message is silently dropped.

   Then the host records the information from the R2 message in the Flow Label field for ULP payload packets, and
   context state.  It records the peer's locator set in the shim headers
   for control messages.  The sender needs to be able to find context.  It
   MAY verify the
   context state when a packet peers locator set at this point in time, but the
   requirement is passed down from that a locator MUST be verified before the ULP.  In host starts
   sending packets to that
   case locator, thus the lookup key is host MAY defer the pair of ULIDs.
   verification until later.

8.  Establishing Host Pair Contexts

   TBD

8.1  Sending I1 messages

8.2  Receiving I1 messages

8.3  Receiving R1 messages

8.4  Retransmitting I1 messages

8.5  Receiving I2 messages

8.6  Retransmitting I2 messages

8.7  Concurrent context establishment

9.  No Such Content Errors

   TBD

10.

   The Interim Meeting discussed ways to recover the context state at
   one end when the other end sees a failure (and starts sending Explore
   messages).  The discussed approach is to use a R1 (or R1bis) message
   in response to a message with an unknown context, which would cause
   the context to be recreated.

9.  Handling ICMP Error Messages

   The routers in the path as well as the destination might generate
   various ICMP error messages, such as host unreachable, packet too
   big, and payload type unknown.  It is critical that these packets
   make it back up to the ULPs so that they can take appropriate action.

   When the ULP packets are sent unmodified, that is, while the initial
   locators=ULIDs are working, this introduces no new concerns; an
   implementation's existing mechanism for delivering these errors to
   the ULP will work.  But when the shim on the transmitting side
   replaces the ULIDs in the IP address fields with some other locators,
   then an ICMP error coming back will have a "packet in error" which is
   not a packet that the ULP sent.  Thus the implementation will have to
   apply the reverse mapping to the "packet in error" before passing the
   ICMP error up to the ULP.

   This mapping is different than when receiving ULP packets from the
   peer, because in that case the packets contain CT(local).  But the
   ICMP errors have a "packet in error" with CT(peer) since they were
   intended to be received by the peer.  In any case, since the <Source
   Locator, Destination Locator, CT(peer)> has to be unique when
   received by the peer, the local host should also only be able to find
   one context that matches this tuple.

   Should the ULP packet have been conveyed using the protocol type
   encoding (Section 4.2), then that encoding must be undone for the
   packet in error before it is delivered able to the ULP. find
   one context that matches this tuple.

   If the ULP packet had been encapsulated in a shim6 payload message,
   then this extension header must be removed.  The result needs to be
   that the ULP receives an ICMP error where the contained "packet in
   error" looks as if the shim did not exist.

11.  Taredown

10.  Teardown of the Host Pair Context

   Each host can unilaterally decide when to tare tear down a host-pair
   context.  It is RECOMMENDED that hosts not tare tear down the context when
   they know that there is some upper layer protocol that might use the
   context.  For example, an implementation might know this is there is
   an open socket which is connected to the ULID(peer).  However, there
   might be cases when the knowledge is not readily available to the
   shim layer, for instance for UDP applications which not not connect
   their sockets, or any application which retains some higher level
   state across (TCP) connections and UDP packets.

   Thus it is RECOMMENDED that implementations minimize premature
   taredown
   teardown by observing the amount of traffic that is sent and received
   using the context, and only after it appears quiescent, tare tear down the
   state.

12.

11.  Updating the Locator Pairs

   TBD

13.

12.  Various Probe Mechanisms

   TBD

14.

13.  Rehoming to a Different Locator Pair

   TBD

15.

14.  Payload Packets before a Switch

   When there is no context state for the ULID pair on the sender, there
   is no effect on how ULP packets are sent.  If the host is using some
   heuristic for determining when to perform a deferred context
   establishment, then the host might need to do some accounting (count
   the number of packets sent and received) even before there is a host-
   pair context.  This need to count packets might also appear on the
   receive side, depending on what heuristics the implementation has
   chosen.

   If there is a host-pair context for the ULID pair, then the sender
   needs to verify whether context uses the ULIDs as locators, that is,
   whether Lp(peer) == ULID(peer) and Lp(local) == ULID(local).

   If this is the case, then packets will be sent unmodified by the
   shim.  If it is not the case, then the logic in Section 16 15 will need
   to be used.

   There will also be some maintenance activity relating to
   (un)reachability detection, whether packets are sent with the
   original locators or not.  The details of this is out of scope for
   this document and will be covered is follow-ons to [5].

16. [6].

15.  Payload Packets after a Switch

   When sending packets, if there is a host-pair context for the ULID
   pair, and the ULID pair is no longer used as the locator pair, then
   the sender needs to transfer transform the packet.  The transformation depends
   on  Apart from replacing the payload type, since some protocol values can be carried
   without adding a shim6 extension header,
   IPv6 source and others need destination fields with a locator pair, an 8-octet
   header.

   Before
   header is added so that the payload dependent transformation, receiver can find the context and inverse
   the transformation.

   First, the IP address fields are replaced.  The IPv6 source address
   field is set to Lp(local) and the destination address field is set to
   Lp(peer).  NOTE that this MUST NOT cause any recalculation of the ULP
   checksums, since the ULP checksums are carried end-to-end and the ULP
   pseudo-header contains the ULIDs which are preserved end-to-end.

   The sender skips any "routing sub-layer extension headers", headers" that the
   ULP might have included, thus it skips any hop-by-hop extension
   header, any routing header, and any destination options header that
   is followed by a routing header.  The
   (extension) header that follows after that is viewed as the ULP
   header.

   If  After any such headers the ULP shim6
   extension header is of a type listed in Section 4.2, then it is
   replaced by the "foo-in-shim6 value for that protocol type.  And in
   this case, the context tag CT(peer) is placed in the flow label field
   in the IPv6 header.  Then the packet can will be passed to the IP routing
   sub-layer.

   If the ULP header type is not listed in that section, then added.  This might be before a Fragment
   header, a Destination Options header, an ESP or AH header, or a ULP
   header.

   The inserted shim6 Payload extension header is inserted in the packet before the ULP
   header.  In this case includes the peer's
   context tag CT(peer) is also placed in the
   flow label field, and the packet is passed down to the routing sub-
   layer.  TBD: We could use the Reserved field in the payload message
   instead of using flow label in this case. tag.

   The receiver parses the (extension) headers in order.  Should it find
   a shim6 extension header it will look at the type field in that
   header.  If the type is Payload message, then the packet must be
   passed to the shim6 payload handling for rewriting.  If the receiver
   finds one of the eight additional payload type (for "foo-inside-
   shim6"), then it treats this analogous to the case of a shim6 payload
   extension header.

   In both cases handling for rewriting.  (Otherwise, the
   shim6 control messages are handled as specified in other parts of
   this document.)

   The receiver extracts the context tag from the IPv6
   flow label field, payload message
   header, and uses this together with the IPv6 source and destination
   address fields to find a host-pair context.  If no context is found,
   the receiver SHOULD generate a No Such Context error message (see
   Section 9). 8).

   With the context in hand, the receiver can now replace the IP address
   fields with the ULIDs kept in the context.  Finally, the traces of
   the shim are removed from the packet; any payload Payload
   extension header is
   removed, removed from the packet (so that the ULP doesn't
   get confused by it), and the next header value in the preceding
   header is set to be the actual protocol number for the payload.  Then
   the packet can be passed to the ULP.

17. protocol identified by the next
   header value (which might be some function associated with the IP
   endpoint sublayer, or a ULP).

16.  Open Issues

   The following open issues are known:
   o  Is there need for keeping the list of locators private between the
      two communicating endpoints?  We can potentially accomplish that
      when using CGA but not with HBA, but it comes at the cost of doing
      some public key encryption and decryption operations as part of
      the context establishment.
   o  Forking the context state.  On the mailing list we've discussed
      the need to fork the context state, so that different ULP streams
      can be sent using different locator pairs.  No protocol extensions
      are needed if any forking is done independently by each endpoint.
      But if we want A to be able to tell B that certain traffic (a
      5-tuple?) should be forked, then we need a way to convey this in
      the shim6 protocol.  The hard part would be defining what
      selectors can be specified for the filter which determines which
      traffic uses which of the forks.  So the question is whether we
      really need signaling for forking, or whether it is sufficient to
      allow each endpoint to do its own selection of which locator pair
      it is using for which traffic.
   o  If we allow forking, it seems like the mechanism for reachability
      detection, whether it is CUD or FBD, must be applied separately
      for each locator pair that is in use.  Without forking a single
      locator pair will be in use for each host-pair context, hence
      things would be simpler.
   o  Having the Locator List option contain all the prefixes implies
      extra bytes when the locators are also in the CGA Parameter Data
      Structure option.  To optimize this will still need to provide an
      ordered list, so that the Locator Preferences can refer to the
      locators by "index".  (The Explore Results option might need to
      refer to them by index as well.)

   o  The index to a locator might get out of synch between the two ends
      if messages with a new Locator List option is lost.  It might make
      sense to include a "generation" or "locator list version" number
      in the Locator List option so that the Locator Preference (and
      Explorer Result) options can refer to a particular version of the
      list.

   o  The specified mechanism (of relying on No Such Context errors)
      doesn't always detect the loss of the context on the peer when the
      original ULID=locators are used.  See Section 18 for other
      options.

   o  Which messages need sequence numbers to prevent parts of the
      protocol to operate on stale information should the shim6
      information get out of date?  Just the Locator List Update
      message?

   o  The CGA PDS might not need to be included in every LLU message.
      If it is associated with the ULID, it is sufficient to exchange it
      once.  Then a HBA-protected LLU would not need anything (it can
      just change the preferences for loss of the locators in any case), and a
      CGA-protected LLU would just need context on the signature option. peer when the
      original ULID=locators are used.  See Section 17 for other
      options.

   o  In the LLU Locator List option, do we need to indicate which locators
      need to be validated using HBA vs. CGA?  Or it could tell which
      locators are in the HBA extension in the PDS, and assume any
      others need CGA validation.
   o  What happens when a host runs out of 20 N bit context tags?  When is
      it safe for a host to reuse a context tag?  With the unilateral
      taredown
      teardown one end might discard the context state long before the
      other end.

18.

17.  Design Alternatives

   This document has picked a certain set of design choices in order to
   try to work out a bunch of the details, and stimulate discussion.
   But as has been discussed on the mailing list, there are other
   choices that make sense.  This section tries to enumerate some
   alternatives.

18.1

17.1  State Cleanup

   This document uses a timer based cleanup mechanism, as specified in
   Section 11. 10.

   An alternative would be to use an explicit CLOSE mechanism, akin to
   the one specified in HIP [17]. [22].  If an explicit CLOSE handshake and
   associated timer is used, then there would no longer be a need for
   the No Context Error message due to a peer having garbage collected
   its end of the context.  However, there is still potentially a need
   to have a No Context Error message in the case of a complete state
   loss of the peer (also known as a crash followed by a reboot).  Only
   if we assume that the reboot takes at least the CLOSE timer, or that
   it is ok to not provide complete service until CLOSE timer minutes
   after the crash, can we completely do away with the No Context Error
   message.

   If there

17.2  Detecting Context Loss

   This document specifies that context loss is no need for the detected by receiving a
   No Such Context Error message, this also means
   that it might be possible to remove error message from the need peer.  Such messages are
   generated in response to explicitly
   identifying the a shim6 payload packets after message that contain a locator switch, neither
   using the foo-inside-shim6 protocol number nor using peer's
   context tag, including the shim6 Payload message.  In essence, messages, when the receiver could identify the context
   based on the locator pair and the Flow Label
   doesn't have matching context.  They are also generated in the received packets.

   There might be some debugging and operational issues with removing
   the explicit identification of the shim6 response
   to data packets after a locator
   switch.  Should the receiver have lost the context state, then there
   will be no indication that something is going wrong.  The shim on the
   receiver would happily pass up the switch (because such payload packets unmodified to the ULP, and
   the ULP would most likely see a checksum error.  The checksum error
   is caused
   are identified as such by using the ULP packet having different IP addresses than payload message header).

   This approach has the
   packet disadvantage that it doesn't detect the sending ULP passed down to its shim.

18.2  Not Overloading the Flow Label

   This document overloads the Flow Label field as a loss of
   context tag for
   packets that are sent after state when the locators have been switched, that is, original ULIDs are used as locators, because
   there might be no shim6 messages exchanged if the packets where reachability
   detection manages to suppress any extra messages.

   The Interim Meeting discussed ways to recover the sending shim has replaced context state at
   one end when the ULIDs with some other locator pair.

   An alternative would be end sees a failure (and starts sending Explore
   messages).  The discussed approach is to not do this, and instead always use the
   shim6 Payload a R1 (or R1bis) message
   in response to encapsulate the payloads when a message with an unknown context, which would cause
   the locators
   are different than context to be recreated.

18.  Implications Elsewhere

   The general shim6 approach, as well as the ULIDs.  While specifics of this doesn't remove proposed
   solution, has implications elsewhere.  The key implications are:
   o  Applications that perform referrals, or callbacks using IP
      addresses as the need 'identifiers' can still function in limited ways,
      as described in [17].  But in order for such applications to
   have any QoS signaling protocol be aware
      able to take advantage of the shim6 architectural
   implications Section 19, it does offer some other simplifications to multiple locators for redundancy,
      the protocol, namely that there would no longer be a applications need to be modified to either use
   designated protocol number values for fully qualified
      domain names as the "foo-inside-shim6"; 'identifiers', or they need to pass all the
   cases when those protocol numbers are used would instead use
      locators as the
   Payload message.  The downside of always using 'identifiers' i.e., the Payload message
   after 'identifier' from the
      applications perspective becomes a failure is set of IP addresses instead of
      a single IP address.
   o  Firewalls that today pass limited traffic, e.g., outbound TCP
      connections, would presumably block the path MTU usable by shim6 protocol.  This
      means that even when shim6 capable hosts are communicating, the ULP I1
      messages would be 8
   octets less.

18.3  Detecting Context Loss

   This document specifies dropped, hence the hosts would not discover that context loss
      their peer is detected by receiving shim6 capable.  This is in fact a
   No Such Context error message from feature, since if
      the peer.  Such messages are
   generated in response hosts managed to establish a shim6 message host-pair context, then the
      firewall would probably drop the "different" packets that contain are sent
      after a the peer's
   context tag, including failure (those using the shim6 Payload messages, when the receiver
   doesn't have matching context.  They payload message with a TCP
      packet inside it).  Thus stateful firewalls  that are modified to
      allow shim6 messages through should also generated in response be modified to data packets allow the
      payload messages through after a locator switch (because such payload packets
   are identified as such using the overloaded protocol field specified
   in Section 4.2). failure.  This approach has the disadvantage of presumably implies
      that the overloaded protocol type,
   and it also doesn't detect firewall needs to track the loss set of context state when locators in use by
      looking at the
   original ULIDs are used as locators, because there might be no shim6
   messages exchanged if the reachability detection manages exchanges.  Such firewalls might even want to suppress
   any extra packets.

   Discussion: it isn't clear we could remove
      verify the protocol type
   overloading with this approach, because without protocol type
   overloading it is undefined in what order locators using the receiver would do
   things.  Normally HBA/CGA verification themselves.
   o  Signaling protocols for QoS or other things that involve having
      devices in the receiver follows network path look at IP addresses and port numbers,
      or IP addresses and Flow Labels, need to be invoked on the next header chain and
   processes things hosts
      when the locator pair changes due to a failure.  At that point in order.  This also works with an overloaded
   protocol type;
      time those protocols need to inform the devices that next header value is basically indicating a new pair of
      IP addresses will be used for the flow.  Note that
   there this is the
      case even though we no longer overload the flow label as a zero length shim payload header.  Thus context
      tag; the sender can
   control whether this happens before in-path devices need to know about the processing use of some other
   extension header or after.  Without any such indication in the
   packet, new
      locators even though the receiver would find flow label stays the same.
   o  MTU implications.  The path MTU mechanisms we use are robust
      against different packets taking different paths through the
      Internet, by computing a shim context based on minimum over the <Source
   Locator, Destination Locator, Flow Label>.  But would it process recently observed path
      MTUs.  When shim6 fails over from using one locator pair to
      another pair, this
   before or after some other extension header, means that packets might travel over a
      different path through the Internet, hence the path MTU might be
      quite different.  Perhaps such as a MIPv6 Home
   Address Option, or IP-in-IP encapsulation header?

   An alternative path change would be a good hint
      to remove the protocol field overloading and
   mandate path MTU mechanism to try a larger MTU?

      The fact that there be some low-frequency periodic Reachability Probe/
   Reply messages, even when there is bidirectional communication and the ULPs report that they are doing fine.  Such shim, at least for uncommon payload types, will
      add an approach would be
   able to detect state loss even before there is 8 octet extension header (the payload message) after a
      locator switch.

   Presumably such probes switch, can be suppressed when there are no ULP
   packets being sent to also affect the peer.

19.  Implications Elsewhere

   The general shim6 approach, as well as usable path MTU for the specifics of ULPs.
      In this proposed
   solution, has implications elsewhere.  The key implications are:

   o  Applications that perform referals, or callbacks using IP
      addresses as case the 'identifiers' can still function MTU change is local to the sending host, thus
      conveying the change to the ULPs is an implementation matter.

19.  Security Considerations

   This document satisfies the concerns specified in limited ways, [16] as described in [12].  But in order follows:
   o  TBD: Using HBA or CGA for such applications to be
      able to take advantage ...

   Some of the multiple locators for redundancy, residual threats in this proposal are:
   o  An attacker which arrives late on the applications need to be modified to either path (after the context has
      been established) can use fully qualified
      domain names as the 'identifiers', or they need No Such Context error to pass all cause one
      peer to recreate the
      locators as context, and at that point in time the 'identifiers' i.e.,
      attacker can observe all of the 'identifier' from exchange.  But this doesn't seem
      to open any new doors for the
      applications perspective becomes a set of IP addresses instead of
      a single IP address.

   o  Firewalls that today pass limited traffic, e.g., outbound TCP
      connections, would presumably block attacker since such an attacker can
      observe the shim6 protocol.  This
      means Context tags that even when shim6 capable hosts are communicating, the I1
      packets would be dropped, hence being used, and once known it
      can use those to send bogus messages.
   o  An attacker which is present on the hosts would not discover path so that
      their peer is shim6 capable.  This is in fact it can find out
      the context tags, can generate a feature, since if No Such Context error after it
      has moved off the hosts managed path.  For this packet to establish be effective it needs
      to have a host-pair source locator which belongs to the context, then thus there
      can not be "too much" ingress filtering between the
      firewall would probably drop attackers new
      location and the "different" packets communicating peers.  But this doesn't seem to be
      that are sent
      after a failure (either using a "TCP-inside-shim6" protocol
      number, or using severe, because once the shim6 payload packet with a TCP packet inside
      it).  Thus stateful firewalls  that are modified error causes the context to allow shim6
      packets through should also be modified torn
      down and re-established, a new pair of context tags will be used,
      which will not be known to allow the payload
      packets through after attacker.  If this is still a failure.  This presumably implies that the
      firewall needs to track
      concern, we could require a 2-way handshake "did you really loose
      the set of locators state?" in use by looking at response to the shim6 exchanges. error message.
   o  Signaling protocols  It might be possible for QoS or other things an attacker to try random 32-bit context
      tags and see if they can cause disruption for communication
      between two hosts.  We can make this harder by using a larger
      context tag; 47 bits is the largest that involve having
      devices fit in the 8-octet
      payload header.  If this isn't sufficient, one could use an even
      larger tag in the network path look at IP addresses and port numbers,
      or IP addresses shim6 control messages, and Flow Labels, need to be invoked on the hosts
      when use the locator pair changes due to a failure.  At that point low-order 47
      bits in
      time those protocols need to inform the devices that payload header.

20.  IANA Considerations

   IANA needs to allocate a new pair of IP addresses will be used Next Header value for this protocol.

   TBD: the flow, as well as a new Flow
      Label being used.

   o  MTU implications. IANA rules for the shim6 message types and option types.

21.  Change Log

   The path MTU mechanisms we following changes have been made since draft-ietf-shim6-proto-00:
   o  Removed the use are robust
      against different packets taking different paths through of the
      Internet, by computing a minimum over flow label and the recently observed path
      MTUs.  When shim6 fails over from using one locator pair to
      another pair, this means that packets might travel over a
      different path through overloading of the Internt, hence IP
      protocol numbers.  Instead, when the path MTU might be
      quite different.  Perhaps such a path change would be a good hint
      to locator pair is not the path MTU mechanism to try a larger MTU?

      The fact that ULID
      pair, the shim, at least for uncommon payload types, ULP payloads will
      add be carried with an 8 octet extension header (the payload message) after a
      locator switch, can also affect the usable path MTU for the ULPs.
      In this case the MTU change
      header.  The belief is local that it is possible to remove these extra
      bytes by defining future shim6 extensions that exchange more
      information between the sending host, thus
      conveying the change hosts, without having to overload the ULPs is an implementation matter.

20.  Security Considerations

   Some of flow
      label or the residual threats in this proposal are: IP protocol numbers.
   o  An attacker which arrives late on the path (after  Grew the context has
      been established) can use tag from 20 bits to 32 bits, with the No Such Context error possibility
      to cause one
      peer grow it to 47 bits.  This implies changes to recreate the context, and at that point in time the
      attacker can observe all of message
      formats.
   o  Almost by accident, the exchange.  But this doesn't seem
      to open any new doors shim6 message format is very close to
      the HIP message format.
   o  Adopted the HIP format for the attacker options, since such an attacker can
      observe this makes it easier
      to describe variable length options.  The original, ND-style,
      option format requires internal padding in the Context tags options to make
      them 8 octet length in total, while the HIP format handles that are being used,
      using the option length field.
   o  Removed some of the control messages, and once known it
      can use those to send bogus messages. renamed the other ones.
   o  An attacker which is present on  Added a "generation" number to the path Locator List option, so that it can find out
      the context tags, peers can generate a No Such Context error after it
      has moved off ensure that the path.  For this packet to be effective it needs preferences refer to have a source locator which belongs the right
      "version" of the Locator List.
   o  In order for FBD and exploration to work when there the context, thus use of the
      context is forked, that is different ULP messages are sent over
      different locator pairs, things are a lot easier if there
      can not be "too much" ingress filtering between is only
      one current locator pair used for each context.  Thus the attackers new
      location and forking
      of the communicating peers.  But this doesn't seem context is now causing a new context to be
      that severe, because once established for
      the error causes same ULID; the new context to be torn
      down and re-established, having a new pair of context tags will be used,
      which will not be known to the attacker.  If this tag.  The
      original context is still a
      concern, we could require a 2-way handshake "did you really loose
      the state?" in response referred to as the error message.

   o  It might be possible for an attacker to try random 24-bit "default" context
      tags and see if they can cause disruption for communication
      between two hosts.  We can make this harder by using a larger
      context tag (64-bits?) in the shim6 control messages,
      ULID pair.
   o  Added more background material and use the
      low-order 24 bits as the flow label.

21. textual descriptions.

22.  Acknowledgements

   Over the years many people active in the multi6 and shim6 WGs have
   contributed ideas a suggestions that are reflected in this draft.

   Thanks to Marcelo Bagnulo for providing comments on earlier versions
   of this draft.

22.

23.  References

22.1

23.1  Normative References

   [1]  Bradner, S., "Key words for use in RFCs to Indicate Requirement
        Levels", BCP 14, RFC 2119, March 1997.

   [2]  Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6)
        Specification", RFC 2460, December 1998.

   [2]

   [3]  Narten, T., Nordmark, E., and W. Simpson, "Neighbor Discovery
        for IP Version 6 (IPv6)", RFC 2461, December 1998.

   [3]

   [4]  Thomson, S. and T. Narten, "IPv6 Stateless Address
        Autoconfiguration", RFC 2462, December 1998.

   [4]

   [5]  Bagnulo, M., "Hash Based Addresses (HBA)",
        draft-ietf-shim6-hba-00 (work in progress), July 2005.

   [5]

   [6]  Beijnum, I., "Shim6 Reachability Detection",
        draft-ietf-shim6-reach-detect-00 (work in progress), July 2005.

   [6]

   [7]  Arkko, J., "Failure Detection and Locator Selection Pair Exploration
        Design
        Considerations", draft-ietf-shim6-failure-detection-00 for IPv6 Multihoming",
        draft-ietf-shim6-failure-detection-01 (work in progress), July
        October 2005.

22.2

23.2  Informative References

   [7]   Bradner, S., "Key words for use in RFCs to Indicate Requirement
         Levels", BCP 14, RFC 2119, March 1997.

   [8]   Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for
         specifying the location of services (DNS SRV)", RFC 2782,
         February 2000.

   [9]   Ferguson, P. and D. Senie, "Network Ingress Filtering:
         Defeating Denial of Service Attacks which employ IP Source
         Address Spoofing", BCP 38, RFC 2827, May 2000.

   [10]  Narten, T. and R. Draves, "Privacy Extensions for Stateless
         Address Autoconfiguration in IPv6", RFC 3041, January 2001.

   [11]  Draves, R., "Default Address Selection for Internet Protocol
         version 6 (IPv6)", RFC 3484, February 2003.

   [10]

   [12]  Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson,
         "RTP: A Transport Protocol for Real-Time Applications", STD 64,
         RFC 3550, July 2003.

   [13]  Abley, J., Black, B., and V. Gill, "Goals for IPv6 Site-
         Multihoming Architectures", RFC 3582, August 2003.

   [11]

   [14]  Rajahalme, J., Conta, A., Carpenter, B., and S. Deering, "IPv6
         Flow Label Specification", RFC 3697, March 2004.

   [12]

   [15]  Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast
         Addresses", RFC 4193, October 2005.

   [16]  Nordmark, E., "Threats relating to IPv6 multihoming solutions",
         draft-ietf-multi6-multihoming-threats-03 (work in progress),
         January 2005.

   [17]  Nordmark, E., "Shim6 Application Referral Issues",
         draft-ietf-shim6-app-refer-00 (work in progress), July 2005.

   [13]

   [18]  Abley, J., "Shim6 Applicability Statement",
         draft-ietf-shim6-applicability-00 (work in progress),
         July 2005.

   [14]

   [19]  Huston, G., "Architectural Commentary on Site Multi-homing
         using a Level 3 Shim", draft-ietf-shim6-arch-00 (work in
         progress), July 2005.

   [15]

   [20]  Bagnulo, M. and J. Arkko, "Functional decomposition of the
         multihoming protocol", draft-ietf-shim6-functional-dec-00 (work
         in progress), July 2005.

   [16]

   [21]  Nordmark, E. and M. Bagnulo, "Multihoming L3 Shim Approach",
         draft-ietf-shim6-l3shim-00 (work in progress), July 2005.

   [17]

   [22]  Moskowitz, R., "Host Identity Protocol", draft-ietf-hip-base-03
         (work in progress), June 2005.

   [18]

   [23]  Lear, E. and R. Droms, "What's In A Name:Thoughts from the
         NSRG", draft-irtf-nsrg-report-10 (work in progress),
         September 2003.

Author's Address

   Erik Nordmark
   Sun Microsystems
   17 Network Circle
   Menlo Park, CA 94043 94025
   USA

   Phone: +1 650 786 2921
   Email: erik.nordmark@sun.com

Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.

Disclaimer of Validity

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Copyright Statement

   Copyright (C) The Internet Society (2005).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.

Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society.