
From sblake@extremenetworks.com  Thu Nov  4 10:56:42 2010
Return-Path: <sblake@extremenetworks.com>
X-Original-To: pcn@core3.amsl.com
Delivered-To: pcn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 05B1228C0FA for <pcn@core3.amsl.com>; Thu,  4 Nov 2010 10:56:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fS6JkZwhNDaa for <pcn@core3.amsl.com>; Thu,  4 Nov 2010 10:56:41 -0700 (PDT)
Received: from ussc-casht-p1.extremenetworks.com (ussc-casht-p1.extremenetworks.com [207.179.9.62]) by core3.amsl.com (Postfix) with ESMTP id 2F37528C0DC for <pcn@ietf.org>; Thu,  4 Nov 2010 10:56:41 -0700 (PDT)
Received: from [10.5.2.40] (10.5.2.40) by ussc-casht-p1.corp.extremenetworks.com (10.0.4.73) with Microsoft SMTP Server id 8.1.358.0; Thu, 4 Nov 2010 10:56:51 -0700
From: Steven Blake <sblake@extremenetworks.com>
To: Steven Blake <slblake@petri-meat.com>
In-Reply-To: <1287671332.2758.9.camel@tachyon>
References: <Dgp2hrvy.1287557988.4120160.karagian@ewi.utwente.nl> <1287671332.2758.9.camel@tachyon>
Content-Type: text/plain; charset="UTF-8"
Organization: Extreme Networks
Date: Thu, 4 Nov 2010 13:56:49 -0400
Message-ID: <1288893409.2892.4.camel@ecliptic.extremenetworks.com>
MIME-Version: 1.0
X-Mailer: Evolution 2.30.3 (2.30.3-1.fc13) 
Content-Transfer-Encoding: 7bit
Cc: "pcn@ietf.org" <pcn@ietf.org>
Subject: Re: [PCN] WGLC for draft-ietf-pcn-signaling-requirements-01.txt?
X-BeenThere: pcn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PCN WG list <pcn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcn>
List-Post: <mailto:pcn@ietf.org>
List-Help: <mailto:pcn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Nov 2010 17:56:42 -0000

On Thu, 2010-10-21 at 07:28 -0700, Steven Blake wrote:

> On Wed, 2010-10-20 at 06:59 +0000, Georgios Karagiannis wrote:
> 
> > Hi Steve, Hi Scott, Hi all
> > 
> > Based on the comments received up to now and based on the last versions
> > of:
> > draft-ietf-pcn-cl-edge-behaviour-07 and
> > draft-ietf-pcn-sm-edge-behaviour-04 we updated the signaling
> > requirements draft.
> > 
> > In my opinion we can start the WG Last Call for this draft!
> 
> Ok, thanks Georgios.
> 
> The WGLC for draft-ietf-pcn-signaling-requirements-01 starts today,
> concluding Thursday, Nov. 4.  Please send comments to the pcn list.

I do not see any evidence of WG consensus for sending this document to
the IESG yet.

Georgios, please work with Philip to address his concerns.  For the rest
of the WG, please review the draft and send your comments to the list.
We can last call a revised draft later on.


Regards,

/////////////////////////////////////////////
Steven Blake       sblake@extremenetworks.com
Extreme Networks              +1 919-884-3211


From karagian@cs.utwente.nl  Fri Nov  5 02:29:03 2010
Return-Path: <karagian@cs.utwente.nl>
X-Original-To: pcn@core3.amsl.com
Delivered-To: pcn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CC6733A67B4 for <pcn@core3.amsl.com>; Fri,  5 Nov 2010 02:29:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level: 
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j8ACJZ58aql3 for <pcn@core3.amsl.com>; Fri,  5 Nov 2010 02:29:03 -0700 (PDT)
Received: from denhaag.ewi.utwente.nl (denhaag.ewi.utwente.nl [130.89.10.11]) by core3.amsl.com (Postfix) with ESMTP id CB0863A67C3 for <pcn@ietf.org>; Fri,  5 Nov 2010 02:29:02 -0700 (PDT)
Received: from ewi977 (ewi977.ewi.utwente.nl [130.89.12.129]) by denhaag.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id oA59Sum5002621;  Fri, 5 Nov 2010 10:29:00 +0100 (MET)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "'Steven Blake'" <sblake@extremenetworks.com>
References: <Dgp2hrvy.1287557988.4120160.karagian@ewi.utwente.nl> <1287671332.2758.9.camel@tachyon> <1288893409.2892.4.camel@ecliptic.extremenetworks.com>
Date: Fri, 5 Nov 2010 10:29:07 +0100
Message-ID: <86CE7D57219B4D79B3464B95770C88A5@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
In-Reply-To: <1288893409.2892.4.camel@ecliptic.extremenetworks.com>
Thread-Index: Act8Sy2fASCQAI88StmgfoLHdIUBhQAgJRGg
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.11
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3 (denhaag.ewi.utwente.nl [130.89.10.11]); Fri, 05 Nov 2010 10:29:10 +0100 (MET)
Cc: pcn@ietf.org
Subject: Re: [PCN] WGLC for draft-ietf-pcn-signaling-requirements-01.txt?
X-BeenThere: pcn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PCN WG list <pcn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcn>
List-Post: <mailto:pcn@ietf.org>
List-Help: <mailto:pcn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Nov 2010 09:29:03 -0000

Hi Steve

Thanks for the information!
I will work with Phil to address his concerns! 

Best regards,
Georgios


> -----Original Message-----
> From: Steven Blake [mailto:sblake@extremenetworks.com] 
> Sent: donderdag 4 november 2010 18:57
> To: Steven Blake
> Cc: Georgios Karagiannis; pcn@ietf.org
> Subject: Re: [PCN] WGLC for 
> draft-ietf-pcn-signaling-requirements-01.txt?
> 
> On Thu, 2010-10-21 at 07:28 -0700, Steven Blake wrote:
> 
> > On Wed, 2010-10-20 at 06:59 +0000, Georgios Karagiannis wrote:
> > 
> > > Hi Steve, Hi Scott, Hi all
> > > 
> > > Based on the comments received up to now and based on the last 
> > > versions
> > > of:
> > > draft-ietf-pcn-cl-edge-behaviour-07 and
> > > draft-ietf-pcn-sm-edge-behaviour-04 we updated the signaling 
> > > requirements draft.
> > > 
> > > In my opinion we can start the WG Last Call for this draft!
> > 
> > Ok, thanks Georgios.
> > 
> > The WGLC for draft-ietf-pcn-signaling-requirements-01 starts today, 
> > concluding Thursday, Nov. 4.  Please send comments to the pcn list.
> 
> I do not see any evidence of WG consensus for sending this 
> document to the IESG yet.
> 
> Georgios, please work with Philip to address his concerns.  
> For the rest of the WG, please review the draft and send your 
> comments to the list.
> We can last call a revised draft later on.
> 
> 
> Regards,
> 
> /////////////////////////////////////////////
> Steven Blake       sblake@extremenetworks.com
> Extreme Networks              +1 919-884-3211
> 



From rbriscoe@jungle.bt.co.uk  Sun Nov  7 18:28:27 2010
Return-Path: <rbriscoe@jungle.bt.co.uk>
X-Original-To: pcn@core3.amsl.com
Delivered-To: pcn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7A47F3A68F0 for <pcn@core3.amsl.com>; Sun,  7 Nov 2010 18:28:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.117
X-Spam-Level: 
X-Spam-Status: No, score=-2.117 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3mkDbum9cliE for <pcn@core3.amsl.com>; Sun,  7 Nov 2010 18:28:20 -0800 (PST)
Received: from smtp1.smtp.bt.com (smtp1.smtp.bt.com [217.32.164.137]) by core3.amsl.com (Postfix) with ESMTP id 84CDE3A694C for <pcn@ietf.org>; Sun,  7 Nov 2010 18:28:19 -0800 (PST)
Received: from i2kc06-ukbr.domain1.systemhost.net ([193.113.197.70]) by smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 8 Nov 2010 02:28:38 +0000
Received: from cbibipnt05.iuser.iroot.adidom.com ([147.149.196.177]) by i2kc06-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(6.0.3790.4675); Mon, 8 Nov 2010 02:28:37 +0000
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by cbibipnt05.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a P0803.399); id 128918331710; Mon, 8 Nov 2010 02:28:37 +0000
Received: from MUT.jungle.bt.co.uk ([10.142.80.34]) by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id oA82SXmv012078 for <pcn@ietf.org>; Mon, 8 Nov 2010 02:28:35 GMT
Message-Id: <201011080228.oA82SXmv012078@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 08 Nov 2010 10:28:31 +0800
To: "PCN IETF list" <pcn@ietf.org>
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 08 Nov 2010 02:28:37.0495 (UTC) FILETIME=[A6240070:01CB7EEC]
Subject: [PCN] Fwd: [ADs] AUTH48 [MF]: RFC 6040 <draft-ietf-tsvwg-ecn-tunnel-10.txt> NOW AVAILABLE
X-BeenThere: pcn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PCN WG list <pcn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcn>
List-Post: <mailto:pcn@ietf.org>
List-Help: <mailto:pcn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2010 02:28:27 -0000

PCN folks,

Just to let you know,=20
<draft-ietf-tsvwg-ecn-tunnel-10.txt> has been=20
through the RFC editor and is awaiting Dave=20
Harrington's sign-off. If approved, it would become RFC 6040.

I believe this tunnelling issue held back PCN=20
considerably. Even with RFC6040, it would require=20
vendors to implement it in order to simplify our PCN encoding choice.


Bob


