[Editorial Errata Reported] RFC5252 (3310)

The following errata report has been submitted for RFC5252,
"OSPF-Based Layer 1 VPN Auto-Discovery".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5252&eid=3310

--------------------------------------
Type: Editorial
Reported by: Kris Michielsen <kmichiel <at> cisco.com>

Section: 2.1

Original Text
-------------
   L1VPN Info TLV
      A single TLV, as defined in Section 3.2, MUST be present.  If more
      than one L1VPN Info TLV is present, only the first TLV is
      processed and the others MUST be ignored on receipt.

Corrected Text
--------------
   L1VPN Info TLV
      A single TLV, as defined in Section 2.2, MUST be present.  If more
      than one L1VPN Info TLV is present, only the first TLV is
      processed and the others MUST be ignored on receipt.

Notes
-----

RFC 5523 on OSPFv3-Based Layer 1 VPN Auto-Discovery

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5523

        Title:      OSPFv3-Based Layer 1 VPN Auto-Discovery 
        Author:     L. Berger
        Status:     Experimental
        Date:       April 2009
        Mailbox:    lberger <at> labn.net
        Pages:      12
        Characters: 23473
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-l1vpn-ospfv3-auto-discovery-03.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5523.txt

This document defines an OSPFv3-based (Open Shortest Path First version 3)
Layer 1 Virtual Private Network (L1VPN) auto-discovery
mechanism.  This document parallels the existing OSPF version 2 L1VPN
auto-discovery mechanism.  The notable functional difference is the
support of IPv6.  This memo defines an Experimental Protocol for 
the Internet community.

This document is a product of the Layer 1 Virtual Private Networks Working Group of the IETF.

EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any

WG Action: Conclusion of Layer 1 Virtual Private Networks (l1vpn)

The Layer 1 Virtual Private Networks (l1vpn) working group in the Routing
Area has concluded.

The IESG contact persons are David Ward and Ross Callon.

The mailing list will remain active.

Fw: Closing L1VPN WG

Hi,

One of Dave's last acts as AD was to issue the closure notice for the L1VPN
working group.

The OSPFv3 draft is with the RFC Editor and being edited at the moment.

This mailing list will stay open for discussion of L1VPN issues.

Thanks to everyone for the hard work to complete the RFCs.

Adrian
----- Original Message ----- 
From: "David Ward" <dward <at> cisco.com>
To: "IESG Secretary" <iesg-secretary <at> ietf.org>; "IESG IESG" <iesg <at> ietf.org>
Cc: "Ross Callon" <rcallon <at> juniper.net>; "Hamid Ould-Brahim"
<hbrahim <at> nortel.com>; "Adrian Farrel" <adrian <at> olddog.co.uk>; "David Ward"
<dward <at> cisco.com>; "Tomonori TAKEDA" <takeda.tomonori <at> lab.ntt.co.jp>
Sent: Monday, March 23, 2009 4:45 PM
Subject: Closing L1VPN WG

> IESG-Secretary -
>
> This note is to state that the L1VPN WG is closed. Please keep the  email
> list open.
>
> -DWard
>

Document Action: 'OSPFv3 Based Layer 1 VPN Auto-Discovery' to Experimental RFC

The IESG has approved the following document:

- 'OSPFv3 Based Layer 1 VPN Auto-Discovery '
   <draft-ietf-l1vpn-ospfv3-auto-discovery-03.txt> as an Experimental RFC

This document is the product of the Layer 1 Virtual Private Networks 
Working Group. 

The IESG contact persons are David Ward and Ross Callon.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l1vpn-ospfv3-auto-discovery-03.txt

Technical Summary

   This document defines an Open Shortest Path First (OSPF) version 3
   based Layer-1 Virtual Private Network (L1VPN) auto-discovery
   mechanism.  This document parallels the existing OSPF version 2 L1VPN
   auto-discovery mechanism.  The notable functional difference is the
   support of IPv6.

Working Group Summary

   Was there anything in the WG process that is worth noting?
   For example, was there controversy about particular points 
   or were there decisions where the consensus was
   particularly rough? No issues

Document Quality

Resigning as chair

Hi L1VPN,

As I have been appointed Routing Area Director to take over from Dave at the
end of the San Francisco meeting, it is appropriate that I step down as
co-chair of L1VPN. I leave you in the capable hands of Tomonori and Hamid.

FWIW, the last I-D (the OSPFv3 experimental status draft) has just been
approved and will move forward to the RFC Editor queue.

If you have any issues or questions please take them to the chairs or to the
current ADs.

Many thanks for all your constructive work.

Adrian

iPOP 2009 CFP Deadline Extended to March 2nd

