Re: [mpls] working group last call draft-ietf-mpls-tp-psc-itu-01

"Ryoo, Jeong-dong" <ryoo@etri.re.kr> Wed, 29 January 2014 07:18 UTC

Return-Path: <ryoo@etri.re.kr>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 126EE1A0437 for <mpls@ietfa.amsl.com>; Tue, 28 Jan 2014 23:18:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.434
X-Spam-Level:
X-Spam-Status: No, score=-102.434 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_NONELEMENT_30_40=0.001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Bqk-SjZjpuc for <mpls@ietfa.amsl.com>; Tue, 28 Jan 2014 23:18:21 -0800 (PST)
Received: from smtpeg.etri.re.kr (smtpeg1.etri.re.kr [129.254.27.141]) by ietfa.amsl.com (Postfix) with ESMTP id 2E13F1A0420 for <mpls@ietf.org>; Tue, 28 Jan 2014 23:18:21 -0800 (PST)
Received: from SMTP4.etri.info (129.254.28.74) by SMTPEG1.etri.info (129.254.27.141) with Microsoft SMTP Server (TLS) id 14.1.355.2; Wed, 29 Jan 2014 16:18:16 +0900
Received: from SMTP2.etri.info ([169.254.2.161]) by SMTP4.etri.info ([10.2.6.33]) with mapi id 14.01.0355.002; Wed, 29 Jan 2014 16:18:15 +0900
From: "Ryoo, Jeong-dong" <ryoo@etri.re.kr>
To: Loa Andersson <loa@pi.nu>, "mpls@ietf.org" <mpls@ietf.org>
Thread-Topic: working group last call draft-ietf-mpls-tp-psc-itu-01
Thread-Index: AQHPHDD6PxX4EfDenE+JJCp9uCTk/JqbAWPi//+sAICAAJ6sqw==
Date: Wed, 29 Jan 2014 07:18:15 +0000
Message-ID: <5B4A6CBE3924BB41A3BEE462A8E0B75A286B4092@SMTP2.etri.info>
References: <52DC89C3.3030003@pi.nu>, <52E7B75F.6010805@pi.nu> <5B4A6CBE3924BB41A3BEE462A8E0B75A286B401B@SMTP2.etri.info>, <52E8A495.1050501@pi.nu>
In-Reply-To: <52E8A495.1050501@pi.nu>
Accept-Language: ko-KR, en-US
Content-Language: ko-KR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-new-displayname: UnlvbywgSmVvbmctZG9uZw==
x-originating-ip: [129.254.28.46]
Content-Type: multipart/alternative; boundary="_000_5B4A6CBE3924BB41A3BEE462A8E0B75A286B4092SMTP2etriinfo_"
MIME-Version: 1.0
Cc: "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>, "draft-ietf-mpls-tp-psc-itu@tools.ietf.org" <draft-ietf-mpls-tp-psc-itu@tools.ietf.org>
Subject: Re: [mpls] working group last call draft-ietf-mpls-tp-psc-itu-01
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 07:18:26 -0000

Loa, thanks.

Jeong-dong


________________________________
From : "Loa Andersson" <loa@pi.nu>
Sent : 2014-01-29 15:50:07 ( +09:00 )
To : Ryoo, Jeong-dong <ryoo@etri.re.kr>, mpls@ietf.org <mpls@ietf.org>
Cc : mpls-chairs@tools.ietf.org <mpls-chairs@tools.ietf.org>, draft-ietf-mpls-tp-psc-itu@tools.ietf.org <draft-ietf-mpls-tp-psc-itu@tools.ietf.org>, VIGOUREUX, MARTIN (MARTIN) <martin.vigoureux@alcatel-lucent.com>
Subject : Re: working group last call draft-ietf-mpls-tp-psc-itu-01

Jeong-dong,

I think we are in agreement. For "WTR Expires" I think you understand
my concern, do what you think is useful and necessary. Maybe there is
Adrian's comment on the page 13 last line could be used to clarify
page 20 3rd line also.

/Loa


