Issue 59 (was: protocol draft status and moving forward)
Tero Kivinen <[email protected]> Fri, 28 Oct 2005 10:54:05 +0300
| Newsgroups | gmane.ietf.mobike |
|---|---|
| Message-ID | <[email protected]> |
Jari Arkko writes:
> 59 - tero's editorial comments (Tero - please check -05)
Checking...
Hmm... 1, 4, 5, 6 seems to be in the draft.
9 is missing, and 10 is missing the picture.
11 and 12 seems also be missing.
Here is actual changes needed to be made to 05:
Change
----------------------------------------------------------------------
4. Payload Formats . . . . . . . . . . . . . . . . . . . . . . . 20
4.1. MOBIKE_SUPPORTED Notify Payload . . . . . . . . . . . . . 20
4.2. ADDITIONAL_IP4/6_ADDRESS Notify Payloads . . . . . . . . . 20
4.3. NO_ADDITIONAL_ADDRESSES Notify Payload . . . . . . . . . . 20
4.4. UPDATE_SA_ADDRESSES Notify Payload . . . . . . . . . . . . 20
4.5. UNACCEPTABLE_ADDRESSES Notify Payload . . . . . . . . . . 21
4.6. COOKIE2 Notify Payload . . . . . . . . . . . . . . . . . . 21
4.7. NO_NATS_ALLOWED Notify Payload . . . . . . . . . . . . . . 21
4.8. UNEXPECTED_NAT_DETECTED Notify Payload . . . . . . . . . . 21
----------------------------------------------------------------------
to
----------------------------------------------------------------------
4. Payload Formats
4.1 Notify messages - Error types
4.1.1 UNACCEPTABLE_ADDRESSES Notify Payload
4.1.2 UNEXPECTED_NAT_DETECTED Notify Payload
4.2 Notify messages - Status types
4.2.1. MOBIKE_SUPPORTED Notify Payload
4.2.2. ADDITIONAL_IP4/6_ADDRESS Notify Payloads
4.2.3. NO_ADDITIONAL_ADDRESSES Notify Payload
4.2.4. UPDATE_SA_ADDRESSES Notify Payload
4.2.5. COOKIE2 Notify Payload
4.2.6. NO_NATS_ALLOWED Notify Payload
----------------------------------------------------------------------
And change the section
----------------------------------------------------------------------
4. Payload Formats
This specification defines several new IKEv2 Notify payload types.
The UNACCEPTABLE_ADDRESSES and UNEXPECTED_NAT_DETECTED notifications
are "error types"; the other notifications are "status types". See
[IKEv2] Section 3.10 for a general description of the Notify payload.
----------------------------------------------------------------------
to:
----------------------------------------------------------------------
4. Payload Formats
This specification defines several new IKEv2 Notify payload types.
See [IKEv2] Section 3.10 for a general description of the Notify
payload.
4.1 Notify messages - Error types
4.1.1 UNACCEPTABLE_ADDRESSES Notify Payload
...
4.2 Notify messages - Status types
...
----------------------------------------------------------------------
Also change the section 6. IANA Considerations from:
----------------------------------------------------------------------
Notify Message Value
--------------------------- -----
MOBIKE_SUPPORTED TBD-BY-IANA1 (16396..40959)
ADDITIONAL_IP4_ADDRESS TBD-BY-IANA2 (16396..40959)
ADDITIONAL_IP6_ADDRESS TBD-BY-IANA3 (16396..40959)
NO_ADDITIONAL_ADDRESSES TBD-BY-IANA4 (16396..40959)
UPDATE_SA_ADDRESSES TBD-BY-IANA5 (16396..40959)
UNACCEPTABLE_ADDRESSES TBD-BY-IANA6 (40..8191)
COOKIE2 TBD-BY-IANA7 (16396..40959)
NO_NATS_ALLOWED TBD-BY-IANA8 (16396..40959)
UNEXPECTED_NAT_DETECTED TBD-BY-IANA9 (40..8191)
----------------------------------------------------------------------
to
----------------------------------------------------------------------
NOTIFY MESSAGES - ERROR TYPES Value
------------------------------ -----
UNACCEPTABLE_ADDRESSES TBD-BY-IANA6 (40..8191)
UNEXPECTED_NAT_DETECTED TBD-BY-IANA9 (40..8191)
NOTIFY MESSAGES - STATUS TYPES Value
------------------------------ -----
MOBIKE_SUPPORTED TBD-BY-IANA1 (16396..40959)
ADDITIONAL_IP4_ADDRESS TBD-BY-IANA2 (16396..40959)
ADDITIONAL_IP6_ADDRESS TBD-BY-IANA3 (16396..40959)
NO_ADDITIONAL_ADDRESSES TBD-BY-IANA4 (16396..40959)
UPDATE_SA_ADDRESSES TBD-BY-IANA5 (16396..40959)
COOKIE2 TBD-BY-IANA7 (16396..40959)
NO_NATS_ALLOWED TBD-BY-IANA8 (16396..40959)
----------------------------------------------------------------------
Just to align with the format used in the IKEv2.
For 10 change:
----------------------------------------------------------------------
4.7. NO_NATS_ALLOWED Notify Payload
See Section 3.9 for a description of this notification.
The data field of this notification contains the following
information: the IP address from which the packet was sent (4 or 16
bytes), the port from which the packet was sent (2 bytes, network
byte order), the IP addresss to which the packet was sent (4 or 16
bytes), and the port to which the packet was sent (2 bytes, network
byte order). The total length of the data field is thus 12 bytes for
IPv4 and 36 bytes for IPv6. The Notify Message Type for this message
is TBD-BY-IANA8. The Protocol ID and SPI Size fields are set to
zero.
----------------------------------------------------------------------
to (just added the picture)
----------------------------------------------------------------------
4.7. NO_NATS_ALLOWED Notify Payload
See Section 3.9 for a description of this notification.
The data field of this notification contains the following
information: the IP address from which the packet was sent (4 or 16
bytes), the port from which the packet was sent (2 bytes, network
byte order), the IP addresss to which the packet was sent (4 or 16
bytes), and the port to which the packet was sent (2 bytes, network
byte order). The total length of the data field is thus 12 bytes for
IPv4 and 36 bytes for IPv6.
Data = src-ip (4 or 16 bytes) | src-port (2 bytes) |
dst-ip (4 or 16 bytes) | dst-port (2 bytes)
The Notify Message Type for this message is TBD-BY-IANA8. The
Protocol ID and SPI Size fields are set to zero.
----------------------------------------------------------------------
For 11 change: (there is also some half-written sentence there that I
fixed at the same time)
----------------------------------------------------------------------
MOBIKE introduces the NO_NATS_ALLOWED notification that is used to
detect modification, by outsiders, of the addresses in the IP header.
Such modifications can only be performed by attackers who are on the
path and capable of modifying the When this notification is used,
communication through NATs and other address translators is
impossible, so it is sent only when not doing NAT Traversal.
----------------------------------------------------------------------
to
----------------------------------------------------------------------
MOBIKE introduces the NO_NATS_ALLOWED notification that is used to
detect modification, by outsiders, of the addresses in the IP
header. When this notification is used, communication through NATs
and other address translators is impossible, so it is sent only
when not doing NAT Traversal. One of the main uses for this feature
is the IPv6 networks.
----------------------------------------------------------------------
For 12 change:
----------------------------------------------------------------------
MOBIKE address updates and ADDITIONAL_IP4/6_ADDRESS notifications
reveal information about which networks the peers are connected to.
----------------------------------------------------------------------
to
----------------------------------------------------------------------
MOBIKE address updates and ADDITIONAL_IP4/6_ADDRESS notifications
reveal information about which networks the peers are connected to.
Note, that this information is only available to the other peers,
not to the passive listeners of the traffic.
----------------------------------------------------------------------
--
[email protected]