>Date: Thu, 28 Oct 2010 00:08:46 +0100
>To: Megan Ferguson <mferguson@amsl.com>
>From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
>Subject: Re: [ADs] AUTH48 [MF]: RFC 6040=20
><draft-ietf-tsvwg-ecn-tunnel-10.txt> NOW AVAILABLE
>Cc: <rfc-editor@rfc-editor.org>,=20
><tsvwg-ads@tools.ietf.org>, <tsvwg-chairs@tools.ietf.org>
>Bcc: =83\In 2009
>
>Megan,
>
>Thanks.
>
>Altho you've already accepted my approval, this=20
>is just to confirm I've checked it again, and I approve again.
>
>
>Bob
>
>At 16:04 27/10/2010, Megan Ferguson wrote:
>>Hi Bob and *ADs,
>>
>>Thank you for your reply.  We have updated our=20
>>files as requested below.  These updates are viewable at:
>>
>>http://www.rfc-editor.org/authors/rfc6040.xml
>>http://www.rfc-editor.org/authors/rfc6040.txt
>>http://www.rfc-editor.org/authors/rfc6040-lastdiff.html
>>
>>For your convenience, we have posted a diff=20
>>file highlighting all changes to date at:
>>
>>http://www.rfc-editor.org/authors/rfc6040-diff.html
>>
>>Please review the document carefully to ensure=20
>>satisfaction as we do not make changes once the=20
>>document has been published as an RFC.  Note=20
>>that it may be necessary for you to refresh=20
>>your browser to view the most recent version of the document.
>>
>>Upon careful review, please contact us with any=20
>>further updates.  As you indicated your=20
>>approval of the text in this form in your=20
>>previous message, we have updated your AUTH48 status to "Approved" at:
>>
>>http://www.rfc-editor.org/auth48/rfc6040
>>
>>*ADs,
>>
>>Please review and approve the changes viewable at:
>>
>>http://www.rfc-editor.org/authors/rfc6040-lastdiff.html
>>
>>Thank you.
>>
>>RFC Editor/mf
>>
>>On Oct 26, 2010, at 3:03 PM, Bob Briscoe wrote:
>>
>> > RFC Editor,
>> >
>> > Thank you for this.
>> >
>> > I'm more than happy with everything you have=20
>> changed, excepting for one or two that I have=20
>> 'improved' in the attached XML. All changes=20
>> should be self-explanatory, except in a few=20
>> cases where the points below may help justify my changes:
>> >
>> > 1) Abstract & Introduction:
>> > In both cases I prefer
>> >  "previously unused combinations of inner and outer headers" to
>> >  "previously unused combinations of the inner and outer header".
>> > Otherwise the addition of the definite=20
>> article changes the sense from "combinations=20
>> of various settings of each header" to=20
>> "combinations of one particular inner header and one particular outer=
 header."
>> >
>> > 2) I noticed you had changed "cater for an=20
>> historic security concern" to "cater to an historic security concern".
>> > This grates to a British ear. For the sense=20
>> of "pander to", Collins Dictionary says the=20
>> latter is American English, while the former=20
>> is British. Given you have allowed the=20
>> document spelling to remain in British=20
>> English, it would be consistent to use British=20
>> wording too. See:=
 <http://bbs.chinadaily.com.cn/viewthread.php?tid=3D575192>
>> >
>> > 3) On the subject of British vs American, I=20
>> notice standardization with a 'z' in the=20
>> boilerplate is inconsistent with the British=20
>> English 'standardisation' spelling in the body of the document.
>> >
>> > A also noticed a couple of my own errors=20
>> while reading through. I assume Gorry, as=20
>> shepherd, can verify that these changes are acceptable:
>> >
>> > 4) In early drafts we sometimes used the=20
>> word 'inner' ambiguously for  'incoming' (at=20
>> ingress) and 'outgoing' (at egress). I=20
>> corrected a number of instances where this=20
>> ambiguity remained - all but one were in the=20
>> appendices that fewer people have reviewed.
>> >
>> > 5) To avoid confusion with the defined terms=20
>> outgoing (at egress) and incoming (at ingress)=20
>> I changed 'outgoing' (at ingress) and=20
>> 'incoming' (at egress) to respectively 'departing' and 'arriving'.
>> >
>> > 6) I corrected 'PCN excess-rate marking' to=20
>> 'PCN excess-traffic-marking', which was the term finally agreed on in=
 RFC5670.
>> >
>> >
>> > Thank you.
>> >
>> >
>> > Bob
>> >
>> > At 20:43 25/10/2010, rfc-editor@rfc-editor.org wrote:
>> >
>> >> Bob,
>> >>
>> >> While reviewing this document during=20
>> AUTH48, please resolve (as necessary) the=20
>> following questions, which are also in the XML file.
>> >>
>> >> 1) <!--[rfced] Please note that after you have approved the document,
>> >> post-xml2rfc changes will be made to update the header and
>> >> boilerplate as described in RFC 5741.
>> >> -->
>> >>
>> >>
>> >> 2) <!--[rfced] Does "Section 5" apply to both RFC 3168 and RFC 4774?
>> >>
>> >> Original:
>> >>   If these defaults do not meet a particular requirement, an alternate
>> >>   ECN tunnelling scheme can be introduced as part of the definition of
>> >>   an alternate congestion marking scheme used by a specific Diffserv
>> >>   PHB (see section 5 of [RFC3168] and [RFC4774]).
>> >>
>> >> If not, perhaps:
>> >>   If these defaults do not meet a particular requirement, an alternate
>> >>   ECN tunnelling scheme can be introduced as part of the definition of
>> >>   an alternate congestion marking scheme used by a specific Diffserv
>> >>   PHB (see RFC 4774 and Section 5 of RFC 3168).
>> >> -->
>> >>
>> >>
>> >> 3) <!-- [rfced] RFC 4306 was obsoleted by RFC 5996.
>> >> How may this text be updated to include mention of RFC 5996?
>> >>
>> >> Current:
>> >>      For instance, IPsec tunnel endpoints compatible with RFC 4301
>> >>      invariably use Internet Key Exchange Protocol version 2 (IKEv2)
>> >>      [RFC4306] for key exchange, which was introduced alongside RFC
>> >>      4301.
>> >>
>> >> Perhaps:
>> >>      For instance, IPsec tunnel endpoints compatible with RFC 4301
>> >>      invariably use Internet Key Exchange Protocol version 2 (IKEv2)
>> >>      [RFC4306] for key exchange, which was introduced alongside RFC
>> >>      4301.  (Note: [RFC4306] has been obsoleted by [RFC5996].)
>> >> -->
>> >>
>> >>
>> >> 4) <!-- [rfced] Please clarify this=20
>> sentence, especially "8b per datagram covert channel".
>> >>
>> >> Original:
>> >>   Of course, an
>> >>   administrator considering copying of the DS field has to take into
>> >>   account that it could be concatenated with the ECN field giving an=
 8b
>> >>   per datagram covert channel.
>> >>
>> >> Perhaps:
>> >>   Of course, an
>> >>   administrator that considers copying the DS field has to take into
>> >>   account that it could be concatenated with the ECN field, giving an
>> >>   eight-bit covert channel for each datagram.
>> >> -->
>> >>
>> >>
>> >> Thank you.
>> >>
>> >> RFC Editor/ah
>> >>
>> >>
>> >> On Oct 25, 2010, at 3:42 PM, rfc-editor@rfc-editor.org wrote:
>> >>
>> >>
>> >> *****IMPORTANT*****
>> >>
>> >> Updated 2010/10/25
>> >>
>> >> RFC Author(s):
>> >> --------------
>> >>
>> >> Instructions for Completing AUTH48 in XML
>> >>
>> >> This is your last chance to make changes to your RFC-to-be:
>> >> draft-ietf-tsvwg-ecn-tunnel-10.txt.
>> >> Once the document is published as an RFC, we will not make changes.
>> >> Please follow the instructions below to complete the AUTH48 process.
>> >>
>> >> 1) Review the edited document completely.  The files are available=
 here:
>> >>
>> >>  http://www.rfc-editor.org/authors/rfc6040.txt
>> >>  http://www.rfc-editor.org/authors/rfc6040-diff.html
>> >>
>> >>  We recommend reviewing the entire document, not just the diff file.
>> >>  The placement of page breaks will be handled during the final stages=
 of
>> >>  publication (typically post-xml2rfc processing).
>> >>
>> >> 2) Review and resolve (as necessary) any questions raised by the RFC
>> >>  Editor.  The questions (if any) have been included in the XML file as
>> >>  comments marked <!-- [rfced] ... --> and=20
>> will be sent in a subsequent email.
>> >>
>> >>  Retrieve the edited XML file here:
>> >>
>> >>     http://www.rfc-editor.org/authors/rfc6040.xml
>> >>
>> >>  (Note that you may need to view the page source to save the file.)
>> >>
>> >> 3) Send us your changes or respond with your approval for publication.
>> >>  Please use 'Reply All' so that rfc-editor@rfc-editor.org and the=
 parties
>> >>  CC'ed on this message receive your=20
>> response. Note that your document will
>> >>  not move forward until we have received approvals from each of the
>> >>  authors listed on the front page.
>> >>
>> >>  If sending changes, please do one of the following:
>> >>
>> >>  a. Update the provided XML file, then email us the revised XML file.
>> >>     You may use any filename for the revised file; we will rename it
>> >>     before posting it.
>> >>
>> >>  --OR--
>> >>
>> >>  b. Provide us with an explicit list of changes in the this format.
>> >>
>> >>     Section # (or indicate Global)
>> >>
>> >>     OLD:
>> >>     old text
>> >>
>> >>     NEW:
>> >>     new text
>> >>
>> >>  Be sure to pay particular attention to these areas of the document:
>> >>  - IANA Considerations updates (if applicable)
>> >>  - Contact information
>> >>  - Copyright notice and legends (see item 5 for more details)
>> >>
>> >> 4) Review changes submitted by your coauthors.  We assume that you
>> >>  will speak up if you do not agree with the proposed changes. That is,
>> >>  your silence is your assent to changes submitted by your coauthors.
>> >>  Note that any changes that are beyond editorial will be sent to the
>> >>  relevant body for approval.
>> >>
>> >>  Additional diff files will be posted as authors send updates for the
>> >>  document.  We recommend viewing these  later diff files to identify=
 and
>> >>  review changes submitted by your coauthors.
>> >>
>> >> 5) Review the copyright notice and legends as defined in RFC 5378 and
>> >>  the Trust Legal Provisions (TLP --=20
>> http://trustee.ietf.org/license-info/).
>> >>
>> >>  If your document was approved for publication with a pre-RFC-5378
>> >>  copyright notice, we have applied the text from section 6.c.iii of=
 the
>> >>  TLP.  Please consider whether this text is required (note that the
>> >>  6.c.iii text is not applicable to Independent Stream RFCs).  See item
>> >>  4.5 of the "Copyright FAQ" at http://trustee.ietf.org/faqs.html for
>> >>  guidance on whether this text applies to your document.
>> >>
>> >> 6) Please reply, as the document will not be published until we=
 receive