On 2014-01-29 12:24, Ryoo, Jeong-dong wrote:
> Loa, thanks for the comments.
> Yes, we need to clarify state/message(/timer) for WTR and others.
> One minor concern is that "WTR Expires" is used as the name of a local
> request in RFC 6378.
> I am not sure if it would be ok to change it to "WTR Timer Expires" in
> this document.
> More specifically, the proposal of the following two items needs the
> change of "WTR Expires" to "WTR timer expires" in the priority list
> in page 19:
> - page 13 last line - s/WTR expires/WTR timer expires (This item would
> disapprear once we take Adrian's proposal to change whole sentence.)
> - page 20 3rd line from the - s/WTR expires/WTR timer expires
>
> Best regards,
> Jeong-dong
>
> ------------------------------------------------------------------------
> *From : *"Loa Andersson"
> *Sent : *2014-01-28 22:58:10 ( +09:00 )
> *To : *mpls@ietf.org
> *Cc : *mpls-chairs@tools.ietf.org ,
> , draft-ietf-mpls-tp-psc-itu@tools.ietf.org
> , VIGOUREUX, MARTIN (MARTIN)
>
> *Subject : *Re: working group last call draft-ietf-mpls-tp-psc-itu-01
>
> Folks,
>
> I've reviewed this document (actually fourth or fifth time) and I have
> very few comments, I think Adrian covered all mine in his review.
>
> I had something that I thought were spelling errors, but turns out to
> be differences between UK and US English. I'm pretty sure that the
> RFC Editor will set that right (if it isn't already).
>
> There is one thing that sometimes makes hard to parse the document,
> the abbreviation WTR stands for "Wait to restore", the thing is that
> WTR can be a state, a message or a timer (given that I understand it
> correctly). When I discussed this earlier the answer has been "Well
> it is confusing, but that is how it is done!"
>
> I think at places where it necessary e.g. WTR are qualified with
> state, message or timer. I found one place where want to add a
> clarifying "state", "message" or "timer".
>
> page 13 last line - s/WTR expires/WTR timer expires
>
> page 20 3rd line from the - s/WTR expires/WTR timer expires
>
> page 25 Note 4 s/WTR/WTR state
>
> page 25 Note 6 s/WTR/WTR state
>
> page 27 Note 11 s/WTR/WTR state
>
> DNR may be a state or a message, for clarification
>
> page 27 note 11 s/DNR./DNR state.
>
> The same exercise maybe be done for EXER [command, message] (actually
> I think that for EXER this is done correctly), but it might valuable
> to check for all abbreviations that has double meaning.
>
> I don't think it is necessary or even motivated to do more about
> this, but it might be a good if readers of the document were aware of
> this.
>
> I think the document - modulo addressing comments in wglc - is ready
> to go.
>
> /Loa
>
> On 2014-01-20 10:28, Loa Andersson wrote:
> > Working Group,
> >
> > This is to start a two week working group last call on
> > draft-ietf-mpls-tp-psc-itu.
> >
> > Please find the document at:
> > https://datatracker.ietf.org/doc/draft-ietf-mpls-tp-psc-itu/
> >
> > The document editors has also supplied a "diff-list" between
> > version -00 and -01 at:
> > http://www.ietf.org/mail-archive/web/mpls/current/msg11338.html
> >
> > ITU-T SG15 has advised us that this document is a necessary reference
> > for documents that is planned to go into the ITU-T approval process
> > from the SG15 meeting end of March / beginning of April. Editors,
> > authors and chairs has put in quite an effort to make this document
> > ready. The schedule is very tight.
> >
> > We are now doing several review steps in parallel
> >
> > - the normal working group last call, please send your comments to the
> > mpls working group mailing list (mpls@ietf.org)
> > - the working group chairs reviewed this document as part of the
> > mpls-rt review, normally we do a wg chair review before starting the
> > wglc, this review will now take place in parallel
> > - after the wglc and publication request there is an AD evaluation,
> > this will now also take place in parallel with the wglc
> >
> > The editors and authors are advised to try to resolve as many of the
> > comments as possible (on the mailing list) as they come in, but not to
> > post the new version of the draft until the wglc is closed and the
> > comments are resolved.
> >
> > This working group last call ends February 3rd.
> >
> > /Loa
> > for the MPLS WG co-chairs
>
> --
>
>
> Loa Andersson email: loa@mail01.huawei.com
> Senior MPLS Expert loa@pi.nu
> Huawei Technologies (consultant) phone: +46 739 81 21 64

--


Loa Andersson email: loa@mail01.huawei.com
Senior MPLS Expert loa@pi.nu
Huawei Technologies (consultant) phone: +46 739 81 21 64