Dear CAMP, PCE, L1VPN, MPLS and MPLS-TP subscribers,
(Apologies for disturbing MLs with multiple copies; 
appreciated if you can forward this to potentially interested people.)

Submission deadline to iPOP 2009, the 5th Conference on IP + Optical
Network, has been extended to March 2nd. See details below.

----
Following the successful events of iPOP, the 5th Conference on
IP + Optical Network (iPOP 2009) will be held at NICT Headquarters, 
Koganei, Tokyo, Japan, June 11-12, 2009.
The conference is intended to share among the industry and the academia, 
the knowledge, new findings, and experience on the state-of-the art of IP 
and optical networking technologies. It features technical sessions and 
planned exhibitions. The opportunity to participate is open to all.
See Call for presentation details at 
http://www.pilab.jp/ipop2009/

Important Dates:
Submission deadline of one page summary: March 2, 2009
Notification of acceptance: April 3, 2009
Submission deadline of final presentation slides: April 24, 2009

The Technical Program Committee for iPOP 2009 is soliciting presentation
proposals for this conference. Protocol design, experiment, theory,
implementation, and operational experiences are solicited.
The topics of the conference will include but not limited to the following:
* GMPLS/ASON technologies
* GMPLS Network management, OA&M
* Multi-layer network (MLN) / Multi-region network (MRN)

iPOP 2009 Call for Presentations

Dear CAMP, PCE, L1VPN, MPLS and MPLS-TP subscribers,
(Apologies for multiple copies, appreciated if you can forward to 
potentially interested people.

Following the successful events of iPOP, the 5th Conference on IP + Optical
Network (iPOP 2009) will be held at NICT Headquarters, Koganei, Tokyo,
Japan, June 11-12, 2009.
The conference is intended to share among the industry and the academia, the
knowledge, new findings, and experience on the state-of-the art of IP and
optical networking technologies. It features technical sessions and planned
exhibitions. The opportunity to participate is open to all.
See Call for presentation details at 
http://www.pilab.jp/ipop2009/

Important Dates:
Submission deadline of one page summary: February 20, 2009
Notification of acceptance: April 3, 2009
Submission deadline of final presentation slides: April 24, 2009

The Technical Program Committee for iPOP 2009 is soliciting presentation
proposals for this conference. Protocol design, experiment, theory,
implementation, and operational experiences are solicited.
The topics of the conference will include but not limited to the following:
* GMPLS/ASON technologies
* GMPLS Network management, OA&M
* Multi-layer network (MLN) / Multi-region network (MRN)
* Path Computation Element (PCE), Traffic engineering
* Inter-area/Inter-AS network
* L1VPN, Bandwidth on Demand, and Photonic Grid
* Wavelength Switched Optical Networks  (WSON), Routing wavelength

No meeting in San Francisco

Hi,

The only outstanding working group draft (OSPFv3 autodiscovery) has just 
been updated after IESG review and we hope it will move to the FC Editor 
soon.

The chairs believe that there is no other business and no need for a 
face-to-face meeting in San Francisco.

Please let us know if you disagree.

Cheers,
Adrian 

I-D Action:draft-ietf-l1vpn-ospfv3-auto-discovery-03.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Layer 1 Virtual Private Networks Working Group of the IETF.

	Title           : OSPFv3 Based Layer 1 VPN Auto-Discovery
	Author(s)       : L. Berger
	Filename        : draft-ietf-l1vpn-ospfv3-auto-discovery-03.txt
	Pages           : 12
	Date            : 2009-01-12

This document defines an Open Shortest Path First (OSPF) version 3
based Layer-1 Virtual Private Network (L1VPN) auto-discovery
mechanism.  This document parallels the existing OSPF version 2 L1VPN
auto-discovery mechanism.  The notable functional difference is the
support of IPv6.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l1vpn-ospfv3-auto-discovery-03.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Layer 1 Virtual Private Networks Working Group of the IETF.

Last Call: draft-ietf-l1vpn-ospfv3-auto-discovery (OSPFv3 Based Layer 1 VPN Auto-Discovery) to Experimental RFC

The IESG has received a request from the Layer 1 Virtual Private Networks

 
WG (l1vpn) to consider the following document:

- 'OSPFv3 Based Layer 1 VPN Auto-Discovery '
   <draft-ietf-l1vpn-ospfv3-auto-discovery-02.txt> as an Experimental RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf <at> ietf.org mailing lists by 2008-11-10. Exceptionally, 
comments may be sent to iesg <at> ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-l1vpn-ospfv3-auto-discovery-02.txt

IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=17312&rfc_flag=0