>> >>  approvals from each author.  The details of the AUTH48 status of your
>> >>  document are here:
>> >>
>> >>  http://www.rfc-editor.org/auth48/rfc6040
>> >>
>> >> Thank you for your cooperation,
>> >>
>> >> RFC Editor
>> >>
>> >> --------------------------------------
>> >> RFC6040 (draft-ietf-tsvwg-ecn-tunnel-10)
>> >> --------------------------------------
>> >> Title            : Tunnelling of Explicit Congestion Notification
>> >> Author(s)        : B. Briscoe
>> >> WG Chair(s)      : James Polk, Gorry Fairhurst
>> >> Area Director(s) : David Harrington, Lars Eggert
>> >
>> > ________________________________________________________________
>> > Bob=20
>> Briscoe,                                BT Innovate & Design=
 <rfc6040_b.xml>
>
>________________________________________________________________
>Bob Briscoe,                                BT Innovate & Design

________________________________________________________________
Bob Briscoe,                                BT Innovate & Design=20


From rbriscoe@jungle.bt.co.uk  Sun Nov  7 19:01:53 2010
Return-Path: <rbriscoe@jungle.bt.co.uk>
X-Original-To: pcn@core3.amsl.com
Delivered-To: pcn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B44EB28C108 for <pcn@core3.amsl.com>; Sun,  7 Nov 2010 19:01:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.117
X-Spam-Level: 
X-Spam-Status: No, score=-2.117 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K3SffLg6OHOz for <pcn@core3.amsl.com>; Sun,  7 Nov 2010 19:01:46 -0800 (PST)
Received: from smtp1.smtp.bt.com (smtp1.smtp.bt.com [217.32.164.137]) by core3.amsl.com (Postfix) with ESMTP id 83D2B3A6962 for <pcn@ietf.org>; Sun,  7 Nov 2010 19:01:46 -0800 (PST)
Received: from i2kc06-ukbr.domain1.systemhost.net ([193.113.197.70]) by smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 8 Nov 2010 03:02:05 +0000
Received: from cbibipnt05.iuser.iroot.adidom.com ([147.149.196.177]) by i2kc06-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(6.0.3790.4675); Mon, 8 Nov 2010 03:02:04 +0000
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by cbibipnt05.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a P0803.399); id 1289185323150; Mon, 8 Nov 2010 03:02:03 +0000
Received: from MUT.jungle.bt.co.uk ([10.142.80.34]) by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id oA831wKm012180; Mon, 8 Nov 2010 03:02:00 GMT
Message-Id: <201011080302.oA831wKm012180@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 08 Nov 2010 11:01:57 +0800
To: Georgios Karagiannis <karagian@cs.utwente.nl>
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
In-Reply-To: <UDhy9t0v.1287719039.9205420.karagian@ewi.utwente.nl>
References: <20101022033003.4F7D93A6826@core3.amsl.com> <UDhy9t0v.1287719039.9205420.karagian@ewi.utwente.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 08 Nov 2010 03:02:04.0351 (UTC) FILETIME=[5251ECF0:01CB7EF1]
Cc: "pcn@ietf.org" <pcn@ietf.org>
Subject: Re: [PCN] I-D Action:draft-ietf-pcn-encoding-comparison-03.txt
X-BeenThere: pcn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PCN WG list <pcn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcn>
List-Post: <mailto:pcn@ietf.org>
List-Help: <mailto:pcn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2010 03:01:53 -0000

Georgios,

Do you think we should ask for WGLC on this now?


Bob

At 18:43 22/10/2010, Georgios Karagiannis wrote:
>Hi all
>
>A new version (03) of the draft-ietf-pcn-encoding-comparison has just
>been submitted. We (and especially Kwok) implemented severeal
>modifications compared to version 02, please see below:
>
>http://tools.ietf.org/rfcdiff?url2=draft-ietf-pcn-encoding-comparison-03
>
>Best regards,
>Georgios
>
>
>On 10/22/2010, "Internet-Drafts@ietf.org" <Internet-Drafts@ietf.org>
>wrote:
>
> >A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
> >This draft is a work item of the Congestion and Pre-Congestion 
> Notification Working Group of the IETF.
> >
> >
> >       Title           : Pre-Congestion Notification Encoding Comparison
> >       Author(s)       : K. Chan, et al.
> >       Filename        : draft-ietf-pcn-encoding-comparison-03.txt
> >       Pages           : 38
> >       Date            : 2010-10-21
> >
> >Pre-congestion notification (PCN) is a link-specific and load-
> >dependent packet marking mechanism for Differentiated Services
> >networks.  The packet markings are evaluated by egress nodes of PCN
> >domains and the result is used for admission control and flow
> >termination decisions.  Two different types of markings have been
> >defined.  This document gives a summary of the marking requirements,
> >the constraints to encode them in the current IP header (version 4
> >and above), and it explains why the PCN WG currently supports
> >different encoding schemes for PCN marking.
> >
> >A URL for this Internet-Draft is:
> >http://www.ietf.org/internet-drafts/draft-ietf-pcn-encoding-compari 
> son-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.
>_______________________________________________
>PCN mailing list
>PCN@ietf.org
>https://www.ietf.org/mailman/listinfo/pcn

________________________________________________________________
Bob Briscoe,                                BT Innovate & Design 


From toby@moncaster.com  Mon Nov  8 01:46:14 2010
Return-Path: <toby@moncaster.com>
X-Original-To: pcn@core3.amsl.com
Delivered-To: pcn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BBC1F28C120 for <pcn@core3.amsl.com>; Mon,  8 Nov 2010 01:46:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.042
X-Spam-Level: 
X-Spam-Status: No, score=-2.042 tagged_above=-999 required=5 tests=[AWL=0.207,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q9sX2KPlCKmE for <pcn@core3.amsl.com>; Mon,  8 Nov 2010 01:46:13 -0800 (PST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.10]) by core3.amsl.com (Postfix) with ESMTP id B9BBE28C0F2 for <pcn@ietf.org>; Mon,  8 Nov 2010 01:46:12 -0800 (PST)
Received: from TobysHP (host86-167-110-184.range86-167.btcentralplus.com [86.167.110.184]) by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis) id 0LrqLm-1OXm013gQI-013gG0; Mon, 08 Nov 2010 10:46:32 +0100
From: "Toby Moncaster" <toby@moncaster.com>
To: "'Bob Briscoe'" <rbriscoe@jungle.bt.co.uk>, "'PCN IETF list'" <pcn@ietf.org>
References: <201011080228.oA82SXmv012078@bagheera.jungle.bt.co.uk>
In-Reply-To: <201011080228.oA82SXmv012078@bagheera.jungle.bt.co.uk>
Date: Mon, 8 Nov 2010 09:46:31 -0000
Message-ID: <000801cb7f29$d3356670$79a03350$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Act+7K4wWgJdfTs/Sxe6IULu+dFmwAAPPA+Q
Content-Language: en-gb
X-Provags-ID: V02:K0:7tZSj8w5zFlMgNtqqiiBTpxzytqm3iXnjW2hUjLmfeb 7hORfMhNDnc2Qu3rOf7rEPLQtRD4oLwiG5xxNzasQx2HVjQlM5 vKIycuOnxipiu3CcxS0931cLsV159FOjG141OXErwph5ZR111h Asg3KgSVUpM8ghu2hJUlhIrAu2QqwJcZbDz2CbeAleuJ+zS973 45o4/i9zuzCk8qfZeg7nN96ommzKElNhIQctoQMLXA=
Subject: Re: [PCN] Fwd: [ADs] AUTH48 [MF]: RFC 6040 <draft-ietf-tsvwg-ecn-tunnel-10.txt> NOW AVAILABLE
X-BeenThere: pcn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PCN WG list <pcn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcn>
List-Post: <mailto:pcn@ietf.org>
List-Help: <mailto:pcn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2010 09:46:14 -0000

Brilliant! Well done Bob... Not only will this make life much easier for =
PCN
(as it makes 3-in-1 the obvious encoding choice), it will also be pretty
useful generally since it retrieves (or allows additional use of) a =
valuable
bit of header space in IP...

Toby

