draft-ietf-dna-simple-15.txt   draft-ietf-dna-simple-16.txt 
Network Working Group S. Krishnan Network Working Group S. Krishnan
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: Standards Track G. Daley Intended status: Standards Track G. Daley
Expires: February 10, 2011 NetStar Networks Expires: February 11, 2011 NetStar Networks
August 9, 2010 August 10, 2010
Simple procedures for Detecting Network Attachment in IPv6 Simple procedures for Detecting Network Attachment in IPv6
draft-ietf-dna-simple-15 draft-ietf-dna-simple-16
Abstract Abstract
Detecting Network Attachment allows hosts to assess if its existing Detecting Network Attachment allows hosts to assess if its existing
addressing or routing configuration is valid for a newly connected addressing or routing configuration is valid for a newly connected
network. This document provides simple procedures for detecting network. This document provides simple procedures for detecting
network attachment in IPv6 hosts, and procedures for routers to network attachment in IPv6 hosts, and procedures for routers to
support such services. support such services.
Status of this Memo Status of this Memo
skipping to change at page 1, line 35 skipping to change at page 1, line 35
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 10, 2011. This Internet-Draft will expire on February 11, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 12, line 14 skipping to change at page 12, line 14
5.7. Response Gathering 5.7. Response Gathering
5.7.1. Receiving Neighbor Advertisements 5.7.1. Receiving Neighbor Advertisements
When a Neighbor Advertisement is received from a router in response When a Neighbor Advertisement is received from a router in response
to a NS probe, the host MUST verify that both the IPv6 and link layer to a NS probe, the host MUST verify that both the IPv6 and link layer
(MAC) addresses of the router match the expected values before (MAC) addresses of the router match the expected values before
utilizing the configuration associated with the detected network utilizing the configuration associated with the detected network
(prefixes, MTU etc.). The host MUST then go through the SDAT and (prefixes, MTU etc.). The host MUST then go through the SDAT and
mark the addresses associated with the router as operable. mark the addresses (both SLAAC and DHCPv6 acquired) associated with
the router as operable.
5.7.2. Receiving Router Advertisements 5.7.2. Receiving Router Advertisements
On reception of a Router Advertisement the host MUST go through the On reception of a Router Advertisement the host MUST go through the
SDAT and mark all the addresses associated with the router as SDAT and mark all the addresses associated with the router (both
inoperable. The host MUST then process the Router Advertisement as SLAAC and DHCPv6 acquired) as inoperable. The host MUST then process
specified in Section 6.3.4. of [RFC4861]. the Router Advertisement as specified in Section 6.3.4. of [RFC4861].
5.7.3. Conflicting results 5.7.3. Conflicting results
5.7.3.1. Conflicting results between RS and NS probes 5.7.3.1. Conflicting results between RS and NS probes
Where the conclusions obtained from the Neighbor Solicitation/ Where the conclusions obtained from the Neighbor Solicitation/
Advertisement from a given router and the RS/RA exchange with the Advertisement from a given router and the RS/RA exchange with the
same router differ, the results obtained from the RS/RA will be same router differ, the results obtained from the RS/RA will be
considered definitive. In case the Neighbor Advertisement was considered definitive. In case the Neighbor Advertisement was
secured using SEND and the Router Advertisement was not, the host secured using SEND and the Router Advertisement was not, the host
 End of changes. 5 change blocks. 
8 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/