Hello,

Acee, Ran, and I have updated the following draft to address the feedback at 
the last meeting and on the mailing list.  In particular, a new section on IPv4 
use case has been added, and the edits that Karsten suggested back on Feb. 17, 
2014 have also been incorporated.

Thanks,
Helen

-----Original Message-----
From: [email protected] [mailto:[email protected]] 
Sent: Wednesday, July 02, 2014 9:27 AM
To: R. Atkinson; Ing-Wher Chen; Ing-Wher Chen; Acee Lindem; Acee Lindem
Subject: New Version Notification for 
draft-chen-ospf-transition-to-ospfv3-01.txt


A new version of I-D, draft-chen-ospf-transition-to-ospfv3-01.txt
has been successfully submitted by I. Chen and posted to the IETF repository.

Name:           draft-chen-ospf-transition-to-ospfv3
Revision:       01
Title:          OSPFv3 over IPv4 for IPv6 Transition
Document date:  2014-07-02
Group:          Individual Submission
Pages:          9
URL:            
http://www.ietf.org/internet-drafts/draft-chen-ospf-transition-to-ospfv3-01.txt
Status:         
https://datatracker.ietf.org/doc/draft-chen-ospf-transition-to-ospfv3/
Htmlized:       
http://tools.ietf.org/html/draft-chen-ospf-transition-to-ospfv3-01
Diff:           
http://www.ietf.org/rfcdiff?url2=draft-chen-ospf-transition-to-ospfv3-01

Abstract:
   This document defines a mechanism to use IPv4 to transport OSPFv3
   packets, in order to facilitate transition from IPv4-only to IPv6 and
   dual-stack within a routing domain.  Using OSPFv3 over IPv4 with the
   existing OSPFv3 Address Family extension can simplify transition from
   an OSFPv2 IPv4-only routing domain to an OSPFv3 dual-stack routing
   domain.

                                                                                
  


Please note that it may take a couple of minutes from the time of submission 
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

_______________________________________________
OSPF mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ospf

Reply via email to