> -----Original Message-----
> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of
> Bob Briscoe
> Sent: 08 November 2010 02:29
> To: PCN IETF list
> Subject: [PCN] Fwd: [ADs] AUTH48 [MF]: RFC 6040 <draft-ietf-tsvwg-ecn-
> tunnel-10.txt> NOW AVAILABLE
>=20
> PCN folks,
>=20
> Just to let you know,
> <draft-ietf-tsvwg-ecn-tunnel-10.txt> has been
> through the RFC editor and is awaiting Dave
> Harrington's sign-off. If approved, it would become RFC 6040.
>=20
> I believe this tunnelling issue held back PCN
> considerably. Even with RFC6040, it would require
> vendors to implement it in order to simplify our PCN encoding choice.
>=20
>=20
> Bob
>=20
>=20
> >Date: Thu, 28 Oct 2010 00:08:46 +0100
> >To: Megan Ferguson <mferguson@amsl.com>
> >From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
> >Subject: Re: [ADs] AUTH48 [MF]: RFC 6040
> ><draft-ietf-tsvwg-ecn-tunnel-10.txt> NOW AVAILABLE
> >Cc: <rfc-editor@rfc-editor.org>,
> ><tsvwg-ads@tools.ietf.org>, <tsvwg-chairs@tools.ietf.org>
> >Bcc: =83\In 2009
> >
> >Megan,
> >
> >Thanks.
> >
> >Altho you've already accepted my approval, this
> >is just to confirm I've checked it again, and I approve again.
> >
> >
> >Bob
> >
> >At 16:04 27/10/2010, Megan Ferguson wrote:
> >>Hi Bob and *ADs,
> >>
> >>Thank you for your reply.  We have updated our
> >>files as requested below.  These updates are viewable at:
> >>
> >>http://www.rfc-editor.org/authors/rfc6040.xml
> >>http://www.rfc-editor.org/authors/rfc6040.txt
> >>http://www.rfc-editor.org/authors/rfc6040-lastdiff.html
> >>
> >>For your convenience, we have posted a diff
> >>file highlighting all changes to date at:
> >>
> >>http://www.rfc-editor.org/authors/rfc6040-diff.html
> >>
> >>Please review the document carefully to ensure
> >>satisfaction as we do not make changes once the
> >>document has been published as an RFC.  Note
> >>that it may be necessary for you to refresh
> >>your browser to view the most recent version of the document.
> >>
> >>Upon careful review, please contact us with any
> >>further updates.  As you indicated your
> >>approval of the text in this form in your
> >>previous message, we have updated your AUTH48 status to "Approved"
> at:
> >>
> >>http://www.rfc-editor.org/auth48/rfc6040
> >>
> >>*ADs,
> >>
> >>Please review and approve the changes viewable at:
> >>
> >>http://www.rfc-editor.org/authors/rfc6040-lastdiff.html
> >>
> >>Thank you.
> >>
> >>RFC Editor/mf
> >>
> >>On Oct 26, 2010, at 3:03 PM, Bob Briscoe wrote:
> >>
> >> > RFC Editor,
> >> >
> >> > Thank you for this.
> >> >
> >> > I'm more than happy with everything you have
> >> changed, excepting for one or two that I have
> >> 'improved' in the attached XML. All changes
> >> should be self-explanatory, except in a few
> >> cases where the points below may help justify my changes:
> >> >
> >> > 1) Abstract & Introduction:
> >> > In both cases I prefer
> >> >  "previously unused combinations of inner and outer headers" to
> >> >  "previously unused combinations of the inner and outer header".
> >> > Otherwise the addition of the definite
> >> article changes the sense from "combinations
> >> of various settings of each header" to
> >> "combinations of one particular inner header and one particular
> outer header."
> >> >
> >> > 2) I noticed you had changed "cater for an
> >> historic security concern" to "cater to an historic security
> concern".
> >> > This grates to a British ear. For the sense
> >> of "pander to", Collins Dictionary says the
> >> latter is American English, while the former
> >> is British. Given you have allowed the
> >> document spelling to remain in British
> >> English, it would be consistent to use British
> >> wording too. See:
> <http://bbs.chinadaily.com.cn/viewthread.php?tid=3D575192>
> >> >
> >> > 3) On the subject of British vs American, I
> >> notice standardization with a 'z' in the
> >> boilerplate is inconsistent with the British
> >> English 'standardisation' spelling in the body of the document.
> >> >
> >> > A also noticed a couple of my own errors
> >> while reading through. I assume Gorry, as
> >> shepherd, can verify that these changes are acceptable:
> >> >
> >> > 4) In early drafts we sometimes used the
> >> word 'inner' ambiguously for  'incoming' (at
> >> ingress) and 'outgoing' (at egress). I
> >> corrected a number of instances where this
> >> ambiguity remained - all but one were in the
> >> appendices that fewer people have reviewed.
> >> >
> >> > 5) To avoid confusion with the defined terms
> >> outgoing (at egress) and incoming (at ingress)
> >> I changed 'outgoing' (at ingress) and
> >> 'incoming' (at egress) to respectively 'departing' and 'arriving'.
> >> >
> >> > 6) I corrected 'PCN excess-rate marking' to
> >> 'PCN excess-traffic-marking', which was the term finally agreed on
> in RFC5670.
> >> >
> >> >
> >> > Thank you.
> >> >
> >> >
> >> > Bob
> >> >
> >> > At 20:43 25/10/2010, rfc-editor@rfc-editor.org wrote:
> >> >
> >> >> Bob,
> >> >>
> >> >> While reviewing this document during
> >> AUTH48, please resolve (as necessary) the
> >> following questions, which are also in the XML file.
> >> >>
> >> >> 1) <!--[rfced] Please note that after you have approved the
> document,
> >> >> post-xml2rfc changes will be made to update the header and
> >> >> boilerplate as described in RFC 5741.
> >> >> -->
> >> >>
> >> >>
> >> >> 2) <!--[rfced] Does "Section 5" apply to both RFC 3168 and RFC
> 4774?
> >> >>
> >> >> Original:
> >> >>   If these defaults do not meet a particular requirement, an
> alternate
> >> >>   ECN tunnelling scheme can be introduced as part of the
> definition of
> >> >>   an alternate congestion marking scheme used by a specific
> Diffserv
> >> >>   PHB (see section 5 of [RFC3168] and [RFC4774]).
> >> >>
> >> >> If not, perhaps:
> >> >>   If these defaults do not meet a particular requirement, an
> alternate
> >> >>   ECN tunnelling scheme can be introduced as part of the
> definition of
> >> >>   an alternate congestion marking scheme used by a specific
> Diffserv
> >> >>   PHB (see RFC 4774 and Section 5 of RFC 3168).
> >> >> -->
> >> >>
> >> >>
> >> >> 3) <!-- [rfced] RFC 4306 was obsoleted by RFC 5996.
> >> >> How may this text be updated to include mention of RFC 5996?
> >> >>
> >> >> Current:
> >> >>      For instance, IPsec tunnel endpoints compatible with RFC
> 4301
> >> >>      invariably use Internet Key Exchange Protocol version 2
> (IKEv2)
> >> >>      [RFC4306] for key exchange, which was introduced alongside
> RFC
> >> >>      4301.
> >> >>
> >> >> Perhaps:
> >> >>      For instance, IPsec tunnel endpoints compatible with RFC
> 4301
> >> >>      invariably use Internet Key Exchange Protocol version 2
> (IKEv2)
> >> >>      [RFC4306] for key exchange, which was introduced alongside
> RFC
> >> >>      4301.  (Note: [RFC4306] has been obsoleted by [RFC5996].)
> >> >> -->
> >> >>
> >> >>
> >> >> 4) <!-- [rfced] Please clarify this
> >> sentence, especially "8b per datagram covert channel".
> >> >>
> >> >> Original:
> >> >>   Of course, an
> >> >>   administrator considering copying of the DS field has to take
> into
> >> >>   account that it could be concatenated with the ECN field =
giving
> an 8b
> >> >>   per datagram covert channel.
> >> >>
> >> >> Perhaps:
> >> >>   Of course, an
> >> >>   administrator that considers copying the DS field has to take
> into
> >> >>   account that it could be concatenated with the ECN field,
> giving an
> >> >>   eight-bit covert channel for each datagram.
> >> >> -->
> >> >>
> >> >>
> >> >> Thank you.
> >> >>
> >> >> RFC Editor/ah
> >> >>
> >> >>
> >> >> On Oct 25, 2010, at 3:42 PM, rfc-editor@rfc-editor.org wrote:
> >> >>
> >> >>
> >> >> *****IMPORTANT*****
> >> >>
> >> >> Updated 2010/10/25
> >> >>
> >> >> RFC Author(s):
> >> >> --------------
> >> >>
> >> >> Instructions for Completing AUTH48 in XML
> >> >>
> >> >> This is your last chance to make changes to your RFC-to-be:
> >> >> draft-ietf-tsvwg-ecn-tunnel-10.txt.
> >> >> Once the document is published as an RFC, we will not make
> changes.
> >> >> Please follow the instructions below to complete the AUTH48
> process.
> >> >>
> >> >> 1) Review the edited document completely.  The files are
> available here:
> >> >>
> >> >>  http://www.rfc-editor.org/authors/rfc6040.txt
> >> >>  http://www.rfc-editor.org/authors/rfc6040-diff.html
> >> >>
> >> >>  We recommend reviewing the entire document, not just the diff
> file.
> >> >>  The placement of page breaks will be handled during the final
> stages of
> >> >>  publication (typically post-xml2rfc processing).
> >> >>
> >> >> 2) Review and resolve (as necessary) any questions raised by the
> RFC
> >> >>  Editor.  The questions (if any) have been included in the XML
> file as
> >> >>  comments marked <!-- [rfced] ... --> and
> >> will be sent in a subsequent email.
> >> >>
> >> >>  Retrieve the edited XML file here:
> >> >>
> >> >>     http://www.rfc-editor.org/authors/rfc6040.xml
> >> >>
> >> >>  (Note that you may need to view the page source to save the
> file.)
> >> >>
> >> >> 3) Send us your changes or respond with your approval for
> publication.
> >> >>  Please use 'Reply All' so that rfc-editor@rfc-editor.org and =
the
> parties
> >> >>  CC'ed on this message receive your
> >> response. Note that your document will
> >> >>  not move forward until we have received approvals from each of
> the
> >> >>  authors listed on the front page.
> >> >>
> >> >>  If sending changes, please do one of the following:
> >> >>
> >> >>  a. Update the provided XML file, then email us the revised XML
> file.
> >> >>     You may use any filename for the revised file; we will =
rename
> it
> >> >>     before posting it.
> >> >>
> >> >>  --OR--
> >> >>
> >> >>  b. Provide us with an explicit list of changes in the this
> format.
> >> >>
> >> >>     Section # (or indicate Global)
> >> >>
> >> >>     OLD:
> >> >>     old text
> >> >>
> >> >>     NEW:
> >> >>     new text
> >> >>
> >> >>  Be sure to pay particular attention to these areas of the
> document:
> >> >>  - IANA Considerations updates (if applicable)
> >> >>  - Contact information
> >> >>  - Copyright notice and legends (see item 5 for more details)
> >> >>
> >> >> 4) Review changes submitted by your coauthors.  We assume that
> you
> >> >>  will speak up if you do not agree with the proposed changes.
> That is,
> >> >>  your silence is your assent to changes submitted by your
> coauthors.
> >> >>  Note that any changes that are beyond editorial will be sent to
> the
> >> >>  relevant body for approval.
> >> >>
> >> >>  Additional diff files will be posted as authors send updates =
for
> the
> >> >>  document.  We recommend viewing these  later diff files to
> identify and
> >> >>  review changes submitted by your coauthors.
> >> >>
> >> >> 5) Review the copyright notice and legends as defined in RFC =
5378
> and
> >> >>  the Trust Legal Provisions (TLP --
> >> http://trustee.ietf.org/license-info/).
> >> >>
> >> >>  If your document was approved for publication with a pre-RFC-
> 5378
> >> >>  copyright notice, we have applied the text from section 6.c.iii
> of the
> >> >>  TLP.  Please consider whether this text is required (note that
> the
> >> >>  6.c.iii text is not applicable to Independent Stream RFCs).  =
See
> item
> >> >>  4.5 of the "Copyright FAQ" at http://trustee.ietf.org/faqs.html
> for
> >> >>  guidance on whether this text applies to your document.
> >> >>
> >> >> 6) Please reply, as the document will not be published until we
> receive
> >> >>  approvals from each author.  The details of the AUTH48 status =
of
> your
> >> >>  document are here:
> >> >>
> >> >>  http://www.rfc-editor.org/auth48/rfc6040
> >> >>
> >> >> Thank you for your cooperation,
> >> >>
> >> >> RFC Editor
> >> >>
> >> >> --------------------------------------
> >> >> RFC6040 (draft-ietf-tsvwg-ecn-tunnel-10)
> >> >> --------------------------------------
> >> >> Title            : Tunnelling of Explicit Congestion =
Notification
> >> >> Author(s)        : B. Briscoe
> >> >> WG Chair(s)      : James Polk, Gorry Fairhurst
> >> >> Area Director(s) : David Harrington, Lars Eggert
> >> >
> >> > ________________________________________________________________
> >> > Bob
> >> Briscoe,                                BT Innovate & Design
> <rfc6040_b.xml>
> >
> >________________________________________________________________
> >Bob Briscoe,                                BT Innovate & Design
>=20
> ________________________________________________________________
> Bob Briscoe,                                BT Innovate & Design
>=20
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn


