Flow Bindings Initiated by Home Agents for Mobile IPv6
RFC 7109

Forgot to submit the review comment to the tracker.

IESG/Authors:

IANA has reviewed draft-yokota-mext-ha-init-flow-binding-06. Authors should review the comments and/or questions below. Please report any inaccuracies and respond to any questions as soon as possible.

IANA has questions about the requested actions in this draft document.

IANA understands that, upon approval of this document four IANA actions are required to be completed.

First, in the Mobility Header Types - for the MH Type field in
the Mobility Header registry located at:

http://www.iana.org/assignments/mobility-parameters

a new Mobility Header Type is to be registered as follows:

Value: [ TBD-at-registration ]
Description: Flow Binding Messages
Reference: [ RFC-to-be ]

QUESTION: Is Flow Binding Messages the name for the new requested
Mobility Header Type?

Second, in the Mobility Options registry in the Mobility Header
registry located at:

http://www.iana.org/assignments/mobility-parameters

two new Mobility Options are to be registered as follows:

Value: [ TBD-at-registration ]
Description: Flow Binding Initiate
Reference: [ RFC-to-be ]

Value: [ TBD-at-registration ]
Description: Flow Binding Acknowledge
Reference: [ RFC-to-be ]

QUESTION: Section 9 has a new requested Mobility Option as "Flow
Binding Initiate". But we cannot locate the new option anywhere
else in the draft document. A term "Flow Binding Indication" is
mentioned throughout the document. Is Flow Binding Initiate
another way referenced to Flow Binding Indication?

QUESTION: Sections 6.1.1. Flow Binding Indication and 6.1.2. Flow
Binding Acknowledgement have trigger values and status values defined.
Are these merely informational definitions for readers? The authors
request IANA-TBD1 through IANA-TBD3 in the IANA Considerations
section.

IANA understands that these two actions are the only ones that need
to be completed upon approval of this document.

Note: The actions requested in this document will not be completed
until the document has been approved for publication as an RFC.
This message is only to confirm what actions will be performed.