Dimitri.Papadimitriou | 1 Oct 2006 16:05
Picon
Picon

Re: Comments on draft-li-ccamp-multinodes-gr-proc-00.txt,

dan - 

ok - do we have a sense of the probability of multiple independent nodes 
failures - is that a common failure scenario operators are facing (and not 
a marginal case) ?

or are we addressing common bugs affecting common equipment - in this case 
this topics is outside scope of CCAMP ?

pls read between the lines i start to be seriously concerned by GMPLS 
protocol over-engineering - if the set currently available technique is 
still not enough for base deployment then it means the issue(s) is/are 
sitting somewhere else -

thanks,
- d.

Dan Li <danli <at> huawei.com>
30/09/2006 07:42

        To:     Dimitri PAPADIMITRIOU/BE/ALCATEL <at> ALCATEL
        cc:     ccamp <ccamp <at> ops.ietf.org>, Olufemi Komolafe 
<femi <at> dcs.gla.ac.uk>, gjhhit <at> huawei.com, owner-ccamp <at> ops.ietf.org
        Subject:        Re: Comments on 
draft-li-ccamp-multinodes-gr-proc-00.txt,

Hi Dimitri,

There is nothing wrong with the GR draft, the mechanism described in that 
draft doesn't need any remedial patch, and it is applied to this draft. 
(Continue reading)

Adrian Farrel | 1 Oct 2006 18:16
Picon

Re: Comments on draft-li-ccamp-multinodes-gr-proc-00.txt,

Dimitri,

I understand your concern about over-engineering. There is a tendency for 
"protocol engineers" to sit and look for corner cases in the protocol that 
they might be able to write specifications for. It might be more useful if 
they wrote implementations and tested the current protocols.

But, I don't think Dan is guilty. His draft proposes no protocol extensions 
and no new procedures. In fact, it is a clarification that no new protocol 
elements are required - the existing work already covers all cases without 
any further work being necessary. I think this is a useful thing to do, but 
not something I would expect to spend a lot of CCAMP cycles on.

Perhaps most useful would be to have a review from the authors of the 
original Graceful Restart draft to confirm that the procedures have been 
correctly interpreted and applied.

As to whether this is a common problem, that might be a question for 
software stack implementers, chip manufacturers, and power supply vendors. 
But clearly we thought it was possible for a single control plane instance 
to fail.

A
----- Original Message ----- 
From: <Dimitri.Papadimitriou <at> alcatel.be>
To: "Dan Li" <danli <at> huawei.com>
Cc: "ccamp" <ccamp <at> ops.ietf.org>; "Olufemi Komolafe" <femi <at> dcs.gla.ac.uk>; 
<gjhhit <at> huawei.com>; <owner-ccamp <at> ops.ietf.org>
Sent: Sunday, October 01, 2006 3:05 PM
Subject: Re: Comments on draft-li-ccamp-multinodes-gr-proc-00.txt,
(Continue reading)

Adrian Farrel | 2 Oct 2006 11:15
Picon

Fw: 67th IETF - DRAFT Meeting Agenda

Hi,

The early, draft, unconfirmed agenda for San Diego has CCAMP on Monday 
morning at 9am.

Adrian
----- Original Message ----- 
From: "IETF Agenda" <agenda <at> ietf.org>
To: "Working Group Chairs" <wgchairs <at> ietf.org>
Cc: <irsg <at> isi.edu>; <bofcharis <at> ietf.org>
Sent: Monday, October 02, 2006 5:03 AM
Subject: 67th IETF - DRAFT Meeting Agenda

> The DRAFT agenda for the 67th IETF Meeting can be found at:
> http://www.ietf.org/meetings/67-agenda.txt
>
> Please send comments to agenda <at> ietf.org
>
> Upcoming Cutoff Dates:
> October 11, Wednesday - Cutoff date for requests to reschedule Working
> Group and BOF meetings 09:00 ET (13:00 UTC/GMT)
> October 16, Monday - Final agenda to be published.

Internet-Drafts | 5 Oct 2006 21:50
Picon
Favicon

I-D ACTION:draft-ietf-ccamp-gmpls-ason-routing-ospf-02.txt

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Common Control and Measurement Plane Working Group of the IETF.

	Title		: OSPFv2 Routing Protocols Extensions for ASON Routing
	Author(s)	: D. Papadimitriou
	Filename	: draft-ietf-ccamp-gmpls-ason-routing-ospf-02.txt
	Pages		: 0
	Date		: 2006-10-5
	
The Generalized MPLS (GMPLS) suite of protocols has been defined to 
   control different switching technologies as well as different 
   applications. These include support for requesting TDM connections 
   including SONET/SDH and Optical Transport Networks (OTNs). 

   This document provides the extensions of the OSPFv2 Link State 
   Routing Protocol to meet the routing requirements for an 
   Automatically Switched Optical Network (ASON) as defined by ITU-T.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-gmpls-ason-routing-ospf-02.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request <at> 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 
(Continue reading)

Jasmin Shrestha | 5 Oct 2006 23:25
Favicon

10 days Left to MPLS 2006 International Conference -Washington D.C