From philip.eardley@bt.com  Fri Nov 12 09:10:29 2010
Return-Path: <philip.eardley@bt.com>
X-Original-To: pcn@core3.amsl.com
Delivered-To: pcn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 427073A6A77 for <pcn@core3.amsl.com>; Fri, 12 Nov 2010 09:10:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.746
X-Spam-Level: 
X-Spam-Status: No, score=-101.746 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_72=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LwO4FUG2aAHG for <pcn@core3.amsl.com>; Fri, 12 Nov 2010 09:10:21 -0800 (PST)
Received: from smtpe1.intersmtp.com (smtp62.intersmtp.COM [62.239.224.235]) by core3.amsl.com (Postfix) with ESMTP id 50F113A6A8B for <pcn@ietf.org>; Fri, 12 Nov 2010 09:10:16 -0800 (PST)
Received: from EVMHT62-UKRD.domain1.systemhost.net (10.36.3.128) by RDW083A006ED62.smtp-e2.hygiene.service (10.187.98.11) with Microsoft SMTP Server (TLS) id 8.2.254.0; Fri, 12 Nov 2010 17:10:48 +0000
Received: from EMV67-UKRD.domain1.systemhost.net ([169.254.1.25]) by EVMHT62-UKRD.domain1.systemhost.net ([10.36.3.128]) with mapi; Fri, 12 Nov 2010 17:10:48 +0000
From: <philip.eardley@bt.com>
To: <rbriscoe@jungle.bt.co.uk>
Date: Fri, 12 Nov 2010 17:10:46 +0000
Thread-Topic: [PCN] I-D Action:draft-ietf-pcn-encoding-comparison-03.txt
Thread-Index: AcuCgpMAkRUjs0/dTeylURqoGAdQJgAAEMNQ
Message-ID: <4C22FF8FA5626046BF68899C06A0C9F7113549DA0A@EMV67-UKRD.domain1.systemhost.net>
References: <20101022033003.4F7D93A6826@core3.amsl.com> <UDhy9t0v.1287719039.9205420.karagian@ewi.utwente.nl> <201011080302.oA831wKm012180@bagheera.jungle.bt.co.uk> <33984F9086BE46838C4DDE5757EA04C7@dynamic.ewi.utwente.nl> <4C22FF8FA5626046BF68899C06A0C9F71135434583@EMV67-UKRD.domain1.systemhost.net> <201011121559.oACFx9uq005772@bagheera.jungle.bt.co.uk>
In-Reply-To: <201011121559.oACFx9uq005772@bagheera.jungle.bt.co.uk>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: pcn@ietf.org
Subject: Re: [PCN] I-D Action:draft-ietf-pcn-encoding-comparison-03.txt
X-BeenThere: pcn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PCN WG list <pcn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcn>
List-Post: <mailto:pcn@ietf.org>
List-Help: <mailto:pcn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Nov 2010 17:10:29 -0000

(on-list)

My mental model is that we have the Baseline encoding as Standards track an=
d 3-in-1 as Experimental track. This doesn't need an update to the baseline=
 (nor its obsoletion).=20

The Baseline has words about restrictions /guidelines on Experimental encod=
ings so that they're compatible with the baseline. If 3-in-1 is standards t=
rack, then those guidelines would be wrong - in fact it would then be hard =
to see how to allow any Experimental encodings.

This leads me to think there are (only) 2 possibilities:-

* Baseline RFC5696 + Experimental 3-in-1 (which does not update baseline)
* Baseline + 3-in-1 as a new Standards track doc

I'm strongly in favour of the first option, since this requires no more wor=
k (or almost none).

This discussion also makes me think that 3-in-1 should be moved through WG =
last call, *then* the encoding comparison has its final updates & is WGLC.=
=20

-----Original Message-----
From: Briscoe,RJ,Bob,XVR9 BRISCORJ R=20
Sent: 12 November 2010 15:59
To: Eardley,PL,Philip,DEE1 R
Cc: karagian@cs.utwente.nl
Subject: RE: [PCN] I-D Action:draft-ietf-pcn-encoding-comparison-03.txt

Phil,

BTW, do we need to be off-list? Feel free to cc reply to PCN list.

Yours are all good points.

1/ I think the comparison draft should also make it clear that=20
choosing encodings for stds track does not preclude also allowing=20
experimental track ones. For instance, neither baseline nor 3-in-1=20
support e2e ECN or ECMP. So if someone wishes to experiment with=20
them, we're not stopping them.

2/ There is still the question of whether we should:
* produce a single RFC that OBSOLETES baseline and describes both=20
baseline and 3-in-1 in one RFC.
* or take 3-in-1 through to RFC as an UPDATE to baseline.

Personally I think the former would be less confusing for future=20
implementers. But it's not how we've currently written 3-in-1.


Bob

At 05:19 08/11/2010, philip.eardley@bt.com wrote:
>Basically i think yes, but:
>
>- now bob's tunnelling is done and we'll only go forward with one=20
>exptal extension [if i understand right], this should come clearer=20
>as a conclusion.
>- note [check throughout], rfc 3260 the correct terminology seems to=20
>be: DSField - 6 bits
>
>- Fig 6, i know this got updated several times. Suggest check this=20
>is the final versionin the soon-to-be-rfc
>
>- section 4 says PCN WG produces 4 different pcn encodings. My=20
>impression is that we're not going forward with all 4 but only 2=20
>[baseline + 3-in-1] will be rfcs. Therefore this section needs some adjust=
ment:
>- in the intro
>- suggest leave the bulk of the section untouched
>- add a short section 5, which is the "final answer" - ie the=20
>baseline + 1 extended encoding, and the key points why they were=20
>chosen [minimise use of DSCPs, allow non-PCN traffic, etc]. I think=20
>it would be very useful for a reader to be able to skip to the final=20
>answer and the summary of Why these 2 encodings were chosen.
>
>-----Original Message-----
>From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
>Sent: 08 November 2010 10:51
>To: Briscoe,RJ,Bob,XVR9 BRISCORJ R
>Cc: Eardley,PL,Philip,DEE1 R
>Subject: RE: [PCN] I-D Action:draft-ietf-pcn-encoding-comparison-03.txt
>
>
>  Hi Bob
>
>It is okay with me! Hoever, Phil had previously some comments on the
>comparison draft,
>and I would like to konow if he is satsified with this version!
>
>Best regards,
>Georgios
>
>
> > -----Original Message-----
> > From: Bob Briscoe [mailto:rbriscoe@jungle.bt.co.uk]
> > Sent: maandag 8 november 2010 4:02
> > To: Georgios Karagiannis
> > Cc: pcn@ietf.org
> > Subject: Re: [PCN] I-D
> > Action:draft-ietf-pcn-encoding-comparison-03.txt
> >
> > Georgios,
> >
> > Do you think we should ask for WGLC on this now?
> >
> >
> > Bob
> >
> > At 18:43 22/10/2010, Georgios Karagiannis wrote:
> > >Hi all
> > >
> > >A new version (03) of the draft-ietf-pcn-encoding-comparison
> > has just
> > >been submitted. We (and especially Kwok) implemented severeal
> > >modifications compared to version 02, please see below:
> > >
> > >http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-pcn-encoding-co
>mparison-0
> > >3
> > >
> > >Best regards,
> > >Georgios
> > >
> > >
> > >On 10/22/2010, "Internet-Drafts@ietf.org" <Internet-Drafts@ietf.org>
> > >wrote:
> > >
> > > >A New Internet-Draft is available from the on-line Internet-Drafts
> > > directories.
> > > >This draft is a work item of the Congestion and Pre-Congestion
> > > Notification Working Group of the IETF.
> > > >
> > > >
> > > >       Title           : Pre-Congestion Notification
> > Encoding Comparison
> > > >       Author(s)       : K. Chan, et al.
> > > >       Filename        : draft-ietf-pcn-encoding-comparison-03.txt
> > > >       Pages           : 38
> > > >       Date            : 2010-10-21
> > > >
> > > >Pre-congestion notification (PCN) is a link-specific and load-
> > > >dependent packet marking mechanism for Differentiated Services
> > > >networks.  The packet markings are evaluated by egress
> > nodes of PCN
> > > >domains and the result is used for admission control and flow
> > > >termination decisions.  Two different types of markings have been
> > > >defined.  This document gives a summary of the marking
> > requirements,
> > > >the constraints to encode them in the current IP header (version 4
> > > >and above), and it explains why the PCN WG currently supports
> > > >different encoding schemes for PCN marking.
> > > >
> > > >A URL for this Internet-Draft is:
> > > >http://www.ietf.org/internet-drafts/draft-ietf-pcn-encoding-compari
> > > son-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.
> > >_______________________________________________
> > >PCN mailing list
> > >PCN@ietf.org
> > >https://www.ietf.org/mailman/listinfo/pcn
> >
> > ________________________________________________________________
> > Bob Briscoe,                                BT Innovate & Design
> >

________________________________________________________________
Bob Briscoe,                                BT Innovate & Design=20


