1 May 2008 14:48
1 May 2008 14:54
Re: draft-ietf-pwe3-tdm-mib-10.txt
Bert Wijnen - IETF <bertietf <at> bwijnen.net>
2008-05-01 12:54:27 GMT
2008-05-01 12:54:27 GMT
As MIB-doctor I am now happy with this revision except for one
little nit (well... it is a bit more, but the change
required is very small):
pwTDMCfgEntry OBJECT-TYPE
SYNTAX PwTDMCfgEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"These parameters define the characteristics of a
TDM PW. They are grouped here to ease NMS burden.
Once an entry is created here it may be re-used
by many PWs.
Unless otherwise specified, all objects in this table
MUST NOT be changed after row activation (see [PWMIB])
if the row index is in use by an entry in pwTDMTable.
Rows must persist after reboot."
So that last sentence needs to be removed. Becuase it is in
conflict with the fact that you do have a pwTDMCfgStorageType
in the table. That is the object that controls the persistency
behaviour for each row. So better not to make a contradictory
statement as in the above DESCRIPTION clause.
Bert Wijnen
2 May 2008 13:12
Re: draft-ietf-pwe3-tdm-mib-10.txt---to fix in rfc editor
Orly Nicklass <orly-n <at> actcom.co.il>
2008-05-02 11:12:07 GMT
2008-05-02 11:12:07 GMT
Lets have a note here to the RFC editor, as the real semantics is well defined and this is more of an oversight in the process. > -----Original Message----- > From: pwe3-bounces <at> ietf.org [mailto:pwe3-bounces <at> ietf.org] On Behalf Of > Bert Wijnen - IETF > Sent: Thursday, May 01, 2008 15:54 > To: Orly Nicklass > Cc: 'ext Thomas Nadeau'; 'Romascanu,Dan (Dan)'; pwe3 <at> ietf.org; MIB > Doctors; 'Danny McPherson' > Subject: Re: [PWE3] draft-ietf-pwe3-tdm-mib-(Continue reading)10.txt---to fix in rfc editor > > As MIB-doctor I am now happy with this revision except for one > little nit (well... it is a bit more, but the change > required is very small): > > pwTDMCfgEntry OBJECT-TYPE > SYNTAX PwTDMCfgEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "These parameters define the characteristics of a > TDM PW. They are grouped here to ease NMS burden. > Once an entry is created here it may be re-used > by many PWs. > Unless otherwise specified, all objects in this table > MUST NOT be changed after row activation (see [PWMIB]) > if the row index is in use by an entry in pwTDMTable. > Rows must persist after reboot." >
2 May 2008 13:15
Re: draft-ietf-pwe3-tdm-mib-10.txt---to fix in rfc editor
Bert Wijnen - IETF <bertietf <at> bwijnen.net>
2008-05-02 11:15:26 GMT
2008-05-02 11:15:26 GMT
Fine by me Bert Wijnen > -----Oorspronkelijk bericht----- > Van: Orly Nicklass [mailto:orly-n <at> actcom.co.il] > Verzonden: vrijdag 2 mei 2008 13:12 > Aan: 'Bert Wijnen - IETF' > CC: 'ext Thomas Nadeau'; 'Romascanu,Dan (Dan)'; pwe3 <at> ietf.org; 'MIB > Doctors'; 'Danny McPherson' > Onderwerp: RE: [PWE3] draft-ietf-pwe3-tdm-mib-(Continue reading)10.txt---to fix in rfc > editor > > > Lets have a note here to the RFC editor, as the real semantics is well > defined and this is more of an oversight in the process. > > > -----Original Message----- > > From: pwe3-bounces <at> ietf.org [mailto:pwe3-bounces <at> ietf.org] On Behalf Of > > Bert Wijnen - IETF > > Sent: Thursday, May 01, 2008 15:54 > > To: Orly Nicklass > > Cc: 'ext Thomas Nadeau'; 'Romascanu,Dan (Dan)'; pwe3 <at> ietf.org; MIB > > Doctors; 'Danny McPherson' > > Subject: Re: [PWE3] draft-ietf-pwe3-tdm-mib-10.txt---to fix in > rfc editor > > > > As MIB-doctor I am now happy with this revision except for one > > little nit (well... it is a bit more, but the change > > required is very small):
2 May 2008 15:50
PWE3 Charter Update - **DRAFT Charter v0.1**
Danny McPherson <danny <at> tcb.net>
2008-05-02 13:50:33 GMT
2008-05-02 13:50:33 GMT
Folks, Time for that periodic charter refresh and update. If you've got comments, send'm along, as we'd like to get this off to the IAB for approval. Please consider this a 2 week call for input, ending on 5/16. Thanks much! -danny ---- v0.1 Pseudowire Emulation Edge to Edge (pwe3) Additional information is available at http://tools.ietf.org/wg/pwe3 Chair(s): Danny McPherson <danny <at> arbor.net> Stewart Bryant <stbryant <at> cisco.com> Internet Area Director(s): Jari Arkko <jari.arkko <at> piuha.net> Mark Townsley <townsley <at> cisco.com> Internet Area Advisor: Mark Townsley <townsley <at> cisco.com> Technical Advisor(s): Allison Mankin <mankin <at> psg.com>(Continue reading)
2 May 2008 20:45
Re: PWE3 Charter Update - **DRAFT Charter v0.1**
Danny McPherson <danny <at> tcb.net>
2008-05-02 18:45:43 GMT
2008-05-02 18:45:43 GMT
On May 2, 2008, at 7:50 AM, Danny McPherson wrote: > Folks, > Time for that periodic charter refresh and update. If you've > got comments, send'm along, as we'd like to get this off to the > IAB for approval. s/IAB/IESG/, of course(Continue reading)-danny > > > Please consider this a 2 week call for input, ending on 5/16. > > Thanks much! > > -danny > > ---- > v0.1 > Pseudowire Emulation Edge to Edge (pwe3) > Additional information is available at http://tools.ietf.org/wg/pwe3 > > Chair(s): > > Danny McPherson <danny <at> arbor.net> > Stewart Bryant <stbryant <at> cisco.com> >
5 May 2008 13:34
Re: PWE3 Charter Update - **DRAFT Charter v0.1**
Alexander Vainshtein <Alexander.Vainshtein <at> ecitele.com>
2008-05-05 11:34:11 GMT
2008-05-05 11:34:11 GMT
Danny and all,
I have a couple of comments regarding the proposed draft charter.
1. The draft says:
<quote>
The IETF PWE3 WG is the design authority for pseudo-wire
over IP/MPLS PSN technology. Extensions to this work by other
SDOs needs to invoke the MPLS Change Process, as provided in
RFC 4929.
<end quote>
I've looked up RFC 4929 and, to the best of my understanding, it treats
the PWE3 WG as one of the "other" IETF WGs when it comes to the
MPLS/GMPLS change process, i.e. it is NOT a valid address for the external
SDO to bring its proposals for the MPLS/GMPLS change, this function is
reserved for the MPLS and CCAMP WGs.
Hence the following re-wording looks to me more accurate (even if
it sounds too much legalese
<proposed text>
The IETF PWE3 WG is the design authority for pseudo-wire
over IP/MPLS PSN technology. An entity or individual that
wishes to propose extensions or changes to this technology
must bring the corresponding proposals to the PWE3 WG that
would treat them via a process similar to one described in
RFC 4929 for the MPLS/GMPLS change.
<end of proposed text>
(Continue reading)
5 May 2008 16:47
Re: PWE3 Charter Update - **DRAFT Charter v0.1**
Danny McPherson <danny <at> tcb.net>
2008-05-05 14:47:29 GMT
2008-05-05 14:47:29 GMT
On May 5, 2008, at 5:34 AM, Alexander Vainshtein wrote: > > <proposed text> > The IETF PWE3 WG is the design authority for pseudo-wire > over IP/MPLS PSN technology. An entity or individual that > wishes to propose extensions or changes to this technology > must bring the corresponding proposals to the PWE3 WG that > would treat them via a process similar to one described in > RFC 4929 for the MPLS/GMPLS change. > <end of proposed text> I think your recommendation here is reasonable, let's see what other folks think about it. > 2. PWE3 security: I have been under the impression that the MPLS WG > is working on the "common" MPLS security document that would cover, > among others, the PWE3-specific security issues. The draft, > however, > proposes to deal with the PWE3 security issues separately. Is such > separation justified, and, if so, how do we see the partitioning > between > the two efforts? I think that such partitioning should be > mentioned in > the draft, the text used for partitioning between PWE3 and L2VPN > could be used as the template. Just as the WG delineation and charter scopes the area of work, PWE3 *specific* work will be done in PWE3, while it's only natural that general MPLS-related work will be done in(Continue reading)
5 May 2008 19:04
Charter Modification
Danny McPherson <danny <at> tcb.net>
2008-05-05 17:04:42 GMT
2008-05-05 17:04:42 GMT
Team, I've added this goal to the charter as well, it's being driven by the MPLS TP work. If you've got comments please let it be known: "In cooperation with the MPLS and CCAMP working groups, define extensions necessary to fulfill an MPLS transport profile." Full charter below (includes Sasha's comments). -danny --- Pseudowire Emulation Edge to Edge (pwe3) Additional information is available at http://tools.ietf.org/wg/pwe3 Chair(s): Danny McPherson <danny <at> arbor.net> Stewart Bryant <stbryant <at> cisco.com> Internet Area Director(s): Jari Arkko <jari.arkko <at> piuha.net> Mark Townsley <townsley <at> cisco.com> Internet Area Advisor: Mark Townsley <townsley <at> cisco.com>(Continue reading)
9 May 2008 12:56
proposed charter update for the MPLS TP work
Loa Andersson <loa <at> pi.nu>
2008-05-09 10:56:45 GMT
2008-05-09 10:56:45 GMT
MPLS, CCAMP and PWE3 working groups,
The Joint Working Team of the IETF and ITU-T has resulted in
the agreement to create a Transport Profile for MPLS (MPLS TP).
This effort requires the MPLS, PWE3 and CCAMP Working Groups
are chartered to do the required work.
The MPLS, PWE3 and CCAMP chairs proposes that we add the
following paragraph to the three working group charters:
"- Include extensions to the [MPLS, PWE3, CCAMP] protocols and RFCs
necessary to fulfill an MPLS Transport Profile (MPLS TP), the work
on the MPLS TP needs to be coordinated between the three working
groups (MPLS, PWE3 and CCAMP) that are chartered to do MPLS TP
work."
Please send your comments to the working group(s) mailing list(s)
eob Friday May 16.
Adrian, Deborah, Danny, Stewart, George and Loa
--
--
Loa Andersson
Principal Networking Architect
Acreo AB phone: +46 8 632 77 14
Isafjordsgatan 22 mobile: +46 739 81 21 64
Kista, Sweden email: loa.andersson <at> acreo.se
loa <at> pi.nu
(Continue reading)
RSS Feed