Only 10 days Left to MPLS 2006!

 

Register for MPLS 2006 International Conference Today!

OCTOBER 15-18, 2006
Omni Shoreham Hotel
WASHINGTON, D.C.
9th Annual International Conference on MPLS and Related Technologies

 

To register:
http://www.mpls2006.com/onlineregis.htm

 

Conference Program:

http://www.mpls2006.com/program.htm

 

Conference Sponsors:

http://www.mpls2006.com/sponsors.htm

 

Interop Demonstration

http://www.mpls2006.com/program.htm#interop

 

 

Internet-Drafts | 6 Oct 2006 21:50
Picon
Favicon

I-D ACTION:draft-ietf-ccamp-gmpls-segment-recovery-03.txt

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Common Control and Measurement Plane Working Group of the IETF.

	Title		: GMPLS Based Segment Recovery
	Author(s)	: L. Berger, et al.
	Filename	: draft-ietf-ccamp-gmpls-segment-recovery-03.txt
	Pages		: 25
	Date		: 2006-10-6
	
This document describes protocol specific procedures for GMPLS
   (Generalized Multi-Protocol Label Switching) RSVP-TE (Resource
   ReserVation Protocol - Traffic Engineering) signaling extensions to
   support label switched path (LSP) segment protection and restoration.
   These extensions are intended to complement and be consistent with
   the Extensions for End-to-End GMPLS-based Recovery.  Implications and
   interactions with Fast Reroute are also addressed.  This document
   also updates the handling of Notify_Request objects.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-gmpls-segment-recovery-03.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request <at> 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-ccamp-gmpls-segment-recovery-03.txt".

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

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

Send a message to:
	mailserv <at> ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ccamp-gmpls-segment-recovery-03.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
Internet-Draft.
Attachment: message/external-body, 152 bytes
Internet-Drafts | 6 Oct 2006 21:50
Picon
Favicon

I-D ACTION:draft-ietf-ccamp-te-node-cap-02.txt

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Common Control and Measurement Plane Working Group of the IETF.

	Title		: IGP Routing Protocol Extensions for Discovery of Traffic Engineering Node Capabilities
	Author(s)	: J. Vasseur, et al.
	Filename	: draft-ietf-ccamp-te-node-cap-02.txt
	Pages		: 15
	Date		: 2006-10-6
	
It is highly desired in several cases, to take into account Traffic 
   Engineering (TE) node capabilities during Multi Protocol Label 
   Switching (MPLS) Traffic Engineered Label Switched Path (TE-LSP)  
   selection, such as for instance the capability to act as a branch 
   Label Switching Router (LSR) of a Point-To-MultiPoint (P2MP) LSP. 
   This requires advertising these capabilities within the Interior 
   Gateway Protocol (IGP). For that purpose, this document specifies 
   Open Shortest Path First (OSPF) and Intermediate System-Intermediate 
   System (IS-IS) traffic engineering extensions for the advertisement 
   of control plane and data plane traffic engineering node 
   capabilities.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-te-node-cap-02.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request <at> 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-ccamp-te-node-cap-02.txt".

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

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

Send a message to:
	mailserv <at> ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ccamp-te-node-cap-02.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
Internet-Draft.
Attachment: message/external-body, 141 bytes
Attachment (draft-ietf-ccamp-te-node-cap-02.txt): message/external-body, 68 bytes
Adrian Farrel | 7 Oct 2006 14:52
Picon

Fw: I-D ACTION:draft-andersson-rtg-gmpls-change-04.txt

Hi,

A new revision of the MPLS and GMPLS change process I-D is available. This 
process appears to be stable and we are thinking of taking to the IESG quite 
soon, so review it now or risk having to live with it.

The changes in this revision are largely to clarify the use of the 
Preliminary Investigation phase.

===
Section 1.2
Change 2119 boiler plate to
   Although this document is not a protocol definition, the key words
   "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
   "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document
   are to be interpreted as described in RFC 2119 [RFC2119]. This usage
   is chosen to make the steps and procedures completely clear.
===
Section 2.3 final paragraph
ADD
   It should be noted that the first stage in the change process is an
   optional Preliminary Investigation (see Section 4.2.1). This stage is
   explicitly included to allow external organizations to discuss
   requirements and proposed uses of the (G)MPLS technologies without
   the need to first develop Internet-Drafts, and builds on existing
   liaison processes where they exist.
===
Section 2.4
ADD
   o  Preliminary Investigation
      An optional preliminary phase that may be used to exchange views
      on a proposed requirement and usage of the (G)MPLS technologies
      without going to the effort of writing an Internet-Draft. This
      phase may be particularly useful to SDOs that have already
      invested heavily in documenting a problem statement, or may be
      used by anyone who wishes to hold discussions on the use of
      (G)MPLS.
===
Section 3
ADD para 2
   Whenever there is reason to believe that a particular problem may be
   solved by use of or extensions to the (G)MPLS protocols, a
   preliminary investigation phase may be used to discuss the
   requirements with the IETF. This may lead to an understanding that
   the problem is already solved, is outside the scope of the IETF, or
   requires more investigation possibly leading to changes to the
   (G)MPLS protocols.