From toby@moncaster.com  Sat Nov 13 02:00:23 2010
Return-Path: <toby@moncaster.com>
X-Original-To: pcn@core3.amsl.com
Delivered-To: pcn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 76A223A6AEF for <pcn@core3.amsl.com>; Sat, 13 Nov 2010 02:00:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_72=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pzxbXiVs6DQn for <pcn@core3.amsl.com>; Sat, 13 Nov 2010 02:00:16 -0800 (PST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.10]) by core3.amsl.com (Postfix) with ESMTP id 105353A6AC8 for <pcn@ietf.org>; Sat, 13 Nov 2010 02:00:16 -0800 (PST)
Received: from TobysHP (host86-149-152-36.range86-149.btcentralplus.com [86.149.152.36]) by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis) id 0MTcI8-1P8Iwi0Dbs-00QpeL; Sat, 13 Nov 2010 11:00:48 +0100
From: "Toby Moncaster" <toby@moncaster.com>
To: <philip.eardley@bt.com>, <rbriscoe@jungle.bt.co.uk>
References: <20101022033003.4F7D93A6826@core3.amsl.com>	<UDhy9t0v.1287719039.9205420.karagian@ewi.utwente.nl>	<201011080302.oA831wKm012180@bagheera.jungle.bt.co.uk>	<33984F9086BE46838C4DDE5757EA04C7@dynamic.ewi.utwente.nl>	<4C22FF8FA5626046BF68899C06A0C9F71135434583@EMV67-UKRD.domain1.systemhost.net>	<201011121559.oACFx9uq005772@bagheera.jungle.bt.co.uk> <4C22FF8FA5626046BF68899C06A0C9F7113549DA0A@EMV67-UKRD.domain1.systemhost.net>
In-Reply-To: <4C22FF8FA5626046BF68899C06A0C9F7113549DA0A@EMV67-UKRD.domain1.systemhost.net>
Date: Sat, 13 Nov 2010 10:00:46 -0000
Message-ID: <000601cb8319$a4f5e2f0$eee1a8d0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
thread-index: AcuCgpMAkRUjs0/dTeylURqoGAdQJgAAEMNQACVKPzA=
Content-Language: en-gb
X-Provags-ID: V02:K0:2qkubfLukQ/vu0D+QYA43gT/mgGBvm0Eas+eYm1sxI6 6mkMlX1J8/ThX9OJwv3AZC3zN+8JJjINHsD0ya4pMfun8khvNu uncugl8H8PKStaQH90Ub5+wbb+ifNUVQgz6l2KBUzat5FTzzF+ XyyrBg8Z8M+N5r5DlgzgNh1ky2ONLd9xAdezCrVOpG3e/Kbc0f cxvnDoArM9Cx6/SN69bozcOmCpkniB4o2DPmEWB+CY=
Cc: pcn@ietf.org
Subject: Re: [PCN] I-D Action:draft-ietf-pcn-encoding-comparison-03.txt
X-BeenThere: pcn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PCN WG list <pcn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcn>
List-Post: <mailto:pcn@ietf.org>
List-Help: <mailto:pcn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Nov 2010 10:00:23 -0000

Inline 

> -----Original Message-----
> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of
> philip.eardley@bt.com
> Sent: 12 November 2010 17:11
> To: rbriscoe@jungle.bt.co.uk
> Cc: pcn@ietf.org
> Subject: Re: [PCN] I-D Action:draft-ietf-pcn-encoding-comparison-03.txt
> 
> (on-list)
> 
> My mental model is that we have the Baseline encoding as Standards
> track and 3-in-1 as Experimental track. This doesn't need an update to
> the baseline (nor its obsoletion).

Although at some point in future we would need to address moving 3-in-1 to
STDs track... 

> 
> The Baseline has words about restrictions /guidelines on Experimental
> encodings so that they're compatible with the baseline. If 3-in-1 is
> standards track, then those guidelines would be wrong - in fact it
> would then be hard to see how to allow any Experimental encodings.
> 
> This leads me to think there are (only) 2 possibilities:-
> 
> * Baseline RFC5696 + Experimental 3-in-1 (which does not update
> baseline)
> * Baseline + 3-in-1 as a new Standards track doc
> 
> I'm strongly in favour of the first option, since this requires no more
> work (or almost none).

you /could/ choose the second option. That would still need to address
legacy cases where Bob's new RFC hasn't been implemented (I guess 3-in-1
would be presented as an extension with a MUST to implement the updated
tunnelling). But as I say above, at some point in future, if 3-in-1 proves
successful it will need to be moved to STDs track anyway so there will still
be work to be done. On the other hand creating a merged document will take
ages. 

How about this as a possibility: 3-in-1 is altered so it has 2 modes of
operation:

_Limited Mode_ is the same as baseline and is used when the tunnelling isn't
there. This would set out the encoding and state that it is the same as
RFC5696.

_Full Mode_ is the full 3-in-1. Tunnelling becomes a MUST, etc.

Limited and Full modes can't be run in the same PCN-domain (or can they? I
assume not...).

That way, if it is a success it should be pretty easy to subsequently
obsolete baseline encoding and move the new document to STDs track?

> 
> This discussion also makes me think that 3-in-1 should be moved through
> WG last call, *then* the encoding comparison has its final updates & is
> WGLC.

I'm sort of tempted to agree - originally the encoding comparison was meant
to present all the encoding options along with pros and cons to allow a
choice to be made. Baseline sort of obsolete that, so now encoding
comparison has to act as a historical record of how we chose the encodings
we did. If 3-in-1 is going to be a significant and viable alternative to
baseline then it needs a thorough treatment in the comparison document.

Toby

> 
> -----Original Message-----
> From: Briscoe,RJ,Bob,XVR9 BRISCORJ R
> Sent: 12 November 2010 15:59
> To: Eardley,PL,Philip,DEE1 R
> Cc: karagian@cs.utwente.nl
> Subject: RE: [PCN] I-D Action:draft-ietf-pcn-encoding-comparison-03.txt
> 
> Phil,
> 
> BTW, do we need to be off-list? Feel free to cc reply to PCN list.
> 
> Yours are all good points.
> 
> 1/ I think the comparison draft should also make it clear that
> choosing encodings for stds track does not preclude also allowing
> experimental track ones. For instance, neither baseline nor 3-in-1
> support e2e ECN or ECMP. So if someone wishes to experiment with
> them, we're not stopping them.
> 
> 2/ There is still the question of whether we should:
> * produce a single RFC that OBSOLETES baseline and describes both
> baseline and 3-in-1 in one RFC.
> * or take 3-in-1 through to RFC as an UPDATE to baseline.
> 
> Personally I think the former would be less confusing for future
> implementers. But it's not how we've currently written 3-in-1.
> 
> 
> Bob
> 
> At 05:19 08/11/2010, philip.eardley@bt.com wrote:
> >Basically i think yes, but:
> >
> >- now bob's tunnelling is done and we'll only go forward with one
> >exptal extension [if i understand right], this should come clearer
> >as a conclusion.
> >- note [check throughout], rfc 3260 the correct terminology seems to
> >be: DSField - 6 bits
> >
> >- Fig 6, i know this got updated several times. Suggest check this
> >is the final versionin the soon-to-be-rfc
> >
> >- section 4 says PCN WG produces 4 different pcn encodings. My
> >impression is that we're not going forward with all 4 but only 2
> >[baseline + 3-in-1] will be rfcs. Therefore this section needs some
> adjustment:
> >- in the intro
> >- suggest leave the bulk of the section untouched
> >- add a short section 5, which is the "final answer" - ie the
> >baseline + 1 extended encoding, and the key points why they were
> >chosen [minimise use of DSCPs, allow non-PCN traffic, etc]. I think
> >it would be very useful for a reader to be able to skip to the final
> >answer and the summary of Why these 2 encodings were chosen.
> >
> >-----Original Message-----
> >From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> >Sent: 08 November 2010 10:51
> >To: Briscoe,RJ,Bob,XVR9 BRISCORJ R
> >Cc: Eardley,PL,Philip,DEE1 R
> >Subject: RE: [PCN] I-D Action:draft-ietf-pcn-encoding-comparison-
> 03.txt
> >
> >
> >  Hi Bob
> >
> >It is okay with me! Hoever, Phil had previously some comments on the
> >comparison draft,
> >and I would like to konow if he is satsified with this version!
> >
> >Best regards,
> >Georgios
> >
> >
> > > -----Original Message-----
> > > From: Bob Briscoe [mailto:rbriscoe@jungle.bt.co.uk]
> > > Sent: maandag 8 november 2010 4:02
> > > To: Georgios Karagiannis
> > > Cc: pcn@ietf.org
> > > Subject: Re: [PCN] I-D
> > > Action:draft-ietf-pcn-encoding-comparison-03.txt
> > >
> > > Georgios,
> > >
> > > Do you think we should ask for WGLC on this now?
> > >
> > >
> > > Bob
> > >
> > > At 18:43 22/10/2010, Georgios Karagiannis wrote:
> > > >Hi all
> > > >
> > > >A new version (03) of the draft-ietf-pcn-encoding-comparison
> > > has just
> > > >been submitted. We (and especially Kwok) implemented severeal
> > > >modifications compared to version 02, please see below:
> > > >
> > > >http://tools.ietf.org/rfcdiff?url2=draft-ietf-pcn-encoding-co
> >mparison-0
> > > >3
> > > >
> > > >Best regards,
> > > >Georgios
> > > >
> > > >
> > > >On 10/22/2010, "Internet-Drafts@ietf.org" <Internet-
> Drafts@ietf.org>
> > > >wrote:
> > > >
> > > > >A New Internet-Draft is available from the on-line Internet-
> Drafts
> > > > directories.
> > > > >This draft is a work item of the Congestion and Pre-Congestion
> > > > Notification Working Group of the IETF.
> > > > >
> > > > >
> > > > >       Title           : Pre-Congestion Notification
> > > Encoding Comparison
> > > > >       Author(s)       : K. Chan, et al.
> > > > >       Filename        : draft-ietf-pcn-encoding-comparison-
> 03.txt
> > > > >       Pages           : 38
> > > > >       Date            : 2010-10-21
> > > > >
> > > > >Pre-congestion notification (PCN) is a link-specific and load-
> > > > >dependent packet marking mechanism for Differentiated Services
> > > > >networks.  The packet markings are evaluated by egress
> > > nodes of PCN
> > > > >domains and the result is used for admission control and flow
> > > > >termination decisions.  Two different types of markings have
> been
> > > > >defined.  This document gives a summary of the marking
> > > requirements,
> > > > >the constraints to encode them in the current IP header (version
> 4
> > > > >and above), and it explains why the PCN WG currently supports
> > > > >different encoding schemes for PCN marking.
> > > > >
> > > > >A URL for this Internet-Draft is:
> > > > >http://www.ietf.org/internet-drafts/draft-ietf-pcn-encoding-
> compari
> > > > son-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.
> > > >_______________________________________________
> > > >PCN mailing list
> > > >PCN@ietf.org
> > > >https://www.ietf.org/mailman/listinfo/pcn
> > >
> > > ________________________________________________________________
> > > Bob Briscoe,                                BT Innovate & Design
> > >
> 
> ________________________________________________________________
> Bob Briscoe,                                BT Innovate & Design
> 
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn


