I-D ACTION:draft-ietf-ospf-ospfv3-update-05.txt

Internet-Drafts@ietf.org Fri, 12 August 2005 20:00 UTC

Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E3fhQ-0003kS-1a for ospf-archive@megatron.ietf.org; Fri, 12 Aug 2005 16:00:16 -0400
Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16637 for <ospf-archive@LISTS.IETF.ORG>; Fri, 12 Aug 2005 16:00:09 -0400 (EDT)
Received: from vms.dc.lsoft.com ( by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <6.010C9923@cherry.ease.lsoft.com>; Fri, 12 Aug 2005 16:00:07 -0400
Received: by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 14.4) with spool id 82333790 for OSPF@PEACH.EASE.LSOFT.COM; Fri, 12 Aug 2005 16:00:02 -0400
Received: from by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0m) with TCP; Fri, 12 Aug 2005 15:50:01 -0400
Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1E3fXW-0004Fe-5r; Fri, 12 Aug 2005 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-ID: <E1E3fXW-0004Fe-5r@newodin.ietf.org>
Date: Fri, 12 Aug 2005 15:50:02 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-ospf-ospfv3-update-05.txt
Comments: To: i-d-announce@ietf.org
Precedence: list

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Open Shortest Path First IGP Working Group of the IETF.

	Title		: OSPF for IPv6
	Author(s)	: D. Ferguson, et al.
	Filename	: draft-ietf-ospf-ospfv3-update-05.txt
	Pages		: 95
	Date		: 2005-8-12
This document describes the modifications to OSPF to support version
   6 of the Internet Protocol (IPv6).  The fundamental mechanisms of
   OSPF (flooding, DR election, area support, SPF calculations, etc.)
   remain unchanged.  However, some changes have been necessary, either
   due to changes in protocol semantics between IPv4 and IPv6, or simply
   to handle the increased address size of IPv6.

   Changes between OSPF for IPv4 and this document include the
   following.  Addressing semantics have been removed from OSPF packets
   and the basic LSAs.  New LSAs have been created to carry IPv6
   addresses and prefixes.  OSPF now runs on a per-link basis rather
   than on a per-IP-subnet basis.  Flooding scope for LSAs has been
   generalized.  Authentication has been removed from the OSPF protocol
   and instead relies on IPv6's Authentication Header and Encapsulating
   Security Payload.

   Even with larger IPv6 packet, most packets in OSPF for IPv6 are
   almost as compact as those in OSPF for IPv4.  Most fields and packet-
   size limitations present in OSPF for IPv4 have been relaxed.  In
   addition, option handling has been made more flexible.

   All of OSPF for IPv4's optional capabilities, including demand
   circuit support, NSSA areas, and the multicast extensions to OSPF
   (MOSPF) are also supported in OSPF for IPv6.

A URL for this Internet-Draft is:

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-ospf-ospfv3-update-05.txt".

A list of Internet-Drafts directories can be found in
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
In the body type:
	"FILE /internet-drafts/draft-ietf-ospf-ospfv3-update-05.txt".
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the