===
Section 4.2.1 para 2
ADD
   In fact, although this step is described
   as lightweight because no Internet-Draft is required and because the
   nature of the step is discursive, it may be the case that this step
   involves considerable technical discussions and may, in fact, be an
   extensive, substantive exchange of opinions.
===
Section 4.2.1 para 3
s/may/MAY/
===
Section 4.2.1 final para
ADD
   A possible outcome of this preliminary invsetigation is that the
   requirements and problem are understood, but agreed to be out of
   scope for the IETF. Alternatively it may be that the problem can be
   solved with existing protocols.
===
Section 5.2 bullet 1
ADD
   (see Section 4.2.1)
===
Section 5.2 bullet 2
ADD
   (see Section 4.2.1)
===
Section 8 para 4
s/may/MAY/
===

----- Original Message ----- 
From: <Internet-Drafts <at> ietf.org>
To: <i-d-announce <at> ietf.org>
Sent: Wednesday, October 04, 2006 11:50 PM
Subject: I-D ACTION:draft-andersson-rtg-gmpls-change-04.txt

>A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
> Title : Change Process for Multiprotocol Label Switching (MPLS) and 
> Generalized MPLS (GMPLS) Protocols and Procedures
> Author(s) : L. Andersson, A. Farrel
> Filename : draft-andersson-rtg-gmpls-change-04.txt
> Pages : 22
> Date : 2006-10-4
>
> The issues surrounding the extensibility of IETF protocols have been
>   widely debated. These issues include when it is reasonable to
>   extend IETF protocols with little or no review, and when extensions
>   or variations need to be reviewed by the larger IETF community.
>   Experience with IETF protocols has shown that extensibility of
>   protocols without early IETF review can cause problems.
>
>   The Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS)
>   suites of protocols have become popular for a number of applications
>   and deployment scenarios. One result of this popularity is a large
>   number of suggestions for modifications and extensions.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-andersson-rtg-gmpls-change-04.txt
>
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request <at> 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-andersson-rtg-gmpls-change-04.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> mailserv <at> ietf.org.
> In the body type:
> "FILE /internet-drafts/draft-andersson-rtg-gmpls-change-04.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
> Internet-Draft.

Adrian Farrel | 9 Oct 2006 12:08
Picon

CCAMP agenda for San Diego

Hi,

Deborah and I will be working on the agenda some time early next week.

Please send us your requests.

Recall that the purpose of the meeting is to have active and constructive 
debate, not to present your work. Everyone can read your drafts so there is 
no requirement to present them. You should be asking for an agenda slot if 
you feel that:

- there is some point that has been discussed on the list that needs
  further debate
- you have questions or issues that you need the working group to
  help you resolve
- you have made a substantial change to a draft that you think people
  will have missed and might object to

New work can also be considered for an agenda slot where you would expect to 
discover whether there is support for the work. Criteria include:
- does the work address a charter milestone?
- is the work in scope for the working group?
- has the draft been discussed on the mailing list?

Thanks,
Adrian 

Adrian Farrel | 9 Oct 2006 19:11
Picon

Fw: Internet-Drafts Submission Cutoff Dates for the 67th IETF Meeting in San Diego, California, USA

Heads up.

Adrian
----- Original Message ----- 
From: <ietf-secretariat <at> ietf.org>
To: <ietf-announce <at> ietf.org>
Sent: Monday, October 09, 2006 5:20 PM
Subject: Internet-Drafts Submission Cutoff Dates for the 67th IETF Meeting 
in San Diego, California, USA

>
> There are two (2) Internet-Draft cutoff dates for the 67th
> IETF Meeting in San Diego, California, USA:
>
> October 16th: Cutoff Date for Initial (i.e., version -00)
> Internet-Draft Submissions
>
> All initial Internet-Drafts (version -00) must be submitted by Monday,
> October 16th at 9:00 AM ET. As always, all initial submissions with a
> filename beginning with "draft-ietf" must be approved by the
> appropriate WG Chair before they can be processed or announced.  The
> Secretariat would appreciate receiving WG Chair approval by Monday,
> October 9th at 9:00 AM ET.
>
> October 23rd: Cutoff Date for Revised (i.e., version -01 and higher)
> Internet-Draft Submissions
>
> All revised Internet-Drafts (version -01 and higher) must be submitted
> by Monday, October 23rd at 9:00 AM ET.
>
> Initial and revised Internet-Drafts received after their respective
> cutoff dates will not be made available in the Internet-Drafts
> directory or announced until on or after Monday, November 6th at 9:00
> AM ET, when Internet-Draft posting resumes.  Please do not wait until
> the last minute to submit.
>
> Thank you for your understanding and cooperation. If you have any
> questions or concerns, then please send a message to
> internet-drafts <at> ietf.org.
>
> The IETF Secretariat
>
> FYI: The Internet-Draft cutoff dates as well as other significant dates
> for the 67th IETF Meeting can be found at 
> http://www.ietf.org/meetings/cutoff_dates_67.html.
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce <at> ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce
>
>
> 


Gmane