IST-2000-25153 Deliverable D15 Update Reviews of status of relevant standards Contractual Date of Delivery to the European Commission: December 2002 Actual Date of Delivery to the European Commission: January 2003 Editor(s): S Rao (Telscom) Participant(s): Telscom, UCL, BT, 6WIND, UoS Workpackage : 2 Title of Deliverable: Update Reviews of status of relevant standards Security: Public Nature: Report Version: Final Number of pages: 57 Abstract: The 6WINIT project participated in multiple standards activities and provided contributions both in IETF for IPv6 related technical issues and in CEN for healthcare related activities. They have adopted multiple on-going standards in their developments. This deliverable is a revised version of deliverable D4, addressing the status of standards that are related to wireless Internet, IPv6 and healthcare. The status of such standards is reviewed and ongoing work is identified which may impact the future work of wireless networks supporting both data and real time applications such as voice and video. Keywords: Mobile IP, IPv6, Wireless Internet, Standards, Healthcare, Tele-medicine Deliverable 15 Update Reviews of status of relevant standards V.1 6WINIT/0045 Table of Contents 1 INTRODUCTION ............................................................................................................................ 3 2 STATUS OF STANDARDS ............................................................................................................. 4 2.1 2.2 2.3 2.4 2.5 3 IPv6 standards .......................................................................................................................... 4 2.1.1 Deployment issues .......................................................................................................... 6 2.1.2 IPv6 address allocation issues ........................................................................................ 6 Mobile IP standards .................................................................................................................. 8 2.2.1 MIPv6............................................................................................................................. 8 2.2.2 Results achieved in IETF meeting of November 2002 in the MIPv6 group ..................... 10 2.2.3 Access Networks ........................................................................................................... 14 2.2.4 Wide Area Networks ..................................................................................................... 15 Fixed wireless networks: Transition to IPv6 based mobile networks........................................ 17 2.3.1 V6ops has already two Internet working drafts.............................................................. 17 Health Informatics standards................................................................................................... 18 2.4.1 CEN standards ............................................................................................................. 18 2.4.2 Health Information Systems Architecture ...................................................................... 19 2.4.3 Health Level 7 .............................................................................................................. 20 2.4.4 Standards for Images .................................................................................................... 20 2.4.5 Data Protection Legislation .......................................................................................... 21 2.4.6 Security Standards ........................................................................................................ 22 Discussion .............................................................................................................................. 22 ONGOING WORK IN IETF .......................................................................................................... 24 3.1 3.2 3.3 Introduction ............................................................................................................................ 24 Interaction of Transition Mechanisms ..................................................................................... 24 3GPP-IPv6 Design Team ........................................................................................................ 25 4 SUMMARY .................................................................................................................................... 27 5 PERSPECTIVE OF WIRELESS INTERNET EVOLUTION ..................................................... 28 ANNEX: STANDARDS AND WORKING DOCUMENTS................................................................... 29 Health related standards.................................................................................................................... 29 IPv6 Documents ............................................................................................................................... 30 IPv6 Core Protocols ............................................................................................................... 30 Addressing and Routing.......................................................................................................... 32 Multihoming ........................................................................................................................... 36 Supporting Protocols, MIBs and APIs..................................................................................... 37 IPv6 Operations / Transition Mechanisms .............................................................................. 40 Mappings to Lower Layers...................................................................................................... 43 Mobility.................................................................................................................................. 44 3GPP/ETSI standards ....................................................................................................................... 47 6 ACKNOWLEDGEMENTS: .......................................................................................................... 48 7 ACRONYMS AND ABBREVIATIONS........................................................................................ 49 19-Jan-03 http://folk.uio.no/paalee/ 6WINIT – IPv6 Wireless Internet IniTiative Page 2 of 57 Deliverable 15 1 Update Reviews of status of relevant standards V.1 6WINIT/0045 INTRODUCTION The 6WINIT project follows two sets of standards in its work, one related to IPv6 and mobile internet and the other related to health related standards. For IPv6 issues, the main standards organisations considered are IETF, 3GPP, UMTS Forum, ETSI, and ITU. IETF is the main specifications development group and ETSI provides a platform for testing during the plugtest events organised regularly. 3GPP (under the umbrella of ETSI) is the main working group working for early specifications development of 3rd generation mobile networks with IPv6 as a chosen protocol. ITU has taken up the issue of IPv6 in their activities within study group 13. and the liaison has been established between IETF, ETSI, 3GPP and IPv6 forum for harmonised activity. However, IETF is the main body which is working towards IPv6 specifications development, which are addressed in this deliverable. Health standards followed are from CEN (Comité Européen de Normalisation) Technical Committee 251, which addresses the Electronic Health Records (EHR) and HL7 an American standards group for health system architecture. Both CEN and ANSI have adopted DICOM specifications for image communication standards which are adopted for medical image communication, with security which is another important issue of health records related communication from CEN. 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 3 of 57 Update Reviews of status of relevant standards Deliverable 15 2 V.1 6WINIT/0045 STATUS OF STANDARDS The IETF working group for Next Generation Internet Protocol (IPng) is responsible for developing the IPv6 standards within IETF (http://www.ietf.org/). There are number of working areas related with 6WINIT activities. They are (but not limited to): • Internet area Ø IPv6: IP Version 6 Working Group Ø Mobile IP: IP Routing for Wireless/Mobile Hosts Ø Nemo: Network Mobility Ø Dnsext: DNS Extensions • Operation and management area Ø Ngtrans: Next generation transition Ø Multi6: Site Multihoming in IPv6 Ø V6ops: IPv6 operations • Routing Area Ø MANET: Mobile Ad-hoc Networks Ø RIP: Routing Information Protocol Ø Bgmp: Border Gateway Multicast Protocol • Security Area Ø IPSec: IP security protocol • Transport Area Ø Diffserv: Differentiated services Ø Megaco: Media Gateway Control Ø Midcom: Middlebox Communication Ø SIP: Session Initiation Protocol The issues range from header format and functions association, addressing and routing issues, Quality of service and security, transition mechanisms, and design issues for interworking across internetworks. IPv6 specifications development has become a central issue in recent meetings of IETF. There is already a number of RFCs available which have been approved and others are in the process of development. Similarly the GPRS Forum, UMTS forum and 3GPP bodies are driving the mobile IP standards incorporating IPv6 into future networks. Partners in 6WINIT are following both these areas. Since health care applications are part of 6WINIT, the project also followed standards in the fields of Health Informatics, principally those developed by CEN/TC 251, ISO/TC 215 and HL7. 2.1 IPv6 standards Many issues related to IPv6 have been finalised and the standards for commercial implementation of IPv6 production networks is possible today with the approved standards. However, there are further 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 4 of 57 Deliverable 15 Update Reviews of status of relevant standards V.1 6WINIT/0045 specifications addressing the address allocation (as a policy issue), renumbering, DHCP, DNS, anycast, multihoming, autoconfiguration, security and quality of services issues which are yet to be resolved. These issues are currently being discussed in the IPv6 working groups in the framework of the IETF. The Annex lists a number of IPv6 related RFCs from IETF. Since the standards of IPv6 are mature enough to start deploying for commercial exploitation, IETF has decided to launch a special IPv6 operations working group: V6ops. The charter of this group is as follows: The global deployment of IPv6 is underway, creating an IPv4/IPv6 Internet consisting of IPv4-only, IPv6-only and IPv4/IPv6 networks and nodes. This deployment must be properly handled to avoid the division of the Internet into separate IPv4 and IPv6 networks while ensuring global addressing and connectivity for all IPv4 and IPv6 nodes. The IPv6 Operations Working Group (v6ops) develops guidelines for the operation of a shared IPv4/IPv6 Internet and provides guidance for network operators on how to deploy IPv6 into existing IPv4-only networks, as well as into new network installations. The v6ops working group[http://www.ietf.org/html.charters/v6ops-charter.html] will: 1. Solicit input from network operators and users to identify operational or security issues with the IPv4/IPv6 Internet, and determine solutions or workarounds to those issues. This includes identifying standards work that is needed in other IETF WGs or areas and working with those groups/areas to begin appropriate work. These issues will be documented in Informational or BCP RFCs, or in Internet-Drafts. For example, important pieces of the Internet infrastructure such as DNS, SMTP and SIP have specific operational issues when they operate in a shared IPv4/IPv6 network. The v6ops WG will cooperate with the relevant areas and WGs to document those issues, and find protocol or operational solutions to those problems. 2. Provide feedback to the IPv6 WG regarding portions of the IPv6 specifications that cause, or are likely to cause, operational or security concerns, and work with the IPv6 WG to resolve those concerns. This feedback will be published in Internet-Drafts or RFCs. 3. Publish Informational RFCs that help application developers understand how to develop IP version-independent applications. Work with the Applications area, and other areas, to ensure that these documents answer the real-world concerns of application developers. This includes helping to identify IPv4 dependencies in existing IETF application protocols and working with other areas and/or groups within the IETF to resolve them. 4. Publish Informational or BCP RFCs that identify potential security risks in the operation of shared IPv4/IPv6 networks, and document operational practices to eliminate or mitigate those risks. This work will be done in co-operation with the Security area and other relevant areas or working groups. 5. Publish Informational or BCP RFCs that identify and analyse solutions for deploying IPv6 within common network environments, such as ISP Networks (including Core, HFC/Cable, DSL & Dial-up networks), Enterprise Networks, Unmanaged Networks (Home/Small Office), and Cellular Networks. These documents should serve as useful guides to network operators and users on how to deploy IPv6 within their existing IPv4 networks, as well as in new network installations. 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 5 of 57 Update Reviews of status of relevant standards Deliverable 15 V.1 6WINIT/0045 6. Identify open operational or security issues with the deployment scenarios documented in (5) and fully document those open issues in Internet-Drafts or Informational RFCs. Work to find workarounds or solutions to basic, IP-level operational or security issues that can be solved using widelyapplicable transition mechanisms, such as dual-stack, tunnelling or translation. If the satisfactory resolution of an operational or security issue requires the standardisation of a new, widely-applicable transition mechanism that does not properly fit into any other IETF WG or area, the v6ops WG will standardise a transition mechanism to meet that need. 7. Assume responsibility for advancing the basic IPv6 transition mechanism RFCs along the standards track, if their applicability to common deployment scenarios is demonstrated in (5) above: • Transition Mechanisms (RFC 2893) • SIIT (RFC 2765) • NAT-PT (RFC 2766) • 6to4 (RFC 3056 & 3068) This includes updating these mechanisms, as needed, to resolve problems. 2.1.1 Deployment issues 2.1.1.1 Moving from 6bone to IPv6 Internet Internet draft : http://www.ietf.org/internet-drafts/draft-savola-v6ops-6bone-mess-01.txt Currently, IPv6 Internet is, globally considered, inseparable from the 6bone network. The 6bone has been built as a tightly meshed tunnelled topology. As the number of participants has grown, it has become an intangible mess, hindering the real deployment of IPv6 due to low quality of connections. This memo discusses the nature and the state of 6bone/IPv6 Internet, points out problems and outlines a few ways to start fixing them; also, some rough operational guidelines for different-sized organisations are presented. The most important issues are: not offering transit to everyone and real transit operators being needed to take a more active role. ETSI is supporting early testing of implementation of these standards by organising interoperability testing among multivendor equipment available from different sources. The last plugtest was conducted in September 2002 in Sophia Antipolis interconnected to NGNLAB premises in Brussels. The next plugtest is expected in Madrid jointly with the IPv6 summit event. 2.1.2 IPv6 address allocation issues 2.1.2.1 IETF working group IP Version 6 Addressing Architecture This IETF working group is working on the Addressing architecture and the corresponding internet draft can be seen at http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-addr-arch-v3-11.txt This specification defines the addressing architecture of the IP Version 6 protocol [IPV6]. The document includes the IPv6 addressing model, text representations of IPv6 addresses, definition of 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 6 of 57 Update Reviews of status of relevant standards Deliverable 15 V.1 6WINIT/0045 IPv6 unicast addresses, anycast addresses, and multicast addresses, and an IPv6 node's required addresses. This document obsoletes RFC 2373 "IP Version 6 Addressing Architecture". Site-local addresses Site-local addresses are defined in the address architecture and approved by the IESG, the address selection document defines the selection rules and is in the RFC Editor Queue; work is ongoing on the Node Requirements and the Scoped Address Architecture documents. Despite all this, there are many concerns about site local addresses including how to implement and manage site border routers, how to deal with multi-site routers and multi-site hosts, as well as the implications for DNS and applications. During a lively debate, the IPv6 WG showed some consensus to continue with sitelocals as specified but to restrict usage to either ‘limited’ usage or ‘moderate’ usage. Documents defining these terms are being written to allow the WG to make a final decision on how to proceed with site-locals as currently specified. Many people have also expressed a desire for an additional chunk of address space that would be globally-unique and provider independent. Debate about whether this address space should be routable or not, and what degree of uniqueness is actually required is ongoing. This parallel address space will be very important for any IPv6 multihoming solution. 2.1.2.2 RIPE The RIPE-246 document provides the new IPv6 address allocation policy based on the ‘sparse allocation’ algorithm. The details can be found at http://www.ripe.net/ripe/docs/ipv6-sparse.html This document provides the management process for IPv6 global unicast address space whereby address allocations are made from a single global pool according to a "sparse allocation" algorithm. This allocation process will maximise aggregation of address space, ensuring that most ISPs retain a single prefix as they grow, and avoiding the address space fragmentation which results from the current IPv4 allocation technique. This document also describes the registration process and the administration of the IP6.ARPA domain. The addressing policy is based on licensing for a limited period (and not considered as property), and renewed automatically if criteria are justified. The goal is to have aggregation as more important than conservation with minimum administrative overhead and at the same to encourage the deployment. Assignment size follows the rules : • Assignment size for all -/48 • Smaller size -/64 for one subnet and -/128 for one device • Very large end users may receive multiple -/48, but in this case approval is needed • Assignment to operator’s infrastructure: -/48 for PoP • Every -/48 must be registered in the RIPE database Other important RIPE documents of interest are: 19-Jan-03 • IPv6 policy for IX points (Ripe- 224) • IPv6 addresses for Root servers (Ripe – 233) 6WINIT – IPv6 Wireless Internet IniTiative Page 7 of 57 Update Reviews of status of relevant standards Deliverable 15 2.2 V.1 6WINIT/0045 Mobile IP standards Since the IETF working group on mobile standards has 2 interest groups for working on IPv6 and IPv4, it has been proposed that the MobileIPv6 WG will be split into two WGs – one focussed on Mobile IP deployment (mipdep) and the other on MobileIPv6 (mIPv6). 2.2.1 MIPv6 Draft 19 was submitted at the end of Oct. 2002 and was adopted in the November meeting. Draft 20 is progressing with number of additional issues clarified. The detailed list of issues in draft 19 and 20 can be seen at http://www.piuha.net/~jarkko/publications/mipv6/MIPv6-Issues.html The list below shows the issues adopted in Draft 19: 19-Jan-03 • Preferred vs. valid lifetimes • MH Type unknown and bad source address • De-reg and failure • Separate authorisation away from home agent IPSec • Requirements section nits and missed requirements • Inconsistent RA and prefix rules • Multiple tries to different HAs and DAD • Sending BA errors conflict 9.4.1/9.4.4 • MPA, MPS security requirement • 9.4.1 and 11.7.2 text in conflict about HAO in CN BUs • Conflicts between Sections 5.2.6 and 11 • Rate limiting for RR not necessary • Clarify "correspondent node address" and "BU" for BAD calculation • Refer to draft-mkhalil-ipv6-fastra-02.txt • No need to change nonce/Kcn if not used • Mauro Tortonesi's editorial comments • More editorial comments from Vesa-Matti Mantyla • Rate limiting vs. exponential back-off • RH processing order inconsistency • MPA security resolution is not in draft 18 • Need DHAAD and MPS/MPA security story in Sect.14 • More editorial comments from Vesa-Matti Mantyla • Remove UID? • Unclear issues in MPA 6WINIT – IPv6 Wireless Internet IniTiative Page 8 of 57 Update Reviews of status of relevant standards Deliverable 15 V.1 • Both cookies expired -status code • BRR response when deleting BCE: lifetime or home address? • Make BAD the last option • Editorial comments from Vesa-Matti Mantyla • Home bindings when L=0 • MPA editorial issues • Unclear authenticator coverage part • State machine problem, missing Start RR • 6.2.7 claims only BUs have BADs • Cookie lifetime clarifications needed • Clarifications for Section 5 • Missing requirements in Section 8 • Editorial review comments from Samita Chakrabarti • Binding Refresh Advice type number wrong • Unclear references to RH (type 0 or 2) • Unclear text about "address suitable for RH" • MH length to include first 8 bytes or not • Reflection attack using BUs and BAs • Status field value inconsistencies • Clarify whether to use HAO or IPv6 Src for checksum • BA length and padding wrong • References to the refresh field still exist 6WINIT/0045 The current implementation from the vendors (e.g. 6WIND) used in 6WINIT is compliant with MIPv6 draft 13. Major changes have been proposed by the IETF to the MIPv6 features since the publication of this draft. For instance, the current draft (19) now includes security features. These features have to be integrated in the near future in order to be compliant with the current draft. The main objective of Mobile IPv6 is to avoid communications being broken even when people are moving (e.g. roaming from a wireless cell associated with one IP network to another). While the IP networks like Internet are including more and more mobile and wireless applications, Mobile IPv6 represents a great opportunity for IPv6 to cope with the new behaviour of users that are now utilising Internet from their hand-held devices. Studies of the new draft (currently 19) and specifications of the changes required from draft 13 are in progress within the developers' team. It should be noted the current IETF specification has become more mature because very few topics remain open. In addition, the security issue now based on a method called “Return Routability” seems stabilised. 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 9 of 57 Deliverable 15 Update Reviews of status of relevant standards V.1 6WINIT/0045 2.2.2 Results achieved in IETF meeting of November 2002 in the MIPv6 group 2.2.2.1 MIPv6 Care of Address Option : http://www.ietf.org/internet-drafts/draft-oneill-mipv6-cao-00.txt IPv6 and MIPv6 has constrained the HoA to being used within forward and reverse tunnels via the HA. In the unicast case, the MN can then activate Route Optimisation to bypass the HA in both directions by securely installing a Binding Cache Entry into the CN. The MN then sends from the CCoA source address to the CN directly into the foreign multicast system, and includes the Home Address Option (HAO) so that the changing CCoA is masked from the transport layer. This draft defines the Care of Address Option, which carries the current CCoA of the MN. The CAO can be included in a Hop By Hop Header or Destination header and used instead of the packet source address for unicast ingress filtering and multicast RPF purposes. This enables a MN to potentially use the HoA as a source address on the foreign network, and to inform the CNs of the evolving MN location. 2.2.2.2 IPv6 Anycast Binding using Return Routability http://www.ietf.org/internet-drafts/draft-haberman-ipv6-anycast-rr-00.txt Today, the use of IPv6 anycast is limited. This document proposes a mechanism by which TCP/SCTP and stateful protocols using UDP can securely discover the mapping from an anycast address to a unicast address that can be used until a failure is detected. The mechanism reuses the Mobile IPv6 Return Routability and Binding Update mechanism. 2.2.2.3 Localized Key Management for AAA in MobileIPv6 http://www.ietf.org/internet-drafts/draft-mun-aaa-localkm-mobileipv6-00.txt This document describes a way to distribute secure key for optimising AAA authentication procedure while a mobile node is away from it's home. The AAA infrastructure is used as an underlying framework which enables a Mobile-IPv6 node to get an global authentication by identifying it with an unique identifier NAI. The Diameter messages are exchanged to transfer information of mobile node between home and foreign AAA servers. The steps to complete an authentication steps for mobile node in the visited link may be reduced by delegating the role for generating and synchronising keys to AAA server in the visited domain. The implications to existing entities supporting mobility such as attendant, AAA server in home and visited domain are discussed. 2.2.2.4 Taxonomy of Route Optimisation Models in the NEMO Context http://www.ietf.org/internet-drafts/draft-thubert-nemo-ro-taxonomy-00.txt Nemo enables Mobile Networks by extending Mobile IP to support Mobile Routers. This paper documents how the MIPv6 concept of Route Optimisation can to be adapted for Nemo to optimise: 19-Jan-03 1. the nested tunnels of the nested Nemo configuration 2. router-to-router within the infrastructure as opposed to end-to-end. and much more .. 6WINIT – IPv6 Wireless Internet IniTiative Page 10 of 57 Deliverable 15 2.2.2.5 Update Reviews of status of relevant standards V.1 6WINIT/0045 Diameter Mobile IPv6 Application http://www.ietf.org/internet-drafts/draft-le-aaa-diameter-mobileipv6-02.txt Mobile IPv6 capable mobile nodes can roam between networks that belong to their home service provider as well as others. Roaming in foreign networks is enabled as a result of the service level and roaming agreements that exist between operators. One of the key protocols that allow this kind of a roaming mechanism to be enabled is Diameter. This Internet Draft specifies a new application to Diameter that enables Mobile IPv6 roaming in networks other than its home. 2.2.2.6 Global Connectivity for IPv6 Mobile Ad Hoc Networks http://www.ietf.org/internet-drafts/draft-wakikawa-manet-globalv6-02.txt This document describes how to provide Internet connectivity with mobile ad-hoc networks. It describes how to obtain a globally routable address, Manet node operation, and Internet-gateway operation. Once a Manet node obtains a global address from an Internet-gateway, it can start to send data to the Internet. Data goes through the Internet-gateway with a routing header specifying the gateway. This connectivity method is not dependent on a particular Manet protocol. Further, use of global connectivity with Mobile IPv6 is specified. 2.2.2.7 Fast Handovers for Mobile IPv6 http://www.ietf.org/internet-drafts/draft-ietf-mobileip-fast-mipv6-05.txt Mobile IPv6 describes how a Mobile Node can maintain connectivity to the Internet when it changes its Access Router for another, a process referred to as handover. During this process, there is a time period when the Mobile Node is unable to send or receive IPv6 packets both due to link switching delay and IP protocol operations. This time period is referred to as handover latency. In many instances, the handover latency resulting from standard Mobile IPv6 handover procedures could be greater than what is acceptable to support real-time or delay sensitive traffic. Furthermore, reducing the handover latency could be beneficial to non-real time, throughput-sensitive applications as well. The intent of this document is to describe protocol enhancements to reduce handover latency due to IP protocol operations as small as possible in comparison to the inevitable link switching latency. 2.2.2.8 Mobility Support in IPv6 http://www.ietf.org/internet-drafts/draft-ietf-mobileip-ipv6-19.txt This document specifies the operation the IPv6 Internet with mobile computers. Each mobile node is always identified by its home address, regardless of its current point of attachment to the Internet. While situated away from its home, a mobile node is also associated with a care-of address, which provides information about the mobile node's current location. IPv6 packets addressed to a mobile node's home address are transparently routed to its care-of address. The protocol enables IPv6 nodes to cache the binding of a mobile node's home address with its care-of address, and to then send any packets destined for the mobile node directly to it at this care-of address. To support this operation, Mobile IPv6 defines a new IPv6 protocol and a new destination option. All IPv6 nodes, whether mobile or stationary, MUST support communications with mobile nodes. 2.2.2.9 Mobile IPv6 VPN using Gateway Home Agent http://www.ietf.org/internet-drafts/draft-ohnishi-mobileip-v6vpngateway-01.txt Mobile IPv6 [Mobile IPv6] provides mobility functions for IPv6. It can also be used for public mobility services. One of the most important services is the VPN service enabling users to access their Intranets from outside. Mobile IP does not work well with VPN, however, and this issue is being discussed in the Mobile IP WG [VPN problem]. This document proposes a simple mechanism 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 11 of 57 Deliverable 15 Update Reviews of status of relevant standards V.1 6WINIT/0045 that combines VPN and Mobile IP functions. This mechanism uses a hierarchical HA architecture and includes an HA with GW functions, called a Gateway Home Agent (GHA). 2.2.2.10 Hierarchical MIPv6 mobility management (HMIPv6) http://www.ietf.org/internet-drafts/draft-ietf-mobileip-hmipv6-07.txt This draft introduces extensions to Mobile IPv6 and IPv6 Neighbour Discovery to allow for local mobility handling. Hierarchical mobility management for Mobile IPv6 reduces the amount of signalling between the Mobile Node, its Correspondent Nodes and its Home Agent. The Mobility Anchor Point described in this document can also be used to improve the performance of Mobile IPv6 in terms of handoff speed. 2.2.2.11 IPv6 Fast Router Advertisement http://www.ietf.org/internet-drafts/draft-mkhalil-ipv6-fastra-02.txt This document specifies an amendment to the router solicitation handling procedures in RFC 2461 that allow for improved default router acquisition performance when an active IP host moves from one subnet to another. 2.2.2.12 Securing MIPv6 Binding Updates Using Address Based Keys (ABKs) http://www.ietf.org/internet-drafts/draft-okazaki-mobileip-abk-01.txt This document outlines a method for authenticating and authorising Mobile IPv6 [MIPv6] Binding Updates between a Correspondent Node and a Mobile Node where there exists no pre-established direct or indirect security relationship between those two entities. The method uses a new security technique called Address Based Keys. Address Based Keys are an alternative to other cryptographic address mechanisms for optimising Binding Update security to avoid the need for Return Routability checks on each binding update. Address Based Keys use some mathematical results in identity based cryptosystems that have been known to cryptographers for some time, but have not been widely discussed in the network security community. 2.2.2.13 Hop-by-Hop Local Mobility Agents Probing for Mobile IPv6 http://www.ietf.org/internet-drafts/draft-vriz-mobileip-hbhlmap-01.txt This document introduces an extension to Mobile IPv6 to provide support for Localised Mobility Management. This proposed Hop-by-Hop Local Mobility Agents Probing scheme specifies the Local Mobility Agent's Discovery, Selection and Failure Detection architecture and procedures for deploying the localised mobility management, whereby the Local Mobility Agents are distributed. It reduces the amount of signalling to the home agent and correspondent nodes when mobile node moves among the subnets of the visited domain. 2.2.2.14 IPv6 Reverse Routing Header and its application to Mobile Networks http://www.ietf.org/internet-drafts/draft-thubert-nemo-reverse-routing-header-01.txt Already existing proposals enable Mobile Networks by extending Mobile IP to support Mobile Routers. In order to enable nested Mobile Networks, some involve the overhead of nested tunnels between the Mobile Routers and their Home Agents. This proposal allows the building of a nested Mobile Network avoiding the nested tunnel overhead. This is accomplished by using a new routing header, called the reverse routing header, and by overlaying a layer 3 tree topology on the evolving Mobile Network. 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 12 of 57 Deliverable 15 2.2.2.15 Update Reviews of status of relevant standards V.1 6WINIT/0045 Using IPSec to Protect Mobile IPv6 Signalling between Mobile Nodes and Home Agents http://www.ietf.org/internet-drafts/draft-ietf-mobileip-mipv6-ha-ipsec-01.txt Mobile IPv6 uses IPSec to protect signalling between the home agent and the mobile node. Mobile IPv6 base document defines the main requirements these nodes must follow. This draft discusses these requirements in more depth, illustrates the used packet formats, describes suitable configuration procedures, and shows how implementations can process the packets in the right order. 2.2.2.16 Regional Mobile IPv6 mobility management http://www.ietf.org/internet-drafts/draft-suh-rmm-00.txt This document defines a new protocol, namely, Regional Mobile IPv6 mobility management (RMM/RMIPv6). RMM mechanism satisfies the LMM requirements while it is more flexible mobility management scheme than existing solution, for example HMIPv6. This document therefore describes methods to be used to reduce the amount of signalling to the Home Agent and Correspondent Nodes. In addition, this scheme is flexible enough to adapt to any network topology assumed by IPv6. The network using RMM/RMIPv6 is robust against the failure or the performance degradation. The mechanism is intended to reuse the Care of Address. Moreover, the forwarding tunnel length from an anchor point to a Mobile Node can be a controllable or configurable. 2.2.2.17 IPv6 over Mobile IPv4 http://www.ietf.org/internet-drafts/draft-mccann-mobileip-ipv6mipv4-03.txt This document specifies a Mobile IPv4 extension that may be used by dual stack mobile nodes to obtain IPv6 service with the use of a Mobile IPv4 registration. This extension allows for immediate deployment of IPv6 on dual stack mobile devices, without the need for a full IPv6 infrastructure. It is believed that providing IPv6 services to mobile devices in the short term will spur the growth of IPv6 networks. This extension makes use of the existing Mobile IPv4 security model, including the interface to the AAA infrastructure, but does not provide the route optimisation capabilities included in the Mobile IPv6 protocol. Further, this specification requires that the mobile node and Home Agent have dual IPv4 and IPv6 stacks. There are no changes to the FA nor does it need to be dual stack. 2.2.2.18 Improving the Architectural Alignment for FMIPv6 http://www.ietf.org/internet-drafts/draft-kempf-mobileip-fmipv6-sem-00.txt The FMIPv6 draft proposes a number of changes in the local link and routing information exchange architecture for wireless networks that are not quite aligned with standard IETF protocols, including the base MIPv6 protocol itself. This draft proposes modifications of FMIPv6 to tighten the semantics of anticipated care-of address configuration around the pre-handover signalling as a logical extension of Router Discovery, and around the HI/HAck exchange as a logical extension of routing information propagation. It also proposes some extensions to Router Discovery for reactive handover to piggyback signalling for quickly establishing a tunnel to the Previous Access Router on top of standard RFC 2461 Router Discovery signalling. 2.2.2.19 Mobile IPv6 Authentication, Authorisation, and Accounting Requirements http://www.ietf.org/internet-drafts/draft-le-aaa-mipv6-requirements-01.txt This document describes the motivation why Diameter support for Mobile IPv6 is required and needs to be developed. It analyses the requirements expressed in RFC 2977 which was written both for MIPv4 and MIPv6; and it finally updates the IPv6 requirements for the AAA support for Mobile IPv6 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 13 of 57 Deliverable 15 Update Reviews of status of relevant standards V.1 6WINIT/0045 to reflect the latest modifications and evolution of the Mobile IP, AAA and other relevant working groups. 2.2.2.20 RObust Header Compression (ROHC): A Compression Profile for Mobile IPv6 http://www.ietf.org/internet-drafts/draft-hwang-rohc-mipv6-00.txt The original RObust Header Compression (ROHC) RFC, RFC 3095, defines a framework for header compression, along with compression protocols (profiles) for IP/UDP/RTP, IP/ESP, IP/UDP, and also for uncompressed packet streams. And another draft [IPPROFILE] posted by Jonson deals with the IP only profile. However, no profile was defined for compression of IP extension headers. But in the coming wireless applications, mobile IP will play an important role. In mobile IPv4, there is no difference to the packet's IP header, so we do not have to make a profile for mobile IPv4; while as to mobile IPv6[MIPV6], there is difference, since some specific IPv6 extension headers will be included in almost every packet in the mobile IPv6 packets. The extension headers will also cost a lot of bandwidth, and we should do compression over them. This document addresses this issue and defines a ROHC compression profile for mobile IPv6, which may work as a complement to the profiles defined by RFC 3095. 2.2.3 Access Networks 6WINIT addresses end-to-end services across a mobile internet. Different types of access networks can be used including the fixed networks. The project addresses wireless access networks more. In this context, experiments have been conducted on wireless LAN based on 802.11b and Bluetooth access. 2.2.3.1 Wireless LAN 802.11 is a family of wireless networking protocols from the IEEE. The most popular of these is the 802.11b standard. which has been in commercial use since 1999. It has a maximum theoretical throughput of 11 Mbit/s, which is much faster than broadband solutions like DSL or cable modems. 802.11 Wavelan technology supports native IPv6 connectivity without any special adaptation. 2.2.3.2 Mobile IPv6 Fast Handovers for 802.11 Networks http://www.ietf.org/internet-drafts/draft-mccann-mobileip-80211fh-01.txt This document describes how a Mobile IPv6 Fast Handover [2] could be implemented on a link layers conforming to the 802.11 suite of specifications [3]. Existing WiFi NICs and APs are very different in their behaviour – not standardised – therefore it is very difficult to write portable code for the IP layer. The WG needs to decide whether this work should focus on existing 802.11 products, or some notion of future products that may implement an ‘exotic’ device driver with soft WiFi. 2.2.3.3 Bluetooth Bluetooth is a wireless communication technology using a frequency hopping scheme in the unlicensed 2.4 GHz ISM (Industrial-Scientific-Medical) band. Two or more Bluetooth (BT) units sharing the same channel form a piconet. Within a piconet a BT unit can have either of two roles: master or slave. Within each piconet there may be only one master (and there must always be one) and up to seven active slaves. Any BT unit can become a master in a piconet. 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 14 of 57 Update Reviews of status of relevant standards Deliverable 15 V.1 6WINIT/0045 The Bluetooth specification consists of different profiles for different applications. So far, only one profile exists which explicitly supports IP (v4 or v6). This is the LAN access profile, used between a laptop/PDA etc. and a LAN access point. The dial-up profile can also be used to transport IP. This profile is used between a laptop/PDA etc and e.g. a cellular phone or a modem. It also uses RFCOMM, and AT commands for dialling and control. It does not specify what protocols are used on top or RFCOMM, but clearly, PPP can be used as over any serial link/modem connection. In addition to this, a new profile will be published soon which is designed specifically for IP networking, the Personal Area Networking (PAN) profile. This profile does not use RFCOMM, but instead defines a new protocol, Bluetooth Network Encapsulation Protocol (BNEP), which is an Ethernet emulation layer. This means that any protocol that can run over Ethernet will be supported, such as IPv6. One important function in the PAN profile is that the master in a piconet will forward packets between its slaves, both unicast packets from one slave to another, and broadcast packets from one slave (or itself) to all the others, thus hiding the point-to-point nature of Bluetooth and making one piconet look like an Ethernet link. 2.2.4 Wide Area Networks The mobile internet addressed by the 6WINIT project can use all kinds of wide area networks: fixed, wireless or satellite. However, the project addresses mainly GPRS (which is available in many EU countries) and UMTS (when available) for trials. 2.2.4.1 GPRS GPRS is a new service designed for Global System for Mobile Communications (GSM) networks. GSM is a digital cellular technology that is used worldwide, predominantly in Europe and Asia, with current estimates of 400 million subscribers and growing. GSM is the world's leading standard in digital wireless communications. GPRS is standardised by the European Telecommunications Standards Institute (ETSI). The most common application of GPRS is expected to be Internet/intranet access. GPRS enables mobile wireless service providers to supply their mobile subscribers with packet-based data services in GSM networks with permanent connection to the network. GPRS introduces the following two new major network elements: • SGSN—Sends data to and receives data from mobile stations, and maintains information about the location of a mobile station (MS). The SGSN communicates between the MS and the GGSN • GGSN—A wireless gateway that allows mobile cell phone users to access the public data network (PDN) or specified private IP networks. With introductory plans of 3G delayed, GPRS is becoming an intermediate step for mobile data network deployment. GPRS is planned on IPv4 and uses the DHCP mechanism to reach several million customers. However, for providing secure services such as VPN on a mobile network combined with wireless LANs which is becoming commercial viable, the plan is to upgrade the GPRS system to IPv6. The transition strategies of this enhancement is being discussed in V6ops group and two internet drafts are under discussion identified in the next section. 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 15 of 57 Update Reviews of status of relevant standards Deliverable 15 2.2.4.2 V.1 6WINIT/0045 UMTS/3GPP UMTS is one of the major new third generation (3G) mobile systems being developed within the framework which has been defined by the International Telecommunications Union (ITU) and known as IMT-2000 (International Mobile Telecommunications). The 3rd Generation Partnership Project (3GPP) is a collaborative agreement among a number of telecommunications standards bodies such as ARIB, CWTS, ETSI, T1, TTA, and TTC. The scope of 3GPP is to produce globally applicable Technical Specifications and Technical Reports for a 3rd Generation Mobile System based on evolved GSM core networks and the radio access technologies that they support (i.e. Universal Terrestrial Radio Access (UTRA) both Frequency Division Duplex (FDD) and Time Division Duplex (TDD) modes). 3GPP has produced all necessary specifications adopted by ETSI and regional standards groups. The full list of 3GPP specifications can be seen at http://www.3gpp.org/ 3GPP specifications are continually being enhanced with new features. In order to provide developers with a stable platform for implementation while at the same time allowing the addition of new features, the 3GPP uses a system of parallel "releases". Release 5 specifications have been published with IPv6 as a mandatory protocol. However, 3GPP has two different architectures developed: 3GPP in Europe and 3GPP2 in U.S. There are significant differences between these architectures related to mobility management, call control, QoS/resource allocation, security and data management. These have created additional dependencies with IETF work. UMTS is being standardised by the European Telecommunications Standards Institute (ETSI) in the IMT-2000 framework, in co-operation with other regional and national standardisation bodies around the world to produce the detailed standards to satisfy growing market needs for global roaming and service availability. IMT-2000 has been defined by the ITU as an open international standard for a high capacity, high data rate mobile telecommunications system incorporating both terrestrial radio and satellite components. The IETF dependencies have been identified and their status is reported below. 3GPP IETF Dependencies and Priorities report can be found at: http://www.3gpp.org/TB/Other/IETF.htm From the report it can be seen that, out of 66 dependencies, 12 are late for Release 5, 35 are completed while the rest are for Release 6. Release 6 Status of Work Items after TSG-RAN #16: - Change of completion date agreed in the last meeting are as follows: 19-Jan-03 • Beamforming Enhancements is moved to March 2003 • Open interface between the SMLC and the SRNC within the UTRAN to support Rel-4 positioning methods also moved to March 2003 • Report Introduction of the Multimedia Broadcast Multicast Service (MBMS) in RAN due to be completed in June 2003 6WINIT – IPv6 Wireless Internet IniTiative Page 16 of 57 Update Reviews of status of relevant standards Deliverable 15 V.1 6WINIT/0045 • Radio link performance enhancements completion date moved to December 2003. • Fast Cell Selection (FCS) for HS-DSCH completion date is moved to March 2003. In the recent meeting held in Munich an ad hoc group to study the roadmap of 3GPP was set up. This 3GPP evolution ad-hoc group produces the initial version of a long-term high-level road map to guide the future work for 3GPP. The ad hoc group focuses on items, which are pertinent to the evolution of 3GPP specifications. The high-level road map is envisaged to be a "living document" that can be updated to reflect future developments and innovation as necessary. Collaboration of the 3GPP group with IETF was once again confirmed with the new liaison statement sent to IETF. The liaison statement is a response to IETF indicating that 3GPP supports the interoperability goals outlined in the IETF liaison and is undertaking to investigate what alignment can be done in the short term (Release 5). Also it indicates that 3GPP encourages future collaboration with IETF to address those interoperability issues that cannot be quickly addressed. Furthermore, 3GPP must ensure backwards compatibility between IMS releases. 2.3 Fixed wireless networks: Transition to IPv6 based mobile networks 2.3.1 V6ops has already two Internet working drafts 2.3.1.1 Transition Scenarios for 3GPP Networks This document describes different scenarios in Third Generation Partnership Project (3GPP) defined packet network, i.e. General Packet Radio Service (GPRS) that would need IPv6 / IPv4 transition. The focus of this document is on the scenarios where the User Equipment (UE) connects to nodes in other networks, e.g. in the Internet. 2.3.1.2 Analysis on IPv6 Transition in 3GPP Networks This document analyses the transition scenarios in 3GPP packet data networks that might come up in the deployment phase of IPv6. The transition scenarios are documented in [3GPP-SCEN] and this document will further analyse them. The scenarios are divided into two categories: GPRS scenarios and IP Multimedia core network System (IMS) scenarios. GPRS scenarios are the following: • Dual Stack UE connecting to IPv4 and IPv6 nodes • IPv6 User equipment (UE) connecting to an IPv6 node through an IPv4 network • IPv4 UE connecting to an IPv4 node through an IPv6 network • IPv6 UE connecting to an IPv4 node • IPv4 UE connecting to an IPv6 node Two IMS scenarios are: 19-Jan-03 • UE connecting to a node in an IPv4 network through IMS • Two IMS islands connected via IPv4 network 6WINIT – IPv6 Wireless Internet IniTiative Page 17 of 57 Update Reviews of status of relevant standards Deliverable 15 V.1 6WINIT/0045 The focus is on analysing different transition scenarios, applicable transition mechanisms and finding solutions for those transition scenarios. In the scenarios, the User Equipment (UE) connects to nodes in other networks. 2.3.1.3 QoS: Use of flow label in IPv6 header Debate during the recent IETF meeting centred on reducing the amount of text in the current draft (version 3) to make it as uncomplicated as possible. 2.3.1.4 IPv6 Flow Label Specification http://www.ietf.org/internet-drafts/draft-ietf-ipv6-flow-label-03.txt This document specifies the usage of the IPv6 Flow Label field, the requirements for IPv6 source nodes labelling flows, and the requirements for flow state establishment methods. Time out mechanism for flushing dynamically establishes flow state, but not on the application or transport stack assigning and using their own defined labels. The proposed time out is 10 seconds. The flow label should not give away information otherwise hidden in IPSec ESP. The usage of the Flow Label field enables efficient IPv6 flow classification based only on IPv6 main header fields in fixed positions. The specification draft needs considerable work to be done and, until then, the usage of flow label is open. 2.4 Health Informatics standards The 6WINIT London Demonstrator focuses on the distributed access to EHR information. The major health informatics standards applicable to EHR representation and secure communication originate from CEN (Comité Européen de Normalisation) Technical Committee 251. 2.4.1 CEN standards 2.4.1.1 ENV 13606: EHCR Communication (1999) This four-part pre-standard (ENV) [CEN] governs the representation of EHR information as it might be communicated between two repositories or between a client and a server. In its four parts, it defines: • the object model that must be used to represent the EHR; • a set of term lists that must be used to populate key attributes defining the classes of information being communicated; • a set of rules and an information model governing how access control requirements should be specified; • a set of message specifications to support message-based exchange (EDI), e.g. using EDIFACT or XML. CHIME (UCL) has been at the forefront internationally in the specification of information models needed to underpin the capture and communication of electronic health records (EHRs). The R&D results of research projects involving CHIME have largely underpinned this standard, and the UCL EHR middleware components closely match the standard. 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 18 of 57 Update Reviews of status of relevant standards Deliverable 15 V.1 6WINIT/0045 In December 2001, CEN TC/251 confirmed a new Task Force, known as “EHRcom”, to review and revise the 1999 four-part pre-standard ENV 13606 relating to Electronic Healthcare Record Communications. The intention of this work is to propose a revision that could be adopted by CEN as a formal standard (EN) during 2004. The Task Force has set out to base the revision of ENV 13606 on the practical experience that has been gained through commercial systems and demonstrator pilots in the communication of whole or part of patients’ EHRs. The overall mission statement of the EHR communications standard proposed by the Task Force is: "to produce a rigorous and durable information architecture for representing the EHR, in order to support the interoperability of systems and components that need to interact with EHR services: • as discrete systems or as middleware components; • to access, transfer, add or modify health record entries; • via electronic messages or distributed objects; • preserving the original clinical meaning intended by the author; • reflecting the confidentiality of that data as intended by the author and patient." A combination of good working relationships between CEN, openEHR [OpenEHR] and HL7 has led to an intention to harmonise the proposed new standard with both openEHR (reference model and archetype approach) and with HL7 (mainly the Clinical Document Architecture, discussed below). A member of CHIME has been invited to lead a new CEN Task Force to revise ENV13606 based on its experience in this field, to develop a definitive standard (EN). As this new standard and the UCL components evolve, the London Demonstrator is likely to provide an important reference implementation of the new standard. 2.4.2 Health Information Systems Architecture This 1999 standard, ENV 12967 [CEN], defines an open systems architecture facilitating the development of products and services by different vendors. It defines the structure for how healthcare information systems should be built, implemented and used. It specifies the interactions between hospital information systems, organisations & users, and the control, storage and manipulation of the different types of data in the various components of the system. HISA services are divided into: • Generic Common Services which would be found in the core information systems in any business domain; • Healthcare Common Services which are more specific to healthcare but common to most applications within healthcare: subject of care, activities, resources, authorisation, patient health characteristics. A new HISA Task Force was established in early 2002 to revise this standard, and this work is expected to be completed during 2003/04. 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 19 of 57 Update Reviews of status of relevant standards Deliverable 15 2.4.3 V.1 6WINIT/0045 Health Level 7 This US based international organisation, generally known as HL7 [HL7], is responsible for the most widely adopted standard for message-based communication in healthcare. HL7, whose message specifications were first published in 1988 as an industry standard, was awarded Standards Development Organisation (SDO) status by the USA national standards body ANSI (American National Standards Institute) in 1993 so that newer versions of the specification are official ANSI legislative standards. The messages primarily support the interoperability of components of a hospital information system and purchaser-provider contractual communications. HL7 version 2 messages have been developed to reflect standardised reporting data sets for several aspects of a patient’s care in hospital: • patient admission, transfer or discharge (ADT); • orders for drugs, procedures or tests and their results; • messages relating to finance and billing information; • clinical observations focusing primarily on measurements. HL7 version 2 is presently being used in the United States, Australia, Canada, Germany, the Netherlands, Israel, Japan and New Zealand. Additional countries are joining each year. Despite its wide uptake internationally, the problems of inconsistent implementations of Version 2 and the unsystematic growth of message segment definitions have limited the realisation of interoperability, leading to the drafting of a new v3 standard. A key feature of Version 3 is the Reference Information Model (RIM): a means of specifying the information content of messages through an information model that clarifies the definitions and ensures that they are used consistently. The RIM is a formal object model, expressed using UML, representing the superset of core classes and attributes that will be required (in various combinations) by the different HL7 version 3 messages. The HL7 Clinical Document Architecture (CDA) is a proposal for the generic structure of clinical documents, and is sometimes regarded as the HL7 equivalent of a record architecture. Only “Level One” of the CDA has at present been ratified: this XML-based specification includes a header with document authorship information, organisational origin and patient identifiers, and a body whose basic structure is loosely defined at this stage. The CEN EHRcom Task Force referred to above will include harmonisation with HL7 within its terms of reference, in particular seeking interoperability with CDA-conformant electronic documents.. 2.4.4 Standards for Images The Digital Imaging and Communications in Medicine (DICOM) standard arose out of a pre-cursor standard for images (ACR-NEMA) that was first published in 1985 by the American College of Radiology (ACR) and the National Electrical Manufacturers' Association (NEMA). The DICOM standard is the most widely used common data representation internationally for the various medical images acquired and communicated. It has addressed many of the issues of vendor-independent data formats and data transfers for digital medical images. It is presently in version 3, with 16 parts each relating to a different kind of image or signal data type or to a communication type. There is also a large number of supplements to the standard, revising it or adding new features. CEN and ANSI have adopted DICOM by reference in their imaging standards. 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 20 of 57 Deliverable 15 Update Reviews of status of relevant standards V.1 6WINIT/0045 Integrating the Health Environment (IHE) is a recently-formed industry sponsored organisation seeking to promote interoperability between systems within specialist departments such as radiology, and the conventional hospital systems used to order such investigations and to receive imaging study reports. It is working closely with DICOM and HL7 in this area. Figure 1: Domains of communication of health information covered by different industry and legislative standards 2.4.5 Data Protection Legislation The processing of personal health data within Europe must comply with the 1995 EU Directive [EU95/46] and the 1997 Council of Europe Recommendations [EU-97/5] regarding its acquisition, storage, communication and analysis. Each member state has passed national legislation to reinforce these instruments, such as the 1998 Data Protection Act in the UK. In the UK it is also necessary to comply with the Caldicott Report [Caldicott] recommendations governing the use of patient identifiable data inside the NHS, between organisations. Although conformance with the act is in practice still variable, the UCL R&D agenda includes the prototyping and evaluation of components that will permit the rigorous adoption of these principles. Many of these are incorporated within the London Demonstrator, even though the pseudonymous nature of the demonstration data does not legally require it. 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 21 of 57 Update Reviews of status of relevant standards Deliverable 15 2.4.6 V.1 6WINIT/0045 Security Standards There are several CEN standards relating to the secure handling of EHR information. The key ones are listed below; in practice many of the general security requirements are similar to those adopted by other industry sectors. They are therefore not discussed further in this report. 2.5 • Algorithm for Digital Signature Services in Health Care, ENV 12388:1996 • Security Categorisation and Protection for Healthcare Information Systems, ENV 12924:1997 • Secure User Authentication for Health Care: Management and Security of Authentication by Passwords, ENV 12251:2000 • Security for Healthcare Communication ENV 13608:1999 • Secure User Identification for Healthcare - Strong Authentication using microprocessor cards ENV 13729:1999 Discussion The principal standards applicable to the 6WINIT technical partners relate to networking, wireless and security protocols, mainly developed through the IETF. The focus of health informatics standards, usually addressed by CEN TC/251, has been to achieve data and service level interoperability at the application layer. This might be expressed, for example, as messages or middleware services. A range of security standards have also been developed, for example for health care enterprise security policy, password management, and encryption. In security the tendency has been to adapt generic standards for health service use rather than to develop independent or ad hoc healthcare specific standards. The majority of current standards focusing on the interoperability of health data have envisaged communications taking place asynchronously through messages between healthcare enterprises, rather than as real-time communications to support distributed or mobile healthcare personnel. This trend is changing, and this section of the deliverable report has summarised the progress of the CEN EHRcom and HISA Task Forces, and of the HL7 CDA, all of which are specifically targeting clinical shared care. The health care sector has historically been slow to adopt new technical solutions and to adapt its business processes to take advantage of them. There are many reasons for this, including the low overall spending on ICT compared with other sectors, which is now being rectified by many EU member states through extensive modernisation programmes. Ethical and legal concerns over distributed (and especially mobile) systems are gradually being tackled, with several recent demonstrators across Europe showing, for example, that simple WAP applications (via WAP phones) can provide acceptably secure access to patient data and alert messages. Another major obstacle to the growth of mobile technologies in healthcare has been the lack of interoperability between clinical applications, requiring the prohibitively expensive bespoke development of interfaces to support every shared information interaction. The set of standards now in the pipeline has every possibility to enable next-generation clinical applications to be fully interoperable. The demonstration within 6WINIT of successful mobile applications, including their security via IPSec (although so far only over wireless LAN), should help to stimulate the adoption of these technologies. From a standards perspective, the rigorous security 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 22 of 57 Deliverable 15 Update Reviews of status of relevant standards V.1 6WINIT/0045 provided by IPSec must be extended to GPRS and UMTS wireless communications, and further demonstration is probably required of how this can interwork in practical healthcare settings with PKI services and strong authentication including biometrics. Health informatics standards, for example the intended EN 13606 through EHRcom, need to include the features by which access control and disclosure policies for electronic health records can be represented for a large and distributed set of healthcare professionals. Standards for specific data types, such as images and waveforms, have largely been driven by industry and co-ordinated through professional or not-for-profit organisations (such as DICOM and openECG). DICOM is already a widely-adopted standard internationally and is used to enable the communication of images and other multi-media health data between heterogeneous applications. Migrating the present use of the Internet towards IPv6 is more an issue of national policy than of legislative standards. National health service and e-Government strategies refer to the eventual migration to IPv6, but the samples reviewed (e.g. UK, France) do not yet specify a schedule for this to become a formal part of the infrastructure framework. The standardisation processes needed to advance the wide-scale adoption of IPv6 within the health sector are very much 'work in progress', with further standardisation and standards uptake needed to enable clinical data interoperability and thereby to expand this market. National policy within EU member states on the migration to IPv6 probably needs to be more directive. 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 23 of 57 Update Reviews of status of relevant standards Deliverable 15 3 ONGOING WORK IN IETF 3.1 Introduction V.1 6WINIT/0045 IETF working groups meet every three months. At the recent meeting, some of the issues identified below were discussed as a part of ongoing work. The technical highlights include: 3.2 • Rough consensus to proceed with ‘limited’ or ‘moderate’ usage of site-local addresses. Drafts are being developed to define these usage types. • DHCPv6 has completed IESG review – will be published as a Proposed Standard very soon • DHCPv6 Options will go to Last Call once the base specification is completed • Zerouter BOF – interest shown in forming WG to develop protocols for autoconfiguring routers in SOHO type network environments. • RIPE has produced a proposal to distribute k-root service through use of anycast routing • MIPv6 WG to split into Mobile IP deployment and MIPv6 parts • MIPv6 has completed AD review and will go to IETF Last Call soon • 6bone meeting shows consensus to work on solutions to cleaning up the 6bone ‘mess’ • Parallel IPv6 multihoming meetings indicate renewed interest in developing provisional solutions in this space. Interaction of Transition Mechanisms The ngtrans working group of the IETF has made the INTERACTION draft (draft-krampellv6transition-interaction-01.txt) a current work item. This document discusses interaction of transition mechanisms that can be involved during the transition phase where both IPv4 and IPv6 will be concurrently used. On one hand, several transition mechanisms have been defined to solve different transition issues. On the other hand, one can face multiple transition issues and may have to use several transition mechanisms at the same time. Since an applicability scope is attached to each transition mechanism, specifying where the mechanism applies, i.e. host, domain or global, this memo aims at identifying cases where multiple transition mechanisms may be involved within the same scope, and what can be the interaction effects between them. As more and more transition mechanisms are deployed in the different local networks, the likelihood increases that a packet undergoes more than one transition on its way from source to destination. This 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 24 of 57 Update Reviews of status of relevant standards Deliverable 15 V.1 6WINIT/0045 may lead to unexpected effects and in the worst case make it unable for the network connection to become established. This work will guide the administrator of a network domain to choose the appropriate transition mechanism and pinpoint the possible side-effects. 3.3 3GPP-IPv6 Design Team The joint 3GPP/IETF design team was founded during a joint IPng working group and 3GPP session at the IPng interim meeting in Redmond May 30th – June 1st 2001. Goals: • Review 3GPP’s current usage of IPv6 and make recommendation for improvements • Write ID to be submitted to IPv6 w.g. • Redesign of 3GPP architecture / protocols Non-Goals: The following topics were announced during a status presentation of the design team at the 51st IETF in London, August 2001: • Allow the use of standard IPv6 implementations in 3GPP usage scenarios • Addressing Ø Single address per PDP context (current) Ø Prefix per PDP context Ø Ø 19-Jan-03 − − − Per device same prefix for all PDP contexts for same device shared among PDP context’s for many devices Node able to create multiple addresses Static or temporary IPv6 addresses • Model for support of devices behind handset Ø Router, bridge, proxy • DNS Ø Locating a DNS server Ø Handset address in DNS • Security • MTU • Issues left to implementers in 3GPP specifications • Transition Ø IPv6 only, dual stack, etc Ø Communication with IPv4 internet • Remote Management Ø MIB support 6WINIT – IPv6 Wireless Internet IniTiative Page 25 of 57 Deliverable 15 Update Reviews of status of relevant standards V.1 6WINIT/0045 The design group has issued a first draft ’Recommendations for IPv6 in 3GPP Standards’ (draftwassermann-3gpp-advice-00.txt, November 2001). This draft deals primarily with the IPv6 address assignments as specified in 3GPP and by the IETF. 3GPP has defined a very narrow approach to IPv6 address configuration. Address auto-configuration is based on PPPv6 and therefore works similarly to dialup networks. Each primary PDP context gets a single 64-bit identifier and /64 prefix assigned by the GGSN. Handsets and attached equipment may request multiple PDP contexts. The design group now gives the recommendation to 3GPP to make the address configuration process more compatible with the current defined praxis for IPv6. This would make it easier to base implementations in handsets and equipment on standard IPv6 stacks. The recommendation take into account the specific requirements of mobile equipment (many devices, scarce bandwidth on air interface). Recommendations: 1. Multiple prefixes should be allowed for each primary PDP context 2. A given prefix must not be assigned to more than one primary PDP context 3. Allow 3GPP nodes to use multiple identifiers under those prefixes including randomly generated ones This would effectively treat every single 3GPP node as a single /64 subnet and would allow standardscompliant IPv6 nodes to connect to the Internet through 3GPP handsets without modification. 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 26 of 57 Deliverable 15 4 Update Reviews of status of relevant standards V.1 6WINIT/0045 SUMMARY This deliverable provides an overview of technologies and standards involved with mobile internet evolution. It is a continuous process and the project members follow all these developments very closely with active participation in different concerned organisations. Since the 6WINIT project addresses specifically the clinical applications for their trials, the standards related with the health issues are also followed very closely by the group concerned.. IETF working groups are progressing well in discussing many issues of urgency related with deployment issues such as transition strategies, DNS, DHCP, Addressing architecture, Assignment, security, Mobile IP, Quality of service etc. To expedite the discussions even a special working group to address the IPv6 Operations has been initiated. Though UMTS/3GPP deployment has been delayed the technology community is aware of importance of IPv6 in mobile networks and hence are considering the roaming between the Wireless LAN and GPRS/UMTS type of cellular networks. It is expected with early deployment of WLAN hotspots and handovers between these hotspots and mobile networks will be happening as 6WINIT project are demonstrating the seamless interworking between these technologies. 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 27 of 57 Deliverable 15 5 Update Reviews of status of relevant standards V.1 6WINIT/0045 PERSPECTIVE OF WIRELESS INTERNET EVOLUTION The mobile information society is fast becoming reality. We see many citizens carrying laptop computers, PDAs and multifunctional mobile terminals communicating from anywhere, anytime to those connected on line, all the time. Though the percentage of always on-line mobile commuters are limited today, the potential of reaching billions of mobile users is not too distant. The terminals with very powerful processing capability, interfaces and functions are evolving fast. Similarly the access networks both fixed and wireless LANs are also reaching all homes and hotspots allowing people to interconnect. However, the limited address space of IPv4 with no guarantees against hackers (security problems) is one of the major problems for the penetration of this always-online fixed or wireless access services. Thanks to IPv6 Internet protocol that has been defined and evolving with large address space, security and quality of service support, mobility support the dream of every citizen having his own domain is not far off. The time to market is so small, it is a matter of time that functions and interoperability standards are defined in IETF and regional bodies, we will be able to use these new technologies cost effectively very soon. 6WINIT addressed many issues related with wireless next generation internet and demonstrated effectively with life saving clinical applications and day to day usable business applications, the advantages of mobile IP networks with IPv6. Now a number of vendors are committed to the development of IPv6 products and hence the project feels proud of contributing to such a development both to standards development and system deployment. 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 28 of 57 Deliverable 15 Update Reviews of status of relevant standards V.1 6WINIT/0045 ANNEX: STANDARDS AND WORKING DOCUMENTS Health related standards [CEN] http://www.centc251.org [OpenEHR] http://www.openehr.org [HL7] http://www.hl7.org [EU-95/46] European Community Directive 95/46/EC "On the Protection of Individuals with Regard to the Processing of Personal Data and on the Free Movement of such Data”. OJ L281/31 - 50, 24 October 1995 [EU-97/5] Council of Europe Recommendation, R(97)5 “On the Protection of Medical Data”. Council of Europe, Strasbourg, 12 February 1997 [Caldicott] The Caldicott Committee, “Report on the review of patient-identifiable information”, Department of Health, London, December 1997 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 29 of 57 Deliverable 15 Update Reviews of status of relevant standards V.1 6WINIT/0045 IPv6 Documents IPv6 Core Protocols RFC 2460: Internet Protocol, Version 6 (IPv6) Specification S. Deering, R. Hinden, December 1998 RFC 2463: Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification A. Conta, S. Deering, December 1998 Internet Control Message Protocol (ICMPv6)for the Internet Protocol Version 6 (IPv6) Specification A. Conta, S. Deering, November 2001 (work in progress) Effects of ICMPv6 on IKE and IPsec Policies J. Arkko, June 2002 (work in progress) Requirements for Plug and Play IPsec for IPv6 applications T. Kobayakawa, S. Miyakawa, October 2002 (work in progress) Manual SA Configuration for IPv6 Link Local Messages J. Arkko et al., June 2002 (work in progress) RFC 2711: IPv6 Router Alert Option C. Partridge, A. Jackson, October 1999 RFC 2461: Neighbor Discovery for IP Version 6 (IPv6) T. Narten, E. Nordmark, W. Simpson, December 1998 RFC 2462: IPv6 Stateless Address Autoconfiguration S. Thomson, T. Narten, December 1998 RFC 2894: Router Renumbering for IPv6 M. Crawford, August 2000 RFC 3041: Privacy Extensions for Stateless Address Autoconfiguration in IPv6 T. Narten, R. Draves, January 2001 Statement on IPv6 Address Privacy S. Deering, R. Hinden, Co-Chairs of the IETF's IP Next Generation Working Group, October 22, 1999 RFC 3041 Considered Harmful F. Dupont, P. Savola, July 2002 (work in progress) IPv6 Stateless Address Autoconfiguration for Hierarchical Mobile Ad Hoc Networks K. Weniger, M. Zitterbart, February 2002 (work in progress) Optimistic Duplicate Address Detection N. Moore, November 2002 (work in progress) Host Requirements of IPv6 for Low Cost Network Appliances N. Okabe et al., July 2002 (work in progress) 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 30 of 57 Deliverable 15 Update Reviews of status of relevant standards V.1 6WINIT/0045 RFC 3122: Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification A. Conta, June 2001 IPv6 Neighbor Discovery trust models and threats P. Nikander, October 2002 (work in progress) Securing IPv6 Neighbor Discovery Using Address Based Keys (ABKs) J. Kempf, June 2002 (work in progress) Securing IPv6 Neighbor Discovery Using Cryptographically Generated Addresses (CGAs) J. Arkko, P. Nikander, V. Mantyla, June 2002 (work in progress) Securing IPv6 Neighbor Discovery G. Montenegro et al., June 2002 (work in progress) IPv6 Neighbor Discovery Link-Layer Option Extension S. Goswami, January 2002 (work in progress) Fast Router Discovery with AP Notification J. Choi, D. Shin, June 2002 (work in progress) IPv6 Fast Router Advertisement J. Kempf, M. Khalil, B. Pentland, October 2002 (work in progress) IPv6 Host to Router Load Sharing B. Hinden, January 2002 (work in progress) RFC 2473: Generic Packet Tunneling in IPv6 Specification A. Conta, S. Deering, December 1998 Generic Packet Tunneling in IPv6 Specification A. Conta, S. Deering, July 2002 (work in progress) IPv6 Node Information Queries M. Crawford, May 2002 (work in progress) Name resolution in zeroconf environment using ICMPv6 node information query J. Hagino, June 2002 (work in progress) Use of ICMPv6 node information query for reverse DNS lookup J. Hagino, June 2002 (work in progress) RFC 2675: IPv6 Jumbograms D. Borman, S. Deering, R. Hinden, August 1999 Automatic Prefix Delegation Protocol for Internet Protocol Version 6 (IPv6) B. Haberman, J. Martin, May 2002 (work in progress) IPv6 Router Advertisement Prefix Delegation Option N. Lutchansky, February 2002 (work in progress) Access Control Prefix Router Advertisement Option for IPv6 S. Bellovin, November 2002 (work in progress) 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 31 of 57 Deliverable 15 Update Reviews of status of relevant standards V.1 6WINIT/0045 IPv6 Flow Label Specification J. Rajahalme, A. Conta, B. Carpenter, S. Deering, September 2002 (work in progress) A Modified Specification for use of the IPv6 Flow Label for providing An efficient Quality of Service using hybrid approach (PostScript, PDF version) R. Banerjee et al., April 2002 (work in progress) Design and Implementation of the Quality-of-Service in IPv6 using the modified Hop-by-Hop Extension header-A Practicable Mechanism (PostScript, PDF version) R. Banerjee et al., March 2002 (work in progress) A model for Diffserv use of the IPv6 Flow Label Specification A. Conta, J. Rajahalme, November 2001 (work in progress) The Features of IPv6 Signaling J. Choi et al., July 2002 (work in progress) Signaling Interworking for IPv6 Network J. Choi et al., October 2002 (work in progress) The IPv6 Payload Header F. Dupont, March 2002 (work in progress) Redundant Address Deletion when Encapsulating IPv6 in IPv6 S. Deering, B. Zill, November 2001 (work in progress) IPv6 destination option header clarification F. Dupont, November 2001 (work in progress) IPv6 Node Requirements J. Loughney, November 2002 (work in progress) IANA Allocation Guidelines for Values in IPv6 and Related Headers T. Narten, October 2002 (work in progress) Addressing and Routing RFC 2373: IP Version 6 Addressing Architecture R. Hinden, S. Deering, July 1998 IP Version 6 Addressing Architecture B. Hinden, S. Deering, October 2002 (work in progress) RFC 2374: An IPv6 Aggregatable Global Unicast Address Format R. Hinden, M. O'Dell, S. Deering, July 1998 RFC 2450: Proposed TLA and NLA Assignment Rules R. Hinden, December 1998 RFC 3177: IAB/IESG Recommendations on IPv6 Address Allocations to Sites IAB, IESG, September 2001 IPv6 Address Allocation and Assignment Assignment Policy (draft) APNIC/ARIN/RIPE, June, 26 2002 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 32 of 57 Deliverable 15 Update Reviews of status of relevant standards V.1 6WINIT/0045 RFC 2471: IPv6 Testing Address Allocation R. Hinden, R. Fink, J. Postel (deceased), December 1998 RFC 2772: 6Bone Backbone Routing Guidelines R. Rockell, R. Fink, February 2000 RFC 2921: 6BONE pTLA and pNLA Formats (pTLA) B. Fink, September 2000 RFC 2928: Initial IPv6 Sub-TLA ID Assignments R. Hinden, S. Deering, R. Fink, T. Hain, September 2000 RFC 3194: The H-Density Ratio for Address Assignment Efficiency An Update on the H ratio A. Durand, C. Huitema, November 2001 Analyzing IPv4 and IPv6 address space with the HD-ratio A. Durand, C. Huitema, February 2002 (work in progress) IPv6 Addressing Architecture Support for mobile ad hoc networks G. Chelius, E. Fleury, September 2002 (work in progress) A Flexible Method for Managing the Assignment of Bites of an IPv6 Address Block M. Blanchet, November 2002 (work in progress) IPv6 Scoped Address Architecture S. Deering, B. Haberman, T. Jinmei, E. Nordmark, A. Onoe, B. Zill, June 2002 (work in progress) IPv6 Globally Unique Site-Local Addresses R. Hinden, December 2002 (work in progress) Use of /127 Prefix Length Between Routers Considered Harmful P. Savola, June 2002 (work in progress) Default Address Selection for IPv6 R. Draves, August 2002 (work in progress) Default Router Preferences, More-Specific Routes and Load Sharing R. Draves, B. Hinden, June 2002 (work in progress) IPv6 Network Ingress Filtering F. Dupont, C. Castelluccia, January 2002 (work in progress) Multi-link Subnet Support in IPv6 D. Thaler, C. Huitema, July 2002 (work in progress) An IPv6 Provider-Independent Global Unicast Address Format T. Hain, October 2002 (work in progress) Application and Use of the IPv6 Provider-Independent Global Unicast Address Format T. Hain, October 2002 (work in progress) IMEI-based universal IPv6 interface IDs F. Dupont, L. Nuaymi, July 2002 (work in progress) 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 33 of 57 Deliverable 15 Update Reviews of status of relevant standards V.1 6WINIT/0045 Mapping Universal Geographical Area Description (GAD) to IPv6 Geo Based Unicast Addresses F. van Megen, P. Muller, October 2001 (work in progress) IPv6 addressing and Stream Control Transmission Protocol R. Stewart, S. Deering, April 2002 (work in progress) Stream Control Transmission Protocol (SCTP) Dynamic Address Reconfiguration R. Stewart et al., May 2002 (work in progress) Multihoming issues in the Stream Control Transmission Protocol L. Coene, February 2002 (work in progress) Multirouting L. Coene, February 2002 (work in progress) RFC 2375: IPv6 Multicast Address Assignments R. Hinden, S. Deering, July 1998 RFC 2526: Reserved IPv6 Subnet Anycast Addresses D. Johnson, S. Deering, March 1999 An analysis of IPv6 anycast J. Hagino, K.Ettikan, July 2002 (work in progress) IPv6 Anycast Binding using Return Routability B. Haberman, E. Nordmark, October 2002 (work in progress) RFC 2710: Multicast Listener Discovery (MLD) for IPv6 S. Deering, W. Fenner, B. Haberman, October 1999 Multicast Listener Discovery Version 2 (MLDv2) for IPv6 R. Vida, L. Costa, December 2002 (work in progress) Source Address Selection for Multicast Listener Discovery Protocol (RFC 2710) B. Haberman, November 2002 (work in progress) Unidirectional link support for MLDv2 J. Lundberg, June 2002 (work in progress) RFC 3019: IP Version 6 Management Information Base for The Multicast Listener Discovery Protocol B. Haberman, R. Worzella, January 2001 RFC 3307: Allocation Guidelines for IPv6 Multicast Addresses B. Haberman, August 2002 RFC 3306: Unicast-Prefix-based IPv6 Multicast Addresses B. Haberman, D. Thaler, August 2002 Host-based Anycast using MLD B. Haberman, D. Thaler, May 2002 (work in progress) Duplicate Address Detection Optimization using IPv6 Multicast Listener Discovery G. Daley, R. Nelson, October 2002 (work in progress) 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 34 of 57 Deliverable 15 Update Reviews of status of relevant standards V.1 6WINIT/0045 Fault Tolerance and Load Balance Services using IPv6 Anycast K. Ettikan, August 2002 (work in progress) RFC 3306: Unicast-Prefix-based IPv6 Multicast Addresses B. Haberman, D. Thaler, August 2002 Host-based IPv6 Multicast Addresses Allocation J. Park et al., February 2002 (work in progress) Link Scoped IPv6 Multicast Addresses J. Park, M. Shin, November 2002 (work in progress) Embedding the Address of RP in IPv6 Multicast Address P. Savola, B. Haberman, October 2002 (work in progress) Securing Group Management in IPv6 with Cryptographically Generated Addresses C. Castelluccia, G. Montenegro, July 2002 (work in progress) RFC 1888: OSI NSAPs and IPv6 Bound, J., B. Carpenter, D. Harrington, J. Houldsworth, A. Lloyd, August 1996 RFC 2080: RIPng for IPv6 Malkin, G., R. Minnear, January 1997 RFC 2740: OSPF for IPv6 R. Coltun, D. Ferguson, J. Moy, December 1999 Routing IPv6 with IS-IS C. Hopps, December 2002 (work in progress) Using OSPFv3 for IPv6 router autoconfiguration G. Chelius, E. Fleury, L. Toutain, June 2002 (work in progress) Authentication/Confidentiality for OSPFv3 M. Gupta, N. Melam, July 2002 (work in progress) Ad hoc On-Demand Distance Vector (AODV) Routing for IP version 6 C. Perkins, E. Royer, S. Das, November 2001 (work in progress) RFC 2283: Multiprotocol Extensions for BGP-4 T. Bates, R. Chandra, D. Katz, Y. Rekhter, February 1998 RFC 2545: Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing P. Marques, F. Dupont, March 1999 BGP4 router ID for IPv6 only routers F. Dupont, A. Durand, January 2002 (work in progress) Identification of IPv6 Routes that need Tunneling - Use of BGP Extended Community Attribute T. Senevirathne, June 2002 (work in progress) RPSL extensions for IPv6 and Multicast Routing Policies F. Parent, January 2002 (work in progress) 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 35 of 57 Deliverable 15 Update Reviews of status of relevant standards V.1 6WINIT/0045 BGP-MPLS VPN extension for IPv6 VPN G. De Clercq et al., November 2002 (work in progress) RSVP-TE Extension for IPv4/IPv6 Dual Stacking PE under IPv4 MPLS Core Environment H. Ishii et al., February 2002 (work in progress) Mobility Extensions to RSVP in an RSVP-Mobile IPv6 Framework C. Shen et al., July 2002 (work in progress) IPv6 Traffic Engineering Tunnel H. Ishii et al., November 2001 (work in progress) An Authenticated Key Exchange Protocol in IPv6 J. Floroiu, February 2002 (work in progress) Security Framework for the Access Control of MIPv6 Mobile Nodes J. Floroiu, November 2002 (work in progress) Visualizing Change; Re-Defining the Role of the IPv6 Protocol Specification E. Terrell, April 2002 (work in progress) Multihoming RFC 3178: IPv6 Multihoming Support at Site Exit Routers J. Hagino, H. Snyder, October 2001 Requirements for IPv6 Site-Multihoming Architectures B. Black, V. Gill, J. Abley, June 2002 (work in progress) Host-Centric IPv6 Multihoming C. Huitema, R. Draves, June 2002 (work in progress) Multi Homing Translation Protocol (MHTP) M. Py, November 2001 (work in progress) Random generation of interface identifiers M. Bagnulo, I. Soto, A. Azcorra, January 2002 (work in progress) Provider-Internal Aggregation based on Geography to Support Multihoming in IPv6 I. van Beijnum, October 2002 (work in progress) GAPI: A Geographically Aggregatable Provider Independent Address Space to Support Multihoming in IPv6 M. Py, I. van Beijnum, October 2002 (work in progress) Extension Header for Site-Multi-homing support M. Bagnulo, A. Garcia-Martinez, November 2002 (work in progress) The Architecture of End to End Multihoming M. Ohta, November 2002 (work in progress) 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 36 of 57 Deliverable 15 Update Reviews of status of relevant standards V.1 6WINIT/0045 Supporting Protocols, MIBs and APIs RFC 1886: DNS Extensions to support IP version 6 S. Thomson, C. Huitema, December 1995 DNS Extensions to support IP version 6 S. Thomson, C. Huitema et al., November 2002 (work in progress) RFC 2874: DNS Extensions to Support IPv6 Address Aggregation and Renumbering M. Crawford, C. Huitema, S. Thomson, July 2000 RFC 3152: Delegation of IP6.ARPA R. Bush, August 2001 RFC 3363: Representing Internet Protocol version 6 (IPv6) Addresses in the Domain Name System (DNS) R. Bush, A. Durand, B. Fink, O. Gudmundsson, T. Hain, August 2002 RFC 3364: Tradeoffs in Domain Name System (DNS) Support for Internet Protocol version 6 (IPv6) R. Austein, August 2002 IPv6 DNS transition issues A. Durand, November 2002 (work in progress) Mapped IPv4 address Considerations in the DNS B. Manning, October 2001 (work in progress) IPv4-to-IPv6 migration and DNS name space fragmentation J. Ihren, March 2002 (work in progress) RFC 2732: Format for Literal IPv6 Addresses in URLs R. Hinden, B. Carpenter, L. Masinter, December 1999 IPv6 DNS lookup proxy A. Durand, October 2001 (work in progress) Indicating Resolver Support for AAAA Records J. Reid, S. Woolf, October 2002 (work in progress) Well known site local unicast addresses for DNS resolver A. Durand, J. Hagino, D. Thaler, November 2002 (work in progress) IPv6 Router Advertisement DNS resolver Option L. Beloeil, October 2002 (work in progress) Domain Name Auto-Registration for Plugged-in IPv6 Nodes H. Kitamura, July 2002 (work in progress) IPv6 Hostname auto-registration Procedure S. Rao, K. Ettikan, December 2002 (work in progress) A Protocol for Anycast Address Resolving S. Ata, H. Kitamura, M. Murata, June 2002 (work in progress) Dynamic Host Configuration Protocol for IPv6 (DHCPv6) R. Droms et al., November 2002 (work in progress) 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 37 of 57 Deliverable 15 Update Reviews of status of relevant standards V.1 6WINIT/0045 Issues Concerning DHCP in IPv6 Specifications R. Droms, October 2002 (work in progress) Load Balancing for DHCPv6 B. Volz, July 2002 (work in progress) Load Balancing using pseudo-Anycast and pseudo-Mobility (LBAM) in IPv6 Y. Feng et al., April 2002 (work in progress) Time Configuration Options for DHCPv6 A. Vijayabhaskar, May 2002 (work in progress) NIS Configuration Options for DHCPv6 A. Vijayabhaskar, May 2002 (work in progress) DNS Configuration Options for DHCPv6 R. Droms, May 2002 (work in progress) Client Preferred Prefix option for DHCPv6 A. Vijayabhaskar, June 2002 (work in progress) Using DHCPv6 for DNS Configuration in Hosts R. Droms, T. Narten, B. Aboba, March 2002 (work in progress) DHCPv6 Options for SIP Servers H. Schulzrinne, B. Volz, November 2002 (work in progress) PPP IPV6 Control Protocol Extensions for DNS Server Addresses T. Hiller, G. Zorn, October 2002 (work in progress) Requirements for IPv6 prefix delegation S. Miyakawa, November 2002 (work in progress) IPv6 Prefix Options for DHCPv6 O. Troan, R. Droms, December 2002 (work in progress) A Guide to Implementing Stateless DHCPv6 Service R. Droms, October 2002 (work in progress) Threat Analysis for IPv6 Public Multi-Access Links J. Kempf, E. Nordmark, June 2002 (work in progress) RFC 3111: Service Location Protocol Modifications for IPv6 E. Guttman, May 2001 RFC 2428: FTP Extensions for IPv6 and NATs M. Allman, S. Ostermann, C. Metz, September 1998 SMTP operational experience in mixed IPv4/IPv6 environements M. Nakamura, J. Hagino, July 2002 (work in progress) Defining and Locating IPv6 Address Blocks using the Internet Resource Query Service E. Hall, July 2002 (work in progress) 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 38 of 57 Deliverable 15 Update Reviews of status of relevant standards V.1 6WINIT/0045 RFC 3266: Support for IPv6 in Session Description Protocol (SDP) S. Olson, G. Camarillo, A. B. Roach, June 2002 Virtual Router Redundancy Protocol for IPv6 R. Hinden, December 2002 (work in progress) Reference ID for NTPv6 J. Boudreault, M. Blanchet, November 2001 (work in progress) Textual Conventions for Transport Addresses M. Daniele, J. Schoenwaelder, September 2002 (work in progress) RFC 2465: Management Information Base for IP Version 6: Textual Conventions and General Group D. Haskin, S. Onishi, December 1998 RFC 2466: Management Information Base for IP Version 6: ICMPv6 Group D. Haskin, S. Onishi, December 1998 IP Forwarding Table MIB M. Wasserman, November 2002 (work in progress) RFC 2452: IP Version 6 Management Information Base for the Transmission Control Protocol M. Daniele, December 1998 RFC 2454: IP Version 6 Management Information Base for the User Datagram Protocol M. Daniele, December 1998 Management Information Base for the Internet Protocol (IP) S. Routhier, November 2002 (work in progress) Management Information Base for the Transmission Control Protocol (TCP) B. Fenner et al., November 2002 (work in progress) Management Information Base for the User Datagram Protocol (UDP) B. Fenner, July 2002 (work in progress) RFC 2553: Basic Socket Interface Extensions for IPv6 R. Gilligan, S. Thomson, J. Bound, W. Stevens, March 1999 Basic Socket Interface Extensions for IPv6 R. Gilligan, S. Thomson, December 2002 (work in progress) Scoped Address Extensions to the IPv6 Basic Socket API R. Gilligan et al., July 2002 (work in progress) RFC 2292: Advanced Sockets API for IPv6 W. Stevens, M. Thomas, February 1998 Advanced Sockets API for IPv6 R. Stevens, M. Thomas, E. Nordmark, T. Jinmei, October 2002 (work in progress) Application Aspects of IPv6 Transition M. Shin et al., October 2002 (work in progress) 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 39 of 57 Deliverable 15 Update Reviews of status of relevant standards V.1 6WINIT/0045 One-way Delay Measurement using IPv6 Source Routing J. Jeong et al., February 2002 (work in progress) Unidentified issues in IPv6 deployment/operation J. Hagino, T. Jinmei, June 2002 (work in progress) IPv6 Operations / Transition Mechanisms RFC 2893: Transition Mechanisms for IPv6 Hosts and Routers R. Gilligan, E. Nordmark, August 2000 Basic Transition Mechanisms for IPv6 Hosts and Routers E. Nordmark, R. Gilligan, November 2002 (work in progress) An overview of the Introduction of IPv6 in the Internet W. Biemolt et al., March 2002 (work in progress) Interaction of transition mechanisms A. Baudot et al., July 2002 (work in progress) Survey of IPv4 Addresses in Currently Deployed IETF Standards P. Nesser II, March 2002 (work in progress) IPv4-Mapped Addresses on the Wire Considered Harmful C. Metz, J. Hagino, October 2002 (work in progress) IPv4-Mapped Address API Considered Harmful C. Metz, J. Hagino, October 2002 (work in progress) RFC 3056: Connection of IPv6 Domains via IPv4 Clouds B. Carpenter, K. Moore, February 2001 RFC 3068: An Anycast Prefix for 6to4 Relay Routers C. Huitema, June 2001 6to4 and DNS K. Moore, October 2002 (work in progress) Support for Multicast over 6to4 Networks D. Thaler, July 2002 (work in progress) An interconnection mechanism of Mobile IPv4 and Mobile IPv6 using 6to4 H. Kahng et al., July 2002 (work in progress) Teredo: Tunneling IPv6 over UDP through NATs C. Huitema, September 2002 (work in progress) Unmanaged Networks Transition Scope C. Huitema et al., November 2002 (work in progress) Evaluation of Transition Mechanisms for Unmanaged Networks C. Huitema et al., November 2002 (work in progress) 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 40 of 57 Deliverable 15 Update Reviews of status of relevant standards V.1 6WINIT/0045 Transition Scenarios for ISP Networks C. Mickles, November 2002 (work in progress) ISP requirements for IPv6 unmanaged networks Y. Noisette, September 2002 (work in progress) IPv6 Enterprise Networks Scenarios Y. Pouffary et al., November 2002 (work in progress) IPv6 for Large Access Providers K. Allen, W. Chen, October 2002 (work in progress) RFC 2765: Stateless IP/ICMP Translation Algorithm (SIIT) E. Nordmark, February 2000 Dual Stack Transition Mechanism (DSTM) Overview J. Bound, June 2002 (work in progress) Dual Stack Transition Mechanism (DSTM) J. Bound et al., July 2002 (work in progress) Extensions to SIIT and DSTM for enhanced routing of inbound packets H. Soliman, E. Nordmark, November 2001 (work in progress) DSTM Options for DHCPv6 B. Volz et al., April 2002 (work in progress) DSTM Ports Option for DHCPv6 M. Shin, June 2002 (work in progress) DSTM in a VPN Scenario J. Richier, O. Medina, L. Toutain, February 2002 (work in progress) Ports Option Support in DSTM M. Shin et al., February 2002 (work in progress) Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) F. Templin, T. Gleeson, M. Talwar, D. Thaler, November 2002 (work in progress) Proposed Solutions for ISATAP Operational Issues F. Templin, October 2002 (work in progress) ISATAP Transition Scenario for Enterprise/Managed Networks F. Templin et al., November 2002 (work in progress) Fast Convergence Extension for ISATAP Router Discovery F. Templin, February 2002 (work in progress) ISATAP Profile for Tunnel Setup Protocol (TSP) F. Templin, August 2002 (work in progress) ISATAP interactions with TSP F. Templin, September 2002 (work in progress) 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 41 of 57 Deliverable 15 Update Reviews of status of relevant standards V.1 6WINIT/0045 Router Affiliation Protocol for v6-over-(foo)-over-IPv4 F. Templin, October 2002 (work in progress) Neighbor Affiliation Protocol for IPv6-over-(foo)-over-IPv4 F. Templin, November 2002 (work in progress) Dual Stack deployment using DSTM and neighbour discovery P. Bereski, D. Galand, G. Gastaud, G. Diribarne, March 2002 (work in progress) RFC 2766: Network Address Translation - Protocol Translation (NAT-PT) G. Tsirtsis, P. Srisuresh, February 2000 Issues with NAT-PT DNS ALG in RFC2766 A. Durand, February 2002 (work in progress) NAT-PT DNS ALG solutions P. Hallin, S. Satapati, July 2002 (work in progress) NAT64 - NAT46 A. Durand, June 2002 (work in progress) RFC 2767: Dual Stack Hosts using the "Bump-In-the-Stack" Technique (BIS) K. Tsuchiya, H. Higuchi, Y. Atarashi, February 2000 Multicast extensions to dual stack hosts using the 'Bump-In-the-Stack' Technique (mBIS) K. Tsuchiya, H. Higuchi, November 2001 (work in progress) RFC 3338: Dual Stack Hosts Using "Bump-in-the-API" (BIA) S. Lee, M-K. Shin, Y-J. Kim, E. Nordmark, A. Durand, October 2002 RFC 3053: IPv6 Tunnel Broker A. Durand, P. Fasano, I. Guardini, D. Lento, January 2001 Tunnel Setup Protocol (TSP)A Control Protocol to Setu IPv6 or IPv4 Tunnels M. Blanchet, July 2002 (work in progress) Applicability of the Tunnel Setup Protocol(TSP) as an IPv6 Transition Technique M. Blanchet, F. Parent, June 2002 (work in progress) TSP-TEREDO: Stateful IPv6 over IPv4 Tunnels with NAT using TSP and TEREDO F. Parent, M. Blanchet, June 2002 (work in progress) DSTM IPv4 over IPv6 tunnel profile for Tunnel Setup Protocol(TSP) M. Blanchet et al., July 2002 (work in progress) IPv6 over IPv4 profile for Tunnel Setup Protocol (TSP) M. Blanchet, July 2002 (work in progress) RFC 3089: A SOCKS-based IPv6/IPv4 Gateway Mechanism H. Kitamura, April 2001 RFC 3142: An IPv6-to-IPv4 Transport Relay Translator J. Hagino, K. Yamamoto, June 2001 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 42 of 57 Deliverable 15 Update Reviews of status of relevant standards V.1 6WINIT/0045 RFC 2529: Transmission of IPv6 over IPv4 Domains without Explicit Tunnels B. Carpenter, C. Jung, March 1999 An IPv6/IPv4 Multicast Translator based on IGMP/MLD Proxying (mtp) K. Tsuchiya, H. Higuchi, S. Sawada, S. Nozaki, October 2002 (work in progress) Connecting IPV6 islands within a same IPV4 AS G. Cristallo et al., March 2002 (work in progress) Security Considerations for 6to4 P. Savola, December 2002 (work in progress) Connecting IPv6 Islands across IPv4 Clouds with BGP J. De Clercq et al., October 2002 (work in progress) Operational Environments and Transition Scenarios for 'Connecting IPv6 Islands across IPv4 Clouds with BGP' F. Le Faucheur, June 2002 (work in progress) Moving in a Dual Stack Internet S. Tsao et al., March 2002 (work in progress) Internet Protocol, Version 64 (IPv64) Specification A. Azcorra et al., April 2002 (work in progress) Analysis on IPv6 Transition in 3GPP Networks J. Wiljakka, December 2002 (work in progress) IPv6 Transition Solutions for 3GPP Networks J. Wiljakka, November 2002 (work in progress) Transition Scenarios for 3GPP Networks J. Soininen, November 2002 (work in progress) Transition cases and their implementations for 3GPP Networks A. Thakur et al., November 2002 (work in progress) Firewalling Considerations for IPv6 P. Savola, September 2002 (work in progress) IPv6 Multicast Deployment Issues P. Savola, November 2002 (work in progress) Moving from 6bone to IPv6 Internet P. Savola, November 2002 (work in progress) Mappings to Lower Layers RFC 2464: Transmission of IPv6 Packets over Ethernet Networks M. Crawford, December 1998 RFC 2467: Transmission of IPv6 Packets over FDDI Networks M. Crawford, December 1998 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 43 of 57 Deliverable 15 Update Reviews of status of relevant standards V.1 6WINIT/0045 RFC 2470: Transmission of IPv6 Packets over Token Ring Networks M. Crawford, T. Narten, S. Thomas, December 1998 RFC 2491: IPv6 over Non-Broadcast Multiple Access (NBMA) networks G. Armitage, P. Schulter, M. Jork, G. Harter, January 1999 RFC 2492: IPv6 over ATM Networks G. Armitage, P. Schulter, M. Jork, January 1999 RFC 2590: Transmission of IPv6 Packets over Frame Relay Networks Specification A. Conta, A. Malis, M. Mueller, May 1999 RFC 2497: Transmission of IPv6 Packets over ARCnet Networks I. Souvatzis, January 1999 RFC 3146: Transmission of IPv6 Packets over IEEE 1394 Networks K. Fujisawa, A. Onoe, October 2001 RFC 2472: IP Version 6 over PPP D. Haskin, E. Allen, December 1998 RFC 3162: RADIUS and IPv6 B. Aboba, G. Zorn, D. Mitton, August 2001 IP Version 6 over MAPOS T. Ogura, M. Maruyama, T. Yoshida, October 2002 (work in progress) IPv6 over Fibre Channel C. DeSanti, October 2002 (work in progress) IPv6 over Mobile IPv4 P. Calhoun, P. Engelstad, T. Hiller, P. McCann, November 2002 (work in progress) Mobility RFC 3314: Recommendations for IPv6 in Third Generation Partnership Project (3GPP) Standards M. Wasserman, Ed., September 2002 Mobility Support in IPv6 D. Johnson, C. Perkins, J. Arkko, November 2002 (work in progress) MIPv6: from hindsight to foresight? E. Nordmark, November 2001 (work in progress) How to make IPsec more mobile IPv6 friendly F. Dupont, July 2002 (work in progress) MIPv6 for Multiple Interfaces N. Montavont, T. Noel, M. Kassi-Lahlou, July 2002 (work in progress) Connecting Mobile IPv6 Nodes Across IPv4 Clouds Back To IPv6 Domains With Mobile IPv4 C. Liu, May 2002 (work in progress) 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 44 of 57 Deliverable 15 Update Reviews of status of relevant standards V.1 6WINIT/0045 Dynamic Diffie Hellman based Key Distribution for Mobile IPv6 S. Faccin, F. Le, January 2002 (work in progress) MIPv6 Care of Address Option A. O'Neill, September 2002 (work in progress) Mobile Networks Support in Mobile IPv6 (Prefix Scope Binding Updates) T. Ernst, L. Bellier, A. Olivereau, C. Castelluccia, H. Lach, March 2002 (work in progress) MIPv6 IP User mobility support through DNS J. Song, C. Chong, D. Lee, October 2001 (work in progress) Mobile IPv6 Extension: Using DNS Servers Assigned by Home Agent J. Bharatia, K. Chowdhury, February 2002 (work in progress) MIPv6 Security: Assessment of Proposals G. Montenegro, A. Petrescu, November 2001 (work in progress) Selection of MIPv6 Security Level Using a Hashed Address J. Arkko, P. Nikander, G. Montenegro, June 2002 (work in progress) Security Framework for Mobile IPv6 Route Optimization J. Arkko, November 2001 (work in progress) Using IPsec to Protect Mobile IPv6 Signaling between Mobile Nodes and Home Agents J. Arkko, V. Devarapalli, F. Dupont, October 2002 (work in progress) Protecting Against Bidding Down Attacks G. Montenegro, P. Nikander, April 2002 (work in progress) Mobile IPv6 support in MPLS J. Choi et al., November 2001 (work in progress) Note about Routing Header Processing on IPv6 Hosts P. Savola, February 2002 (work in progress) Security of IPv6 Routing Header and Home Address Options P. Savola, December 2002 (work in progress) Threat Models introduced by Mobile IPv6 and Requirements for Security in Mobile IPv6 A. Mankin et al., November 2001 (work in progress) Issues in Protecting MIPv6 Binding Updates J. Arkko, November 2001 (work in progress) Securing MIPv6 Binding Updates Using Address Based Keys (ABKs) S. Okazaki et al., October 2002 (work in progress) Local Key Exchange for Mobile IPv6 Local Binding Security Association C. Liu, November 2002 (work in progress) MIPv6 BU Attacks and Defenses T. Aura, j. Arkko, March 2002 (work in progress) 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 45 of 57 Deliverable 15 Update Reviews of status of relevant standards V.1 6WINIT/0045 Authentication of Mobile IPv6 Binding Updates and Acknowledgments M. Roe et al., November 2001 (work in progress) Mobile IPv6 Authentication, Authorization, and Accounting Requirements S. Faccin et al., November 2002 (work in progress) AAA for mobile IPv6 F. Dupont et al., November 2001 (work in progress) Diameter Mobile IPv6 Application S. Faccin, F. Le et al., September 2002 (work in progress) MIPv6 User Authentication support through AAA J. Song, November 2001 (work in progress) Fast Handovers for Mobile IPv6 R. Koodli, October 2002 (work in progress) Mobile IPv6 Fast Handovers for 802.11 Networks P. McCann, November 2002 (work in progress) Simultaneous Bindings for Mobile IPv6 Fast Handoffs K. Malki, H. Soliman, July 2002 (work in progress) Mobile IPv6 handoff by Explicit Multicast Y. Ezaki, Y. Imai, June 2002 (work in progress) Per-flow movement in MIPv6 H. Soliman, K. Malki, C. Castelluccia, July 2002 (work in progress) QoS-Conditionalized Binding Update in Mobile IPv6 X. Fu et al., January 2002 (work in progress) Enhancements to Bi-directional Edge Tunnel Handover for IPv6 S. Faccin, B. Patil, R. Patil, S. Sreemanthula, October 2001 (work in progress) Localized Mobility Management Requirements for IPv6 C. Williams, March 2002 (work in progress) Localized Mobility Management for Mobile IPv6 in Distributed Manner J. Choi, W. Kang, November 2001 (work in progress) Localized Key Management for AAA in Mobile IPv6 M. Kim, Y. Mun, October 2002 (work in progress) Route Optimization Support for Localized Mobility Management Based on IPv6 Y. Han et al., July 2002 (work in progress) Nonfinal Mobility Header for Mobile IPv6 C. Perkins, F. Dupont, April 2002 (work in progress) Hierarchical Mobile IPv6 mobility management (HMIPv6) H. Soliman, C. Castelluccia, K. Malki, L. Bellier, October 2002 (work in progress) 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 46 of 57 Deliverable 15 Update Reviews of status of relevant standards V.1 6WINIT/0045 Supporting Mobile SSM Sources for IPv6 (MSSMSv6) C. Jelger, T. Noel, January 2002 (work in progress) MIPv6 IPCP configuration option for PPP IPv6CP J. Song, C. Chong, D. Leigh, October 2001 (work in progress) AAA for IPv6 Network Access P. Flykt, C. Perkins, T. Eklund, March 2002 (work in progress) SIM Authentication EAP extension over AAAv6 (SIM6) T. Kniveton, J. Malinen, July 2002 (work in progress) IPv6 for Some Second and Third Generation Cellular Hosts J. Arkko et al., June 2002 (work in progress) Global Connectivity for IPv6 Mobile Ad Hoc Networks R. Wakikawa et al., November 2002 (work in progress) IPv6 Reverse Routing Header and its application to Mobile Networks P. Thubert, M. Molteni, October 2002 (work in progress) Issues in Designing Mobile IPv6 Network Mobility with the MR-HA Bidirectional Tunnel (MRHA) A. Petrescu et al., November 2002 (work in progress) Two-plane and Three-tier QoS Framework for Mobile IPv6 Networks Z. Kan, J. Ma, May 2002 (work in progress) Hop-by-Hop Local Mobility Agents Probing for Mobile IPv6 V. Thing et al., October 2002 (work in progress) Enhanced Forwarding From Previous Care-of Address For Fast Mobile IPv6 Handovers (eFWD) Y. Gwon, A. Yegin, June 2002 (work in progress) Improving the Architectural Alignment for FMIPv6 J. Kempf, J. Wood, November 2002 (work in progress) Mobile IPv6 VPN using Gateway Home Agent H. Ohnishi, K. Suzuki, Y. Takagi, November 2002 (work in progress) Regional Mobile IPv6 mobility management K. Suh, October 2002 (work in progress) RObust Header Compression (ROHC): A Compression Profile for Mobile IPv6 H. Wang et al., December 2002 (work in progress) 3GPP/ETSI standards The specifications produced by 3GPP and adopted by ETSI are available on their respective web sites: http://www.3gpp.org http://www.etsi.org 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 47 of 57 Deliverable 15 6 Update Reviews of status of relevant standards V.1 6WINIT/0045 ACKNOWLEDGEMENTS: Some of the text in this Deliverable is taken from the 6LINK standardisation report from Mat Ford which summarises the state of the art standards activities which have been compiled from various sources and the IPv6 operations working group website. The list of IPv6 standards was provided by Mr. Simon Leinen of SWITCH in Switzerland; the latest version of this list is available at: http://www.switch.ch 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 48 of 57 Deliverable 15 7 Update Reviews of status of relevant standards V.1 6WINIT/0045 ACRONYMS AND ABBREVIATIONS 2G Second Generation Mobile Telecommunications (including GSM and GPRS technologies) 3DES Triple Data Encryption Standard 3G Third Generation Mobile Telecommunications (including WCDMA/UMTS technology) 3GPP 3rd Generation Partnership Project 6WINIT IPv6 Wireless INternet IniTiative 6to4 Automatic IPv6 in IPv4 tunnelling method, used router-to-router (RFC3056) AAA Authentication, Authorisation and Accounting ACC Academic Computer Centre "Cyfronet", a part of the UMM ACL Asynchronous Connectionless Links ACR American College of Radiologists ADPCM Adaptive Differential Pulse Code Modulation AF Assured Forwarding AH Authentication Header (IPsec) AIIH Assignment of IPv4 Addresses to IPv6 Hosts ALAN Application Level Active Networking ALG Application Layer Gateway AM_ADDR Active Member Address AN Active Networking ANP Anchor Points AP Access Point API Application Level Interface AR Access Routers AS Application Server ASP Application Service Provider ATM Asynchronous Transfer Mode B2BUA Back-to-Back User Agent BACK Binding Acknowledgement BAKE Binding Authentication Key Establishment BD_ADDR Bluetooth Device Address BGP Border Gateway Protocol BGW Border Gateway BNEP Bluetooth Network Encapsulation Protocol BSR Bootstrap Router BSS Base Station System 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 49 of 57 Deliverable 15 Update Reviews of status of relevant standards BU Binding Update CA Certificate Authority CAS Clinical Appointment System CBR Committed Bandwidth Rate CCU Clinical Care Unit CEN Comité Européen de Normalisation CHIME Centre for Health Informatics and Multi-professional Education CHTML Compact HTML CLI (1) Calling Line Identification V.1 6WINIT/0045 (2) Command Line Interface CN Correspondent Node COPS Common Open Policy Service CPE Customer Premises Equipment CPN Customer Premises Network CRL Certificate Revocation Lists CRTP Compressed RTP CS2 Coding Scheme 2 CSMA/CA Carrier Sense Multiple Access/Collision Avoidance CSP Cryptographic Service Provider CoA Care-of Address DAO Data Access Objects DCF Distributed Co-ordination Function DES Data Encryption Standard DHCP Dynamic Host Configuration Protocol DHCPv6 Dynamic Host Configuration Protocol for IPv6 DIAC Dedicated Inquiry Access Code DICOM Digital Imaging and Communications in Medicine DMZ Demilitarised Zone DNS Domain Name Server/System DS Differentiated Services DSCP Differentiated Services Code Point DSSS Direct Sequence Spread Spectrum DSTM Dual Stack Transition Mechanism DTI Dynamic Tunnelling Interface DTMF Dual-Tone Multi-Frequency DiffServ Differentiated Services DoS Denial of Service 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 50 of 57 Deliverable 15 Update Reviews of status of relevant standards Dx 6WINIT Deliverable x ECG Electrocardiogram/graphy EEP Execution Environment for Proxylets EF Expedited Forwarding EHR Electronic Healthcare Record EJB Enterprise JavaBeans Components EPR Electronic Patient Record ESP Encapsulation Security Payload ETCP Extended Transport Control Protocol ETRI Electronics and Telecommunications Research Institute ETSI European Telecommunications Standards Institute FDD Frequency Division Duplex FHR Federated Health Record FHSS Frequency Hopped Spread Spectrum FQDN Fully-Qualified Domain Name GANS Guardian ANgel System (UKT-RUS) GB Gigabyte (109 bytes) GEK Group Encryption Key GGSN Gateway GPRS Support Node GIAC General Inquiry Access Code GPRS General Packet Radio Service GRX GPRS Roaming Exchange GSM Global System for Mobile communications GSN GPRS Support Node GTP GPRS Tunnelling Protocol GW Gateway Routers HA Home Agent HAT High-quality Audio Tool HCSS Health Care Service System HI Host Identity HIP Host Identity Payload Protocol HIT Host Identity Tag HLP Host Layer Protocol HLR Home Location Register HMIP Hierarchical Mobile IP HSCSD High Speed Circuit Switched Data HTML HyperText Mark-up Language 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative V.1 6WINIT/0045 Page 51 of 57 Update Reviews of status of relevant standards Deliverable 15 HTTP HyperText Transfer Protocol HVCT High-quality Video Conferencing Tool ICMP(v6) Internet Control Message Protocol ICP Internet Content Provider ICU Intensive Care Unit IEC International Electrotechnical Commission IEEE Institute of Electrical and Electronics Engineers IETF Internet Engineering Task Force IGMP Internet Group Multicast Protocol IGP Internet Gateway Protocol IKE Internet Key Exchange IMS Interactive Multimedia Subsystem IMSI International Mobile Subscriber Identity IP Internet Protocol IPSec IP Security Protocol IPv4 Internet Protocol Version 4 IPv6 Internet Protocol Version 6 IR Infra-Red ISAKMP Internet Security Association and Key Management Protocol ISDN Integrated Services Digital Network ISO International Organization for Standardization ISP Internet Service Provider IST Information Society Technologies ITU International Telecommunications Union IntServ Integrated Services J2EE Java 2 Enterprise Edition J2SE Java 2 Standard Edition JDBC Java Database Connectivity JNDI Java Naming and Directory Interface JPEG Joint Photographic Experts' Group JSP Java Server Pages Kbit/s Kilobits per second Kbps Kilobits per second KLIPS Kernel IPSec Support LAN Local Area Network LDAP Lightweight Directory Access Protocol LI Lawful Interception 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative V.1 6WINIT/0045 Page 52 of 57 Deliverable 15 Update Reviews of status of relevant standards LON Local Operating Network MAN Metropolitan Area Network MD5 Message Digest 5 MDML Market Data Mark-up Language MGW Media Gateway MIDI Musical Instrument Digital Interface MIP Mobile Internet Protocol MIP WG Mobile IP Working Group MIPL Mobile IPv6 for Linux MLD Multicast Listener Discovery MLP Mobile Location Protocol MMUSIC Multiparty Multimedia Session Control MN Mobile Node MSC Mobile Service Centre MT Mobile Terminal Mbit/s Megabits per second Mbps Megabits per second NAI Network Access Identifier NAPT-PT Network Address Port Translation - Protocol Translation NAS Network Access Server NAT-PT Network Address Translation - Protocol Translation NEMA National Electrical Manufacturers' Association NFS Network File System NHS National Health Service (United Kingdom) NREN National Research and Education Network NRN National Research Network NTE Network Text Editor NetRAAD Network Radiology Acquisition, Access and Distribution O&M Operations and Management OCSP Online Certificate Status Protocol OSGi Open Services Gateway initiative PACS Picture Archiving and Communication System PAN Personal Area Networking PCBI Protocol Control Block Identifier PCM Pulse Code Modulation PDA Personal Digital Assistant PDCP Packet Data Convergence Protocol 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative V.1 6WINIT/0045 Page 53 of 57 Deliverable 15 Update Reviews of status of relevant standards PDN Packet Data Network PDP Packet Data Protocol PDR Per Domain Reservation PDU Protocol Data Unit PEP Policy Enforcement Point PHB Per-Hop Behaviour PHR Per-Hop Reservation PIM Protocol Independent Multicast PIM-SM PIM Sparse Mode PKCS Public Key Cryptography Standard PKI Public Key Infrastructure PLIM Presence and Location Instant Messaging PLMN Public Land Mobile Network POP Point of Presence PPP Point-to-Point Protocol PS Paging Servers PSK Phase Shift Keying PSTN Public Switched Telephone Network PVC Permanent Virtual Circuit QoS Quality of Service RADIUS Remote Access Dial-in User Server RAN Radio Access Network RAS Remote Access Server RAT Robust Audio Tool RFC (Internet) Request for Comments RM Reflection Manager RMD Resource Management in DiffServ RMI Remote Method Invocation RODA Resource Management in DiffServ On DemAnd ROHC Robust Header compression RP Rendezvous Point RQM RTP Quality Matrix RSA Rivest-Shamir-Adleman (encryption algorithm) RSVP Resource ReSerVation Protocol RTCP RTP control protocol RTP Real Time Transport Protocol RTSP Real Time Streaming Protocol 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative V.1 6WINIT/0045 Page 54 of 57 Deliverable 15 Update Reviews of status of relevant standards RTT Round-Trip Time RUS Rechenzentrum Universität Stuttgart SA Security Association(s) SADB Security Association Database SAP Session Announcement Protocol SASL Simple Authentication and Security Layer SCEP Simple Certificate Enrolment Protocol SCO Synchronous Connection Oriented SCS (1) Secure Conference Store V.1 6WINIT/0045 (2) Service Capability Server SCTP Stream Control Transmission Protocol SDH Synchronous Digital Hierarchy SDP Session Description Protocol SDR Session Directory Tool SGSN Serving GSN SGW (1) Signalling Gateway (2) Security Gateway SIIT Stateless IP/ICMP Translation Algorithm SIMA SImultaneous Multi-Access SIP Session Initiation Protocol SMF Service Management Framework (IBM) SN Service Network SNMP Simple Network Management Protocol SONET Synchronous Optical NETwork SPAR SDP Parser Applet SPD Security Policy Database SRM Scalable Reliable Multicast protocol SRTP Secure Real Time Transport Protocol SSH Secure SHell SSL Secure Socket Layer SecGW Security Gateway SoFAR Southampton Framework for Agent Research TAG Transcoding Active Gateway TB Tunnel Broker TCP Transmission Control Protocol TDD Time Division Duplex TE Terminal Equipment 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative Page 55 of 57 Deliverable 15 Update Reviews of status of relevant standards TEID Tunnel Endpoint IDentifier TEIN TransEurasia Information Network TETRA Trans-European Trunked Radio TLA Top Level Aggregator TLS Transport Layer Security TS Tunnel Server TTP Trusted Third Party ToS Type of Service UAC User Agent Client UAS User Agent Server UCL University College London UDP User Datagram Protocol UIML User Interface Markup Language UKT Universitätsklinikum Tübingen UMM University of Mining and Metallurgy (Krakow, Poland) UMTS Univeral Mobile Telecommunications System UR User Registries UTRA Universal Terrestrial Radio Access VIC Video Conference Tool VJ Van Jacobsen VLAN Virtual Local Area Network VPN Virtual Private Network VTT Technical Research Centre of Finland VoIP Voice over IP W3C World-Wide Web Consortium WAE Wireless Application Environment WAN Wide Area Network WAP Wireless Application Protocol WBD Whiteboard (application) WCDMA Wideband Code Division Multiple Access WDP Wireless Datagram Protocol WEP Wire Equivalent Privacy WLAN Wireless Local Area Network WML Wireless Mark-up Language WTA Wireless Telephony Application WTLS Wireless Transport Layer Security WWW World-Wide Web 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative V.1 6WINIT/0045 Page 56 of 57 Deliverable 15 Update Reviews of status of relevant standards X10 Powerline carrier protocol XHTML Extensible Hypertext Mark-up Language XML Extensible Markup Language 19-Jan-03 6WINIT – IPv6 Wireless Internet IniTiative V.1 6WINIT/0045 Page 57 of 57