From karagian@cs.utwente.nl  Mon Nov 15 03:34:03 2010
Return-Path: <karagian@cs.utwente.nl>
X-Original-To: pcn@core3.amsl.com
Delivered-To: pcn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D95A03A6C96 for <pcn@core3.amsl.com>; Mon, 15 Nov 2010 03:34:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.54
X-Spam-Level: 
X-Spam-Status: No, score=0.54 tagged_above=-999 required=5 tests=[AWL=-1.044,  BAYES_05=-1.11, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, J_CHICKENPOX_72=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ceWgKII86dNp for <pcn@core3.amsl.com>; Mon, 15 Nov 2010 03:33:56 -0800 (PST)
Received: from denhaag.ewi.utwente.nl (denhaag.ewi.utwente.nl [130.89.10.11]) by core3.amsl.com (Postfix) with ESMTP id 75D7528B797 for <pcn@ietf.org>; Mon, 15 Nov 2010 03:33:56 -0800 (PST)
Received: from ewi977 (ewi977.ewi.utwente.nl [130.89.12.129]) by denhaag.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id oAFBYLCs023187;  Mon, 15 Nov 2010 12:34:24 +0100 (MET)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: <philip.eardley@bt.com>, <rbriscoe@jungle.bt.co.uk>
References: <20101022033003.4F7D93A6826@core3.amsl.com> <UDhy9t0v.1287719039.9205420.karagian@ewi.utwente.nl> <201011080302.oA831wKm012180@bagheera.jungle.bt.co.uk> <33984F9086BE46838C4DDE5757EA04C7@dynamic.ewi.utwente.nl> <4C22FF8FA5626046BF68899C06A0C9F71135434583@EMV67-UKRD.domain1.systemhost.net> <201011121559.oACFx9uq005772@bagheera.jungle.bt.co.uk> <4C22FF8FA5626046BF68899C06A0C9F7113549DA0A@EMV67-UKRD.domain1.systemhost.net>
Date: Mon, 15 Nov 2010 12:34:17 +0100
Message-ID: <17A07FFA88A34F5C9A8E0CA7B53B92B4@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
Thread-Index: AcuCgpMAkRUjs0/dTeylURqoGAdQJgAAEMNQAI13XZA=
In-Reply-To: <4C22FF8FA5626046BF68899C06A0C9F7113549DA0A@EMV67-UKRD.domain1.systemhost.net>
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.11
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3 (denhaag.ewi.utwente.nl [130.89.10.11]); Mon, 15 Nov 2010 12:34:34 +0100 (MET)
Cc: pcn@ietf.org
Subject: Re: [PCN] I-D Action:draft-ietf-pcn-encoding-comparison-03.txt
X-BeenThere: pcn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PCN WG list <pcn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcn>
List-Post: <mailto:pcn@ietf.org>
List-Help: <mailto:pcn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Nov 2010 11:34:04 -0000

Hi Phil, Hi all

I agree with the proposal of Phil regarding the first option:
 
> * Baseline RFC5696 + Experimental 3-in-1 (which does not 
> update baseline)

It also makes sense to me, to first move 3-in-1 
through WG last call, and then the encoding comparison 
has its final updates & is WGLC!

Best regards,
Georgios



> -----Original Message-----
> From: philip.eardley@bt.com [mailto:philip.eardley@bt.com] 
> Sent: vrijdag 12 november 2010 18:11
> To: rbriscoe@jungle.bt.co.uk
> Cc: karagian@cs.utwente.nl; pcn@ietf.org
> Subject: RE: [PCN] I-D 
> Action:draft-ietf-pcn-encoding-comparison-03.txt
> 
> (on-list)
> 
> My mental model is that we have the Baseline encoding as 
> Standards track and 3-in-1 as Experimental track. This 
> doesn't need an update to the baseline (nor its obsoletion). 
> 
> The Baseline has words about restrictions /guidelines on 
> Experimental encodings so that they're compatible with the 
> baseline. If 3-in-1 is standards track, then those guidelines 
> would be wrong - in fact it would then be hard to see how to 
> allow any Experimental encodings.
> 
> This leads me to think there are (only) 2 possibilities:-
> 
> * Baseline RFC5696 + Experimental 3-in-1 (which does not 
> update baseline)
> * Baseline + 3-in-1 as a new Standards track doc
> 
> I'm strongly in favour of the first option, since this 
> requires no more work (or almost none).
> 
> This discussion also makes me think that 3-in-1 should be 
> moved through WG last call, *then* the encoding comparison 
> has its final updates & is WGLC. 
> 
> -----Original Message-----
> From: Briscoe,RJ,Bob,XVR9 BRISCORJ R
> Sent: 12 November 2010 15:59
> To: Eardley,PL,Philip,DEE1 R
> Cc: karagian@cs.utwente.nl
> Subject: RE: [PCN] I-D 
> Action:draft-ietf-pcn-encoding-comparison-03.txt
> 
> Phil,
> 
> BTW, do we need to be off-list? Feel free to cc reply to PCN list.
> 
> Yours are all good points.
> 
> 1/ I think the comparison draft should also make it clear 
> that choosing encodings for stds track does not preclude also 
> allowing experimental track ones. For instance, neither 
> baseline nor 3-in-1 support e2e ECN or ECMP. So if someone 
> wishes to experiment with them, we're not stopping them.
> 
> 2/ There is still the question of whether we should:
> * produce a single RFC that OBSOLETES baseline and describes 
> both baseline and 3-in-1 in one RFC.
> * or take 3-in-1 through to RFC as an UPDATE to baseline.
> 
> Personally I think the former would be less confusing for 
> future implementers. But it's not how we've currently written 3-in-1.
> 
> 
> Bob
> 
> At 05:19 08/11/2010, philip.eardley@bt.com wrote:
> >Basically i think yes, but:
> >
> >- now bob's tunnelling is done and we'll only go forward with one 
> >exptal extension [if i understand right], this should come clearer 
> >as a conclusion.
> >- note [check throughout], rfc 3260 the correct terminology seems to 
> >be: DSField - 6 bits
> >
> >- Fig 6, i know this got updated several times. Suggest check this 
> >is the final versionin the soon-to-be-rfc
> >
> >- section 4 says PCN WG produces 4 different pcn encodings. My 
> >impression is that we're not going forward with all 4 but only 2 
> >[baseline + 3-in-1] will be rfcs. Therefore this section 
> needs some adjustment:
> >- in the intro
> >- suggest leave the bulk of the section untouched
> >- add a short section 5, which is the "final answer" - ie the 
> >baseline + 1 extended encoding, and the key points why they were 
> >chosen [minimise use of DSCPs, allow non-PCN traffic, etc]. I think 
> >it would be very useful for a reader to be able to skip to the final 
> >answer and the summary of Why these 2 encodings were chosen.
> >
> >-----Original Message-----
> >From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> >Sent: 08 November 2010 10:51
> >To: Briscoe,RJ,Bob,XVR9 BRISCORJ R
> >Cc: Eardley,PL,Philip,DEE1 R
> >Subject: RE: [PCN] I-D 
> Action:draft-ietf-pcn-encoding-comparison-03.txt
> >
> >
> >  Hi Bob
> >
> >It is okay with me! Hoever, Phil had previously some comments on the
> >comparison draft,
> >and I would like to konow if he is satsified with this version!
> >
> >Best regards,
> >Georgios
> >
> >
> > > -----Original Message-----
> > > From: Bob Briscoe [mailto:rbriscoe@jungle.bt.co.uk]
> > > Sent: maandag 8 november 2010 4:02
> > > To: Georgios Karagiannis
> > > Cc: pcn@ietf.org
> > > Subject: Re: [PCN] I-D
> > > Action:draft-ietf-pcn-encoding-comparison-03.txt
> > >
> > > Georgios,
> > >
> > > Do you think we should ask for WGLC on this now?
> > >
> > >
> > > Bob
> > >
> > > At 18:43 22/10/2010, Georgios Karagiannis wrote:
> > > >Hi all
> > > >
> > > >A new version (03) of the draft-ietf-pcn-encoding-comparison
> > > has just
> > > >been submitted. We (and especially Kwok) implemented severeal
> > > >modifications compared to version 02, please see below:
> > > >
> > > >http://tools.ietf.org/rfcdiff?url2=draft-ietf-pcn-encoding-co
> >mparison-0
> > > >3
> > > >
> > > >Best regards,
> > > >Georgios
> > > >
> > > >
> > > >On 10/22/2010, "Internet-Drafts@ietf.org" 
> <Internet-Drafts@ietf.org>
> > > >wrote:
> > > >
> > > > >A New Internet-Draft is available from the on-line 
> Internet-Drafts
> > > > directories.
> > > > >This draft is a work item of the Congestion and Pre-Congestion
> > > > Notification Working Group of the IETF.
> > > > >
> > > > >
> > > > >       Title           : Pre-Congestion Notification
> > > Encoding Comparison
> > > > >       Author(s)       : K. Chan, et al.
> > > > >       Filename        : 
> draft-ietf-pcn-encoding-comparison-03.txt
> > > > >       Pages           : 38
> > > > >       Date            : 2010-10-21
> > > > >
> > > > >Pre-congestion notification (PCN) is a link-specific and load-
> > > > >dependent packet marking mechanism for Differentiated Services
> > > > >networks.  The packet markings are evaluated by egress
> > > nodes of PCN
> > > > >domains and the result is used for admission control and flow
> > > > >termination decisions.  Two different types of 
> markings have been
> > > > >defined.  This document gives a summary of the marking
> > > requirements,
> > > > >the constraints to encode them in the current IP 
> header (version 4
> > > > >and above), and it explains why the PCN WG currently supports
> > > > >different encoding schemes for PCN marking.
> > > > >
> > > > >A URL for this Internet-Draft is:
> > > > 
> >http://www.ietf.org/internet-drafts/draft-ietf-pcn-encoding-compari
> > > > son-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.
> > > >_______________________________________________
> > > >PCN mailing list
> > > >PCN@ietf.org
> > > >https://www.ietf.org/mailman/listinfo/pcn
> > >
> > > ________________________________________________________________
> > > Bob Briscoe,                                BT Innovate & Design
> > >
> 
> ________________________________________________________________
> Bob Briscoe,                                BT Innovate & Design 
> 



From menth@informatik.uni-tuebingen.de  Mon Nov 29 23:28:05 2010
Return-Path: <menth@informatik.uni-tuebingen.de>
X-Original-To: pcn@core3.amsl.com
Delivered-To: pcn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5E3B13A6B39 for <pcn@core3.amsl.com>; Mon, 29 Nov 2010 23:28:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level: 
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, HTML_MESSAGE=0.001, J_CHICKENPOX_93=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XMadbzNn1-Gb for <pcn@core3.amsl.com>; Mon, 29 Nov 2010 23:28:04 -0800 (PST)
Received: from mx3.informatik.uni-tuebingen.de (mx3.Informatik.Uni-Tuebingen.De [134.2.12.26]) by core3.amsl.com (Postfix) with SMTP id BCAF03A6925 for <pcn@ietf.org>; Mon, 29 Nov 2010 23:28:02 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx3.informatik.uni-tuebingen.de (Postfix) with ESMTP id A21CA529E; Tue, 30 Nov 2010 08:29:09 +0100 (MET)
X-Virus-Scanned: amavisd-new at informatik.uni-tuebingen.de
Received: from mx3.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx3.informatik.uni-tuebingen.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qD6ULzckF2yH; Tue, 30 Nov 2010 08:29:04 +0100 (MET)
Received: from zcs-pu.informatik.uni-tuebingen.de (zcs-pu.Informatik.Uni-Tuebingen.De [134.2.12.61]) by mx3.informatik.uni-tuebingen.de (Postfix) with ESMTP id AAEEB528F; Tue, 30 Nov 2010 08:29:04 +0100 (MET)
Received: from [192.168.1.101] (HSI-KBW-095-208-114-108.hsi5.kabel-badenwuerttemberg.de [95.208.114.108]) by zcs-pu.informatik.uni-tuebingen.de (Postfix) with ESMTP id 547FABCB74C; Tue, 30 Nov 2010 08:29:04 +0100 (CET)
Message-ID: <4CF4A7C0.2080403@informatik.uni-tuebingen.de>
Date: Tue, 30 Nov 2010 08:29:04 +0100
From: Michael Menth <menth@informatik.uni-tuebingen.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: "Dr. Bob Briscoe" <rbriscoe@jungle.bt.co.uk>
Content-Type: multipart/alternative; boundary="------------010501040302040105020204"
X-Mailman-Approved-At: Tue, 30 Nov 2010 07:06:51 -0800
Cc: pcn@ietf.org
Subject: [PCN] Fwd: RFC 6040 on Tunnelling of Explicit Congestion Notification
X-BeenThere: pcn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PCN WG list <pcn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcn>
List-Post: <mailto:pcn@ietf.org>
List-Help: <mailto:pcn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Nov 2010 07:28:05 -0000

This is a multi-part message in MIME format.
--------------010501040302040105020204
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit

Hi Bob,

congratulations to this RFC and thanks a lot for all your work! This 
clarification and streamlining is important for the extensibility of the 
Internet, and in particular for PCN of course.

Best wishes,

     Michael

-------- Original-Nachricht --------
Betreff: 	RFC 6040 on Tunnelling of Explicit Congestion Notification
Datum: 	Mon, 29 Nov 2010 22:27:37 -0800 (PST)
Von: 	rfc-editor@rfc-editor.org
An: 	ietf-announce@ietf.org, rfc-dist@rfc-editor.org
CC: 	tsvwg@ietf.org, rfc-editor@rfc-editor.org



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


         RFC 6040

         Title:      Tunnelling of Explicit Congestion Notification
         Author:     B. Briscoe
         Status:     Standards Track
         Stream:     IETF
         Date:       November 2010
         Mailbox:    bob.briscoe@bt.com
         Pages:      35
         Characters: 89412
         Updates:    RFC3168, RFC4301, RFC4774

         I-D Tag:    draft-ietf-tsvwg-ecn-tunnel-10.txt

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

This document redefines how the explicit congestion notification
(ECN) field of the IP header should be constructed on entry to and
exit from any IP-in-IP tunnel.  On encapsulation, it updates RFC 3168
to bring all IP-in-IP tunnels (v4 or v6) into line with RFC 4301
IPsec ECN processing.  On decapsulation, it updates both RFC 3168 and
RFC 4301 to add new behaviours for previously unused combinations of
inner and outer headers.  The new rules ensure the ECN field is
correctly propagated across a tunnel whether it is used to signal one
or two severity levels of congestion; whereas before, only one
severity level was supported.  Tunnel endpoints can be updated in any
order without affecting pre-existing uses of the ECN field, thus
ensuring backward compatibility.  Nonetheless, operators wanting to
support two severity levels (e.g., for pre-congestion notification --
PCN) can require compliance with this new specification.  A thorough
analysis of the reasoning for these changes and the implications is
included.  In the unlikely event that the new rules do not meet a
specific need, RFC 4774 gives guidance on designing alternate ECN
semantics, and this document extends that to include tunnelling
issues.  [STANDARDS-TRACK]

This document is a product of the Transport Area Working Group Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
   http://www.ietf.org/mailman/listinfo/ietf-announce
   http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


--------------010501040302040105020204
Content-Type: text/html; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>

    <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DISO=
-8859-15">
  </head>
  <body text=3D"#000000" bgcolor=3D"#ffffff">
    Hi Bob,<br>
    <br>
    congratulations to this RFC and thanks a lot for all your work! This
    clarification and streamlining is important for the extensibility of
    the Internet, and in particular for PCN of course. <br>
    <br>
    Best wishes,<br>
    <br>
    =A0=A0=A0 Michael<br>
    <br>
    -------- Original-Nachricht --------
    <table class=3D"moz-email-headers-table" border=3D"0" cellpadding=3D"=
0"
      cellspacing=3D"0">
      <tbody>
        <tr>
          <th valign=3D"BASELINE" align=3D"RIGHT" nowrap=3D"nowrap">Betre=
ff: </th>
          <td>RFC 6040 on Tunnelling of Explicit Congestion Notification<=
/td>
        </tr>
        <tr>
          <th valign=3D"BASELINE" align=3D"RIGHT" nowrap=3D"nowrap">Datum=
: </th>
          <td>Mon, 29 Nov 2010 22:27:37 -0800 (PST)</td>
        </tr>
        <tr>
          <th valign=3D"BASELINE" align=3D"RIGHT" nowrap=3D"nowrap">Von: =
</th>
          <td><a class=3D"moz-txt-link-abbreviated" href=3D"mailto:rfc-ed=
itor@rfc-editor.org">rfc-editor@rfc-editor.org</a></td>
        </tr>
        <tr>
          <th valign=3D"BASELINE" align=3D"RIGHT" nowrap=3D"nowrap">An: <=
/th>
          <td><a class=3D"moz-txt-link-abbreviated" href=3D"mailto:ietf-a=
nnounce@ietf.org">ietf-announce@ietf.org</a>, <a class=3D"moz-txt-link-ab=
breviated" href=3D"mailto:rfc-dist@rfc-editor.org">rfc-dist@rfc-editor.or=
g</a></td>
        </tr>
        <tr>
          <th valign=3D"BASELINE" align=3D"RIGHT" nowrap=3D"nowrap">CC: <=
/th>
          <td><a class=3D"moz-txt-link-abbreviated" href=3D"mailto:tsvwg@=
ietf.org">tsvwg@ietf.org</a>, <a class=3D"moz-txt-link-abbreviated" href=3D=
"mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a></td>
        </tr>
      </tbody>
    </table>
    <br>
    <br>
    <pre>A new Request for Comments is now available in online RFC librar=
ies.

       =20
        RFC 6040

        Title:      Tunnelling of Explicit Congestion Notification=20
        Author:     B. Briscoe
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2010
        Mailbox:    <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:=
bob.briscoe@bt.com">bob.briscoe@bt.com</a>
        Pages:      35
        Characters: 89412
        Updates:    RFC3168, RFC4301, RFC4774

        I-D Tag:    draft-ietf-tsvwg-ecn-tunnel-10.txt

        URL:        <a class=3D"moz-txt-link-freetext" href=3D"http://www=
.rfc-editor.org/rfc/rfc6040.txt">http://www.rfc-editor.org/rfc/rfc6040.tx=
t</a>

This document redefines how the explicit congestion notification
(ECN) field of the IP header should be constructed on entry to and
exit from any IP-in-IP tunnel.  On encapsulation, it updates RFC 3168
to bring all IP-in-IP tunnels (v4 or v6) into line with RFC 4301
IPsec ECN processing.  On decapsulation, it updates both RFC 3168 and
RFC 4301 to add new behaviours for previously unused combinations of
inner and outer headers.  The new rules ensure the ECN field is
correctly propagated across a tunnel whether it is used to signal one
or two severity levels of congestion; whereas before, only one
severity level was supported.  Tunnel endpoints can be updated in any
order without affecting pre-existing uses of the ECN field, thus
ensuring backward compatibility.  Nonetheless, operators wanting to
support two severity levels (e.g., for pre-congestion notification --
PCN) can require compliance with this new specification.  A thorough
analysis of the reasoning for these changes and the implications is
included.  In the unlikely event that the new rules do not meet a
specific need, RFC 4774 gives guidance on designing alternate ECN
semantics, and this document extends that to include tunnelling
issues.  [STANDARDS-TRACK]

This document is a product of the Transport Area Working Group Working Gr=
oup of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestio=
ns
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  <a class=3D"moz-txt-link-freetext" href=3D"http://www.ietf.org/mailman/=
listinfo/ietf-announce">http://www.ietf.org/mailman/listinfo/ietf-announc=
e</a>
  <a class=3D"moz-txt-link-freetext" href=3D"http://mailman.rfc-editor.or=
g/mailman/listinfo/rfc-dist">http://mailman.rfc-editor.org/mailman/listin=
fo/rfc-dist</a>

For searching the RFC series, see <a class=3D"moz-txt-link-freetext" href=
=3D"http://www.rfc-editor.org/rfcsearch.html">http://www.rfc-editor.org/r=
fcsearch.html</a>.
For downloading RFCs, see <a class=3D"moz-txt-link-freetext" href=3D"http=
://www.rfc-editor.org/rfc.html">http://www.rfc-editor.org/rfc.html</a>.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to <a class=3D"moz-txt-link-abbreviated=
" href=3D"mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>=
.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC
</pre>
  </body>
</html>

--------------010501040302040105020204--
