Transcript • IEEE 802.21 MEDIA INDEPENDENT HANDOVER • DCN:21-06-068500-0000 • Title: IETF Liaison Report • Date Submitted: July 20, 2006 • Presented at IEEE 802.21

• IEEE 802.21 MEDIA INDEPENDENT HANDOVER
• DCN:21-06-068500-0000
• Title: IETF Liaison Report
• Date Submitted: July 20, 2006
• Presented at IEEE 802.21 session in San Diego
• Authors or Source(s):
• Yoshihiro Ohba
• Abstract: This is IETF Liaison Report on July 2006
21-06-0685-00-0000
IEEE 802.21 presentation release statements
• This
document has been prepared to assist the IEEE 802.21 Working Group. It
is offered as a basis for discussion and is not binding on the contributing
•
•
individual(s) or organization(s). The material in this document is subject to
change in form and content after further study. The contributor(s) reserve(s)
the right to add, amend or withdraw material contained herein.
The contributor grants a free, irrevocable license to the IEEE to incorporate
material contained in this contribution, and any modifications thereof, in the
creation of an IEEE Standards publication; to copyright in the IEEE’s name
any IEEE Standards publication even though it may include portions of this
contribution; and at the IEEE’s sole discretion to permit others to reproduce in
whole or in part the resulting IEEE Standards publication. The contributor also
acknowledges and accepts that this contribution may be made public by IEEE
802.21.
The contributor is familiar with IEEE patent policy, as outlined in Section 6.3
of
the
IEEE-SA
Standards
Board
Operations
Manual
<http://standards.ieee.org/guides/opman/sect6.html#6.3>
and
in
Understanding Patent Issues During IEEE Standards Development
http://standards.ieee.org/board/pat/guide.html>
21-06-0685-00-0000
MIPSHOP WG
• Revised MIPSHOP charter approved – containing MIH protocol transport
support
• 802.21 D01.00 review completed on May 22, 2006 -- no comment received
• IETF66 in July, 2006
• MIH problem statement draft
•
•
•
•
•
•
draft-hepworth-mipshop-mih-problem-statement-02
Containing the official MIH transport requirements from 802.21 WG
Trying to support multiple Mobility Support Services including MIH
Will be a WG draft
•
•
draft-hepworth-mipshop-mih-design-considerations-00.txt
Addressing detailed issues
•
MIH over UDP
MIH design considerations draft
Three MIH transport proposals in total, the 1st two are new drafts
– draft-rahman-mipshop-mih-transport-00.txt
•
MIH over GIST (General Internet Signaling Protocol)
•
MIH over DHCP (for IS only)
– draft-hancock-mipshop-gist-for-mih-00.txt
– draft-jang-mipshop-nhdisc-00.txt
•
•
Other MIH related draft in MIPSHOP WG
•
Network Initiated Handovers PS (draft-melia-mobopts-niho-ps)
•
IS server discovery using DHCP (draft-daniel-dhc-mihis-opt-01.txt)
Other MIH related draft in DHC WG
• Possible next step: 802.21 WG review of MIH-related MIPSHOP WG drafts
21-06-0685-00-0000
DNA WG
• “Link-layer Event Notifications for DNA” draft (draft-ietf-dnalink-information-03.txt) is already submitted to the IESG
• There were some concerns raised about the presence of link
down events in the link-information draft
• DNAv4 will ignore link down events, and generating such
events would actually be harmful to operating systems or
applications that tear down connections on receipt of "link
down" events
• It is proposed to remove link down event info from the
document
• 802.21 is not mentioned in the link-information draft
• AD’s comment: Once DNA WG finishes most of what it is
working on now and there are proposals that talk about
details and motivation for 802.21 support, they can work on
it
21-06-0685-00-0000
2nd HOAKEY BOF in IETF66





Three topics were presented:
 EAPext, Pre-authentication, Handover keying
Discussion on high-level requirements
 Inter-technology handover must be supported
 Inter-domain handover must be supported
There was a clear consensus on forming a new WG
 A new WG is most likely to be formed before IETF67
Needs discussion on detailed requirements over mailing list
Possible next step in 802.21 WG: write-up problem statement on
media-independent pre-authentication and key management and run
a motion on creating a Study Group in the next interim in September
21-06-0685-00-0000
Persistent URL for 802.21 IS Basic Schema
• IANA indicated that they can allocate a persistent URL for 802.21 Basic
Schema which is an RDF schema
• IANA RDF schema registry:
•
•
•
http://www.iana.org/assignments/xml-registry/rdfschema.html
What is registered: (ID, URI, Filename, Reference)
Allocation policy for RDF schema [RFC3688]: First Come First Serve,
with Specification Required
•
“Specification Required - Values and their meaning must be documented in an RFC
or other permanent and readily available reference, in sufficient detail so that
interoperability between independent implementations is possible.”
• IANA suggested writing an Information RFC for 802.21 Basic Schema
• IANA also contacted to IESG on this issue
• IESG do not think that the community will comment or suggest changes
that the authors will have to accept
• If the community comments anyway, the IEEE WG can decide whether
or not to take the comments on board
• Next step: Writing-up an Informational RFC on the Basic Schema after
Sponsor Ballot
21-06-0685-00-0000