From nobody Thu Mar 6 10:38:20 2014 Return-Path: X-Original-To: conex@ietfa.amsl.com Delivered-To: conex@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C8361A0192; Thu, 6 Mar 2014 10:38:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 VLFJZMplygky; Thu, 6 Mar 2014 10:38:14 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 53D111A0265; Thu, 6 Mar 2014 10:38:11 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.1.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140306183811.8025.62241.idtracker@ietfa.amsl.com> Date: Thu, 06 Mar 2014 10:38:11 -0800 Archived-At: http://mailarchive.ietf.org/arch/msg/conex/rB3Tf3kgy-GVQTz2RV0JcTe1CgI Cc: conex@ietf.org Subject: [conex] I-D Action: draft-ietf-conex-abstract-mech-10.txt X-BeenThere: conex@ietf.org X-Mailman-Version: 2.1.15 List-Id: Congestion Exposure working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Mar 2014 18:38:15 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Congestion Exposure Working Group of the IETF. Title : Congestion Exposure (ConEx) Concepts and Abstract Mechanism Authors : Matt Mathis Bob Briscoe Filename : draft-ietf-conex-abstract-mech-10.txt Pages : 28 Date : 2014-03-06 Abstract: This document describes an abstract mechanism by which senders inform the network about the congestion encountered by packets earlier in the same flow. Today, network elements at any layer may signal congestion to the receiver by dropping packets or by ECN markings, and the receiver passes this information back to the sender in transport-layer feedback. The mechanism described here enables the sender to also relay this congestion information back into the network in-band at the IP layer, such that the total amount of congestion from all elements on the path is revealed to all IP elements along the path, where it could, for example, be used to provide input to traffic management. This mechanism is called congestion exposure or ConEx. The companion document "ConEx Concepts and Use Cases" provides the entry-point to the set of ConEx documentation. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-conex-abstract-mech/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-conex-abstract-mech-10 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-conex-abstract-mech-10 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Thu Mar 13 14:32:02 2014 Return-Path: X-Original-To: conex@ietfa.amsl.com Delivered-To: conex@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 207331A0A10; Thu, 13 Mar 2014 14:31:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 0HtoTXN6bivp; Thu, 13 Mar 2014 14:31:55 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B63941A0A55; Thu, 13 Mar 2014 14:31:54 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.1.0p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140313213154.13957.16849.idtracker@ietfa.amsl.com> Date: Thu, 13 Mar 2014 14:31:54 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/conex/vTn0PSeT1upNTya4njPZVAwaJsc Cc: conex@ietf.org Subject: [conex] I-D Action: draft-ietf-conex-abstract-mech-11.txt X-BeenThere: conex@ietf.org X-Mailman-Version: 2.1.15 List-Id: Congestion Exposure working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Mar 2014 21:31:57 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Congestion Exposure Working Group of the IETF. Title : Congestion Exposure (ConEx) Concepts and Abstract Mechanism Authors : Matt Mathis Bob Briscoe Filename : draft-ietf-conex-abstract-mech-11.txt Pages : 29 Date : 2014-03-13 Abstract: This document describes an abstract mechanism by which senders inform the network about the congestion encountered by packets earlier in the same flow. Today, network elements at any layer may signal congestion to the receiver by dropping packets or by ECN markings, and the receiver passes this information back to the sender in transport-layer feedback. The mechanism described here enables the sender to also relay this congestion information back into the network in-band at the IP layer, such that the total amount of congestion from all elements on the path is revealed to all IP elements along the path, where it could, for example, be used to provide input to traffic management. This mechanism is called congestion exposure or ConEx. The companion document "ConEx Concepts and Use Cases" provides the entry-point to the set of ConEx documentation. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-conex-abstract-mech/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-conex-abstract-mech-11 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-conex-abstract-mech-11 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Thu Mar 13 23:55:05 2014 Return-Path: X-Original-To: conex@ietfa.amsl.com Delivered-To: conex@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F39EF1A0059 for ; Thu, 13 Mar 2014 23:55:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.748 X-Spam-Level: X-Spam-Status: No, score=-104.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547, 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 oFmzRRJMoTyF for ; Thu, 13 Mar 2014 23:55:00 -0700 (PDT) Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133]) by ietfa.amsl.com (Postfix) with ESMTP id E6A631A0062 for ; Thu, 13 Mar 2014 23:54:59 -0700 (PDT) Received: from smtp03.uc3m.es (localhost [127.0.0.1]) by localhost.uc3m.es (Postfix) with ESMTP id 38B17118484E for ; Fri, 14 Mar 2014 07:54:52 +0100 (CET) X-uc3m-safe: yes Received: from [163.117.203.211] (unknown [163.117.203.211]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: marcelo@smtp03.uc3m.es) by smtp03.uc3m.es (Postfix) with ESMTPSA id 05C921183EDC for ; Fri, 14 Mar 2014 07:54:51 +0100 (CET) Message-ID: <5322A7BC.4000602@it.uc3m.es> Date: Fri, 14 Mar 2014 07:54:52 +0100 From: marcelo bagnulo braun User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: 'ConEx IETF list' References: <20140313213154.13957.16849.idtracker@ietfa.amsl.com> In-Reply-To: <20140313213154.13957.16849.idtracker@ietfa.amsl.com> X-Forwarded-Message-Id: <20140313213154.13957.16849.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelistedACL 131 matched, not delayed by milter-greylist-4.2.7 (smtp03.uc3m.es); Fri, 14 Mar 2014 07:54:52 +0100 (CET) X-TM-AS-Product-Ver: IMSS-7.1.0.1224-7.5.0.1017-20564.004 X-TM-AS-Result: No--17.642-7.0-31-1 X-imss-scan-details: No--17.642-7.0-31-1 Archived-At: http://mailarchive.ietf.org/arch/msg/conex/n0iEe5cACQeUfm3W798wz77rAyU Subject: [conex] Fwd: I-D Action: draft-ietf-conex-abstract-mech-11.txt X-BeenThere: conex@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Congestion Exposure working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Mar 2014 06:55:04 -0000 Hi, The plan is to send this last version to the IESG next week. Regards, marcelo -------- Mensaje original -------- Asunto: I-D Action: draft-ietf-conex-abstract-mech-11.txt Fecha: Thu, 13 Mar 2014 14:31:54 -0700 De: internet-drafts@ietf.org Responder a: internet-drafts@ietf.org Para: i-d-announce@ietf.org CC: conex@ietf.org A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Congestion Exposure Working Group of the IETF. Title : Congestion Exposure (ConEx) Concepts and Abstract Mechanism Authors : Matt Mathis Bob Briscoe Filename : draft-ietf-conex-abstract-mech-11.txt Pages : 29 Date : 2014-03-13 Abstract: This document describes an abstract mechanism by which senders inform the network about the congestion encountered by packets earlier in the same flow. Today, network elements at any layer may signal congestion to the receiver by dropping packets or by ECN markings, and the receiver passes this information back to the sender in transport-layer feedback. The mechanism described here enables the sender to also relay this congestion information back into the network in-band at the IP layer, such that the total amount of congestion from all elements on the path is revealed to all IP elements along the path, where it could, for example, be used to provide input to traffic management. This mechanism is called congestion exposure or ConEx. The companion document "ConEx Concepts and Use Cases" provides the entry-point to the set of ConEx documentation. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-conex-abstract-mech/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-conex-abstract-mech-11 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-conex-abstract-mech-11 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt From nobody Wed Mar 19 02:46:42 2014 Return-Path: X-Original-To: conex@ietfa.amsl.com Delivered-To: conex@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1F4A1A069A for ; Wed, 19 Mar 2014 02:46:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.147 X-Spam-Level: X-Spam-Status: No, score=-3.147 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] 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 mqGpiz3R6pPf for ; Wed, 19 Mar 2014 02:46:33 -0700 (PDT) Received: from hubrelay-rd.bt.com (hubrelay-rd.bt.com [62.239.224.99]) by ietfa.amsl.com (Postfix) with ESMTP id D832F1A06A9 for ; Wed, 19 Mar 2014 02:46:32 -0700 (PDT) Received: from EVMHR71-UKRD.domain1.systemhost.net (10.36.3.109) by EVMHR67-UKRD.bt.com (10.187.101.22) with Microsoft SMTP Server (TLS) id 8.3.297.1; Wed, 19 Mar 2014 09:46:23 +0000 Received: from EPHR01-UKIP.domain1.systemhost.net (147.149.196.177) by EVMHR71-UKRD.domain1.systemhost.net (10.36.3.109) with Microsoft SMTP Server (TLS) id 8.3.279.1; Wed, 19 Mar 2014 09:46:21 +0000 Received: from bagheera.jungle.bt.co.uk (132.146.168.158) by EPHR01-UKIP.domain1.systemhost.net (147.149.196.177) with Microsoft SMTP Server id 14.2.347.0; Wed, 19 Mar 2014 09:46:16 +0000 Received: from BTP075694.jungle.bt.co.uk ([10.109.159.220]) by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id s2J9kE0x010476; Wed, 19 Mar 2014 09:46:14 GMT Message-ID: <201403190946.s2J9kE0x010476@bagheera.jungle.bt.co.uk> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 19 Mar 2014 09:46:14 +0000 To: marcelo bagnulo braun From: Bob Briscoe In-Reply-To: References: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_50083949==.ALT" X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158 Archived-At: http://mailarchive.ietf.org/arch/msg/conex/9i_uJVaZod-PD781keoirH4fF8U Cc: ConEx IETF list Subject: [conex] Remaining ConEx I-Ds X-BeenThere: conex@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Congestion Exposure working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Mar 2014 09:46:40 -0000 --=====================_50083949==.ALT Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Marcelo, At 21:39 13/03/2014, Matt Mathis wrote: >I am concerned that there are too many=20 >non-progressing IDs as references. =C2 These are=20 >not so much of an issue at this stage, but we=20 >need a plan for the RFC editor: which are we=20 >going to leave at "work in progress" and which=20 >can be replaced by other references? [Matt, actually, all except the "historic" re-ECN=20 ones have had recent material updates.] What's the plan for each category below in the=20 timescale of RFC-Edits on abstract-mech? 1) Ready: presumably you will WG last-call the=20 ConEx ones? Or has that already happened? 2) "Historic" (re-ECN): Do we leave these to=20 expire, or get them issued as historic RFCs? 3) Individual: Do you plan to make these WG items? (Small groups are actively working on=20 implementing and evaluating policing and audit.) I count the following I-D refs in abstract-mech: 1) Ready for WG last call (either ConEx or TCPM): * ietf-conex-destopt * ietf-tcp-modifications * ietf-tcpm-accecn-reqs 2) "Historic" re-ECN drafts * briscoe-conex-re-ecn-motiv * briscoe-conex-re-ecn-tcp 3) Individual drafts satisfying ConEx charter items: * briscoe-conex-policing * draft-wagner-conex-audit (mistakenly not=20 referenced from abstract-mech, but we'll add during RFC-Editor phase) The other category in the charter (cited in=20 concepts-uses, not abstract-mech) is 4) Use cases draft-ietf-conex-mobile draft-briscoe-conex-data-centre draft-briscoe-conex-initial-deploy Bob >Thanks, >--MM-- >The best way to predict the future is to create it. =C2 - Alan Kay > >Privacy matters! =C2 We know from recent events=20 >that people are using our services to speak in=20 >defiance of unjust governments. =C2 We treat=20 >privacy and security as matters of life and=20 >death, because for some users, they are. > > >---------- Forwarded message ---------- >From: <internet-drafts@ietf.org> >Date: Thu, Mar 13, 2014 at 2:31 PM >Subject: New Version Notification for draft-ietf-conex-abstract-mech-11.txt >To: Matt Mathis=20 ><mattmathis@google.com>,=20 >"Bob J. Briscoe" <bob.briscoe@bt.com> > > > >A new version of I-D, draft-ietf-conex-abstract-mech-11.txt >has been successfully submitted by Matt Mathis and posted to the >IETF repository. > >Name: =C2 =C2 =C2 =C2 =C2 draft-ietf-conex-abstract-mech >Revision: =C2 =C2 =C2 11 >Title: =C2 =C2 =C2 =C2 =C2 Congestion Exposure (ConEx)=20 >Concepts and Abstract Mechanism >Document date: =C2 2014-03-13 >Group: =C2 =C2 =C2 =C2 =C2 conex >Pages: =C2 =C2 =C2 =C2 =C2 29 >URL: =C2 =C2 =C2 =C2 =C2 =C2=20 >= http://www.ietf.org/internet-drafts/draft-ietf-conex-abstract-mech-11.txt >Status:=20 >=C2 =C2 =C2 =C2=20 >https://d= atatracker.ietf.org/doc/draft-ietf-conex-abstract-mech/ >Htmlized:=20 >=C2 =C2 =C2=20 >http://tools.= ietf.org/html/draft-ietf-conex-abstract-mech-11 >Diff:=20 >=C2 =C2 =C2 =C2 =C2=20 >http:= //www.ietf.org/rfcdiff?url2=3Ddraft-ietf-conex-abstract-mech-11 > >Abstract: >=C2 =C2 This document describes an abstract mechanism by which senders= inform >=C2 =C2 the network about the congestion encountered by packets earlier in >=C2 =C2 the same flow. =C2 Today, network elements at any layer may signal >=C2 =C2 congestion to the receiver by dropping packets or by ECN markings, >=C2 =C2 and the receiver passes this information back to the sender in >=C2 =C2 transport-layer feedback. =C2 The mechanism described here enables= the >=C2 =C2 sender to also relay this congestion information back into the >=C2 =C2 network in-band at the IP layer, such that the total amount of >=C2 =C2 congestion from all elements on the path is revealed to all IP >=C2 =C2 elements along the path, where it could, for example, be used to >=C2 =C2 provide input to traffic management. =C2 This mechanism is called >=C2 =C2 congestion exposure or ConEx. =C2 The companion document "ConEx= Concepts >=C2 =C2 and Use Cases" provides the entry-point to the set of ConEx >=C2 =C2 documentation. > > > > >Please note that it may take a couple of minutes from the time of= submission >until the htmlized version and diff are=20 >available at tools.ietf.org. > >The IETF Secretariat > ________________________________________________________________ Bob Briscoe, BT=20 --=====================_50083949==.ALT Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Marcelo,

At 21:39 13/03/2014, Matt Mathis wrote:
I am concerned that there are too many non-progressing IDs as references. =C2  These are not so much of an issue at this stage, but we need a plan for the RFC editor: which are we going to leave at "work in progress" and which can be replaced by other references?

[Matt, actually, all except the "historic" re-ECN ones have had recent material updates.]

What's the plan for each category below in the timescale of RFC-Edits on abstract-mech?
1) Ready: presumably you will WG last-call the ConEx ones? Or has that already happened?
2) "Historic" (re-ECN): Do we leave these to expire, or get them issued as historic RFCs?
3) Individual: Do you plan to make these WG items?
   (Small groups are actively working on implementing and evaluating policing and audit.)


I count the following I-D refs in abstract-mech:

1) Ready for WG last call (either ConEx or TCPM):
* ietf-conex-destopt
* ietf-tcp-modifications
* ietf-tcpm-accecn-reqs

2) "Historic" re-ECN drafts
* briscoe-conex-re-ecn-motiv
* briscoe-conex-re-ecn-tcp

3) Individual drafts satisfying ConEx charter items:
* briscoe-conex-policing
* draft-wagner-conex-audit (mistakenly not referenced from abstract-mech, but we'll add during RFC-Editor phase)

The other category in the charter (cited in concepts-uses, not abstract-mech) is
4) Use cases
         draft-ietf-conex-mobile
         draft-briscoe-conex-data-centre
         draft-briscoe-conex-initial-deploy



Bob




Thanks,
--MM--
The best way to predict the future is to create it. =C2 - Alan Kay

Privacy matters! =C2 We know from recent events that people are using our services to speak in defiance of unjust governments. =C2  We treat privacy and security as matters of life and death, because for some users, they are.


---------- Forwarded message ----------
From: <internet-drafts@ietf.org >
Date: Thu, Mar 13, 2014 at 2:31 PM
Subject: New Version Notification for draft-ietf-conex-abstract-mech-11.txt
To: Matt Mathis <mattmathis@google.com>, "Bob J. Briscoe" <bob.briscoe@bt.com>



A new version of I-D, draft-ietf-conex-abstract-mech-11.txt
has been successfully submitted by Matt Mathis and posted to the
IETF repository.

Name: =C2  =C2  =C2  =C2  =C2  draft-ietf-conex-abstract-mech
Revision: =C2  =C2  =C2  11
Title: =C2  =C2  =C2  =C2  =C2 Congestion Exposure (ConE= x) Concepts and Abstract Mechanism
Document date: =C2 2014-03-13
Group: =C2  =C2  =C2  =C2  =C2 conex
Pages: =C2  =C2  =C2  =C2  =C2 29
URL: =C2  =C2  =C2  =C2  =C2  =C2 http://www.ietf.org/internet-drafts/draft-ietf-conex-abstract-mech-11.txt
Status: =C2  =C2  =C2  =C2  https://datatracker.ietf.org/doc/draft-ietf-conex-abstract-mech/
Htmlized: =C2  =C2  =C2  http://tools.ietf.org/html/draft-ietf-conex-abstract-mech-11
Diff: =C2  =C2  =C2  =C2  =C2  http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-conex-abstract-mech-11

Abstract:
=C2  =C2 This document describes an abstract mechanism by which senders inform
=C2  =C2 the network about the congestion encountered by packets earlie= r in
=C2  =C2 the same flow. =C2 Today, network elements at any layer may signal
=C2  =C2 congestion to the receiver by dropping packets or by ECN markings,
=C2  =C2 and the receiver passes this information back to the sender in
=C2  =C2 transport-layer feedback. =C2 The mechanism described here enables the
=C2  =C2 sender to also relay this congestion information back into the
=C2  =C2 network in-band at the IP layer, such that the total amount of
=C2  =C2 congestion from all elements on the path is revealed to all IP
=C2  =C2 elements along the path, where it could, for example, be used to
=C2  =C2 provide input to traffic management. =C2 This mechanism is called
=C2  =C2 congestion exposure or ConEx. =C2 The companion document "ConEx Concepts
=C2  =C2 and Use Cases" provides the entry-point to the set of ConEx
=C2  =C2 documentation.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

________________________________________________________________
Bob Briscoe,           &n= bsp;            =             &nbs= p;             BT --=====================_50083949==.ALT-- From nobody Wed Mar 19 02:51:20 2014 Return-Path: X-Original-To: conex@ietfa.amsl.com Delivered-To: conex@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 860BE1A06AF for ; Wed, 19 Mar 2014 02:51:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.748 X-Spam-Level: X-Spam-Status: No, score=-104.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547, 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 PRp4ASDlSW57 for ; Wed, 19 Mar 2014 02:51:11 -0700 (PDT) Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131]) by ietfa.amsl.com (Postfix) with ESMTP id 934121A069A for ; Wed, 19 Mar 2014 02:51:11 -0700 (PDT) Received: from smtp01.uc3m.es (localhost [127.0.0.1]) by localhost.uc3m.es (Postfix) with ESMTP id 4E91ACC5C92; Wed, 19 Mar 2014 10:51:02 +0100 (CET) X-uc3m-safe: yes Received: from dummyhost17.it.uc3m.es (dummyhost0.it.uc3m.es [163.117.139.74]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: marcelo@smtp01.uc3m.es) by smtp01.uc3m.es (Postfix) with ESMTPSA id 3EA4CC3534D; Wed, 19 Mar 2014 10:51:02 +0100 (CET) Message-ID: <53296885.1070309@it.uc3m.es> Date: Wed, 19 Mar 2014 10:51:01 +0100 From: marcelo bagnulo braun User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Bob Briscoe References: <201403190946.s2J9kE0x010476@bagheera.jungle.bt.co.uk> In-Reply-To: <201403190946.s2J9kE0x010476@bagheera.jungle.bt.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelistedACL 138 matched, not delayed by milter-greylist-4.2.7 (smtp01.uc3m.es); Wed, 19 Mar 2014 10:51:02 +0100 (CET) X-TM-AS-Product-Ver: IMSS-7.1.0.1224-7.5.0.1017-20574.006 Archived-At: http://mailarchive.ietf.org/arch/msg/conex/fRbgH9QER2vmgvFEuZrdbKsFVdM Cc: ConEx IETF list Subject: Re: [conex] Remaining ConEx I-Ds X-BeenThere: conex@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Congestion Exposure working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Mar 2014 09:51:16 -0000 Hi, I can only speak about the conex ones, the tcp one and the dst options one, i will issue a wglc shortly. the other ones, i can ask for expression of interest in working in the documents and see how much energy we have left. Regards, marcelo El 19/03/14 10:46, Bob Briscoe escribió: > Marcelo, > > At 21:39 13/03/2014, Matt Mathis wrote: >> I am concerned that there are too many non-progressing IDs as >> references. Â These are not so much of an issue at this stage, but >> we need a plan for the RFC editor: which are we going to leave at >> "work in progress" and which can be replaced by other references? > > [Matt, actually, all except the "historic" re-ECN ones have had recent > material updates.] > > What's the plan for each category below in the timescale of RFC-Edits > on abstract-mech? > 1) Ready: presumably you will WG last-call the ConEx ones? Or has that > already happened? > 2) "Historic" (re-ECN): Do we leave these to expire, or get them > issued as historic RFCs? > 3) Individual: Do you plan to make these WG items? > (Small groups are actively working on implementing and evaluating > policing and audit.) > > > I count the following I-D refs in abstract-mech: > > 1) Ready for WG last call (either ConEx or TCPM): > * ietf-conex-destopt > * ietf-tcp-modifications > * ietf-tcpm-accecn-reqs > > 2) "Historic" re-ECN drafts > * briscoe-conex-re-ecn-motiv > * briscoe-conex-re-ecn-tcp > > 3) Individual drafts satisfying ConEx charter items: > * briscoe-conex-policing > * draft-wagner-conex-audit (mistakenly not referenced from > abstract-mech, but we'll add during RFC-Editor phase) > > The other category in the charter (cited in concepts-uses, not > abstract-mech) is > 4) Use cases > draft-ietf-conex-mobile > draft-briscoe-conex-data-centre > draft-briscoe-conex-initial-deploy > > > > Bob > > > > >> Thanks, >> --MM-- >> The best way to predict the future is to create it. Â - Alan Kay >> >> Privacy matters! Â We know from recent events that people are using >> our services to speak in defiance of unjust governments. Â We treat >> privacy and security as matters of life and death, because for some >> users, they are. >> >> >> ---------- Forwarded message ---------- >> From: > >> Date: Thu, Mar 13, 2014 at 2:31 PM >> Subject: New Version Notification for >> draft-ietf-conex-abstract-mech-11.txt >> To: Matt Mathis > >, "Bob J. Briscoe" > > >> >> >> >> A new version of I-D, draft-ietf-conex-abstract-mech-11.txt >> has been successfully submitted by Matt Mathis and posted to the >> IETF repository. >> >> Name: Â Â Â Â Â draft-ietf-conex-abstract-mech >> Revision: Â Â Â 11 >> Title: Â Â Â Â Â Congestion Exposure (ConEx) Concepts and >> Abstract Mechanism >> Document date: Â 2014-03-13 >> Group: Â Â Â Â Â conex >> Pages: Â Â Â Â Â 29 >> URL: Â Â Â Â Â Â >> http://www.ietf.org/internet-drafts/draft-ietf-conex-abstract-mech-11.txt >> >> Status: Â Â Â Â >> https://datatracker.ietf.org/doc/draft-ietf-conex-abstract-mech/ >> Htmlized: Â Â Â >> http://tools.ietf.org/html/draft-ietf-conex-abstract-mech-11 >> >> Diff: Â Â Â Â Â >> http://www.ietf.org/rfcdiff?url2=draft-ietf-conex-abstract-mech-11 >> >> Abstract: >> Â Â This document describes an abstract mechanism by which senders >> inform >> Â Â the network about the congestion encountered by packets earlier in >> Â Â the same flow. Â Today, network elements at any layer may signal >> Â Â congestion to the receiver by dropping packets or by ECN markings, >> Â Â and the receiver passes this information back to the sender in >> Â Â transport-layer feedback. Â The mechanism described here enables the >> Â Â sender to also relay this congestion information back into the >> Â Â network in-band at the IP layer, such that the total amount of >> Â Â congestion from all elements on the path is revealed to all IP >> Â Â elements along the path, where it could, for example, be used to >> Â Â provide input to traffic management. Â This mechanism is called >> Â Â congestion exposure or ConEx. Â The companion document "ConEx >> Concepts >> Â Â and Use Cases" provides the entry-point to the set of ConEx >> Â Â documentation. >> >> >> >> >> Please note that it may take a couple of minutes from the time of >> submission >> until the htmlized version and diff are available at tools.ietf.org >> . >> >> The IETF Secretariat >> > ________________________________________________________________ > Bob Briscoe, BT > From nobody Wed Mar 19 09:40:56 2014 Return-Path: X-Original-To: conex@ietfa.amsl.com Delivered-To: conex@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01A691A07D6 for ; Wed, 19 Mar 2014 09:40:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.149 X-Spam-Level: X-Spam-Status: No, score=-3.149 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.547, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 UcOvrBlyIDtw for ; Wed, 19 Mar 2014 09:40:49 -0700 (PDT) Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 139691A0412 for ; Wed, 19 Mar 2014 09:40:49 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 9DA30FF844; Wed, 19 Mar 2014 17:40:39 +0100 (CET) X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de) Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JiMeDq9d9ufm; Wed, 19 Mar 2014 17:40:39 +0100 (CET) X-ENC: Last-Hop-TLS-encrypted X-ENC: Last-Hop-TLS-encrypted Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailer1.neclab.eu (Postfix) with ESMTPS id 79C9F107098; Wed, 19 Mar 2014 17:40:24 +0100 (CET) Received: from HYDRA.office.hd ([169.254.4.196]) by ENCELADUS.office.hd ([192.168.24.52]) with mapi id 14.01.0323.003; Wed, 19 Mar 2014 17:40:04 +0100 From: Dirk Kutscher To: marcelo bagnulo braun , Bob Briscoe Thread-Topic: [conex] Remaining ConEx I-Ds Thread-Index: AQHPQ1gofUZAsz80/kOMiXYytFEWjJroGgSAgACCnhA= Date: Wed, 19 Mar 2014 16:40:02 +0000 Message-ID: <82AB329A76E2484D934BBCA77E9F5249639FFD5D@Hydra.office.hd> References: <201403190946.s2J9kE0x010476@bagheera.jungle.bt.co.uk> <53296885.1070309@it.uc3m.es> In-Reply-To: <53296885.1070309@it.uc3m.es> Accept-Language: de-DE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.1.2.204] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/conex/uUGU7FEVVhGDsDE8uQUJBVxqyvY Cc: ConEx IETF list Subject: Re: [conex] Remaining ConEx I-Ds X-BeenThere: conex@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Congestion Exposure working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Mar 2014 16:40:53 -0000 Hi, conex-mobile has been rev'ed recently -- we have a plan for another update = before we would ask for WGLC. Dirk > -----Original Message----- > From: conex [mailto:conex-bounces@ietf.org] On Behalf Of marcelo bagnulo > braun > Sent: Mittwoch, 19. M=E4rz 2014 10:51 > To: Bob Briscoe > Cc: ConEx IETF list > Subject: Re: [conex] Remaining ConEx I-Ds >=20 > Hi, >=20 > I can only speak about the conex ones, the tcp one and the dst options on= e, i > will issue a wglc shortly. > the other ones, i can ask for expression of interest in working in the > documents and see how much energy we have left. >=20 > Regards, marcelo >=20 >=20 >=20 > El 19/03/14 10:46, Bob Briscoe escribi=F3: > > Marcelo, > > > > At 21:39 13/03/2014, Matt Mathis wrote: > >> I am concerned that there are too many non-progressing IDs as > >> references. =C2 These are not so much of an issue at this stage, but > >> we need a plan for the RFC editor: which are we going to leave at > >> "work in progress" and which can be replaced by other references? > > > > [Matt, actually, all except the "historic" re-ECN ones have had recent > > material updates.] > > > > What's the plan for each category below in the timescale of RFC-Edits > > on abstract-mech? > > 1) Ready: presumably you will WG last-call the ConEx ones? Or has that > > already happened? > > 2) "Historic" (re-ECN): Do we leave these to expire, or get them > > issued as historic RFCs? > > 3) Individual: Do you plan to make these WG items? > > (Small groups are actively working on implementing and evaluating > > policing and audit.) > > > > > > I count the following I-D refs in abstract-mech: > > > > 1) Ready for WG last call (either ConEx or TCPM): > > * ietf-conex-destopt > > * ietf-tcp-modifications > > * ietf-tcpm-accecn-reqs > > > > 2) "Historic" re-ECN drafts > > * briscoe-conex-re-ecn-motiv > > * briscoe-conex-re-ecn-tcp > > > > 3) Individual drafts satisfying ConEx charter items: > > * briscoe-conex-policing > > * draft-wagner-conex-audit (mistakenly not referenced from > > abstract-mech, but we'll add during RFC-Editor phase) > > > > The other category in the charter (cited in concepts-uses, not > > abstract-mech) is > > 4) Use cases > > draft-ietf-conex-mobile > > draft-briscoe-conex-data-centre > > draft-briscoe-conex-initial-deploy > > > > > > > > Bob > > > > > > > > > >> Thanks, > >> --MM-- > >> The best way to predict the future is to create it. =C2 - Alan Kay > >> > >> Privacy matters! =C2 We know from recent events that people are using > >> our services to speak in defiance of unjust governments. =C2 We treat > >> privacy and security as matters of life and death, because for some > >> users, they are. > >> > >> > >> ---------- Forwarded message ---------- > >> From: > > >> Date: Thu, Mar 13, 2014 at 2:31 PM > >> Subject: New Version Notification for > >> draft-ietf-conex-abstract-mech-11.txt > >> To: Matt Mathis >> >, "Bob J. Briscoe" > >> > > >> > >> > >> > >> A new version of I-D, draft-ietf-conex-abstract-mech-11.txt > >> has been successfully submitted by Matt Mathis and posted to the IETF > >> repository. > >> > >> Name: =C2 =C2 =C2 =C2 =C2 draft-ietf-conex-abstract-mech > >> Revision: =C2 =C2 =C2 11 > >> Title: =C2 =C2 =C2 =C2 =C2 Congestion Exposure (ConEx) Concepts an= d > >> Abstract Mechanism Document date: =C2 2014-03-13 > >> Group: =C2 =C2 =C2 =C2 =C2 conex > >> Pages: =C2 =C2 =C2 =C2 =C2 29 > >> URL: =C2 =C2 =C2 =C2 =C2 =C2 > >> http://www.ietf.org/internet-drafts/draft-ietf-conex-abstract-mech-11 > >> .txt > >> > >> Status: =C2 =C2 =C2 =C2 > >> https://datatracker.ietf.org/doc/draft-ietf-conex-abstract-mech/ > >> Htmlized: =C2 =C2 =C2 > >> http://tools.ietf.org/html/draft-ietf-conex-abstract-mech-11 > >> > >> Diff: =C2 =C2 =C2 =C2 =C2 > >> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-conex-abstract-mech-11 > >> > >> Abstract: > >> =C2 =C2 This document describes an abstract mechanism by which sender= s > >> inform =C2 =C2 the network about the congestion encountered by packet= s > >> earlier in =C2 =C2 the same flow. =C2 Today, network elements at any = layer > >> may signal =C2 =C2 congestion to the receiver by dropping packets or = by > >> ECN markings, =C2 =C2 and the receiver passes this information back t= o > >> the sender in =C2 =C2 transport-layer feedback. =C2 The mechanism > >> described here enables the =C2 =C2 sender to also relay this congesti= on > >> information back into the =C2 =C2 network in-band at the IP layer, su= ch > >> that the total amount of =C2 =C2 congestion from all elements on the > >> path is revealed to all IP =C2 =C2 elements along the path, where it > >> could, for example, be used to =C2 =C2 provide input to traffic > >> management. =C2 This mechanism is called =C2 =C2 congestion exposure = or > >> ConEx. =C2 The companion document "ConEx Concepts =C2 =C2 and Use Cas= es" > >> provides the entry-point to the set of ConEx =C2 =C2 documentation. > >> > >> > >> > >> > >> Please note that it may take a couple of minutes from the time of > >> submission until the htmlized version and diff are available at > >> tools.ietf.org . > >> > >> The IETF Secretariat > >> > > > __________________________________________________________ > ______ > > Bob Briscoe, BT > > >=20 > _______________________________________________ > conex mailing list > conex@ietf.org > https://www.ietf.org/mailman/listinfo/conex From nobody Sun Mar 23 07:58:59 2014 Return-Path: X-Original-To: conex@ietfa.amsl.com Delivered-To: conex@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 806A11A6FC4 for ; Sun, 23 Mar 2014 07:58:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.089 X-Spam-Level: X-Spam-Status: No, score=0.089 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 vqOkksweGFO2 for ; Sun, 23 Mar 2014 07:58:53 -0700 (PDT) Received: from hubrelay-rd.bt.com (hubrelay-rd.bt.com [62.239.224.99]) by ietfa.amsl.com (Postfix) with ESMTP id 7727E1A6FC3 for ; Sun, 23 Mar 2014 07:58:53 -0700 (PDT) Received: from EVMHR02-UKBR.domain1.systemhost.net (193.113.108.41) by EVMHR68-UKRD.bt.com (10.187.101.23) with Microsoft SMTP Server (TLS) id 8.3.279.1; Sun, 23 Mar 2014 14:58:52 +0000 Received: from EPHR01-UKIP.domain1.systemhost.net (147.149.196.177) by EVMHR02-UKBR.domain1.systemhost.net (193.113.108.41) with Microsoft SMTP Server (TLS) id 8.3.297.1; Sun, 23 Mar 2014 14:58:51 +0000 Received: from bagheera.jungle.bt.co.uk (132.146.168.158) by EPHR01-UKIP.domain1.systemhost.net (147.149.196.177) with Microsoft SMTP Server id 14.2.347.0; Sun, 23 Mar 2014 14:58:50 +0000 Received: from BTP075694.jungle.bt.co.uk ([10.109.134.242]) by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id s2NEwmPD031048; Sun, 23 Mar 2014 14:58:48 GMT Message-ID: <201403231458.s2NEwmPD031048@bagheera.jungle.bt.co.uk> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Sun, 23 Mar 2014 14:58:45 +0000 To: marcelo bagnulo braun From: Bob Briscoe In-Reply-To: <5322A7BC.4000602@it.uc3m.es> References: <20140313213154.13957.16849.idtracker@ietfa.amsl.com> <5322A7BC.4000602@it.uc3m.es> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158 Archived-At: http://mailarchive.ietf.org/arch/msg/conex/Mt3eNFAQp24hG5gDf5fSok8tpdI Cc: ConEx IETF list Subject: Re: [conex] Fwd: I-D Action: draft-ietf-conex-abstract-mech-11.txt X-BeenThere: conex@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Congestion Exposure working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Mar 2014 14:58:57 -0000 Marcelo, I noticed I omitted the ack of Trilogy 2 funding. We have draft-11bis ready, which also includes the missing ref to draft-wagner-conex-audit and fixes a couple of typos I noticed. We'd rather you sent draft-12 to the IESG, especially if you haven't yet sent draft-11. Bob At 06:54 14/03/2014, marcelo bagnulo braun wrote: >Hi, > >The plan is to send this last version to the IESG next week. >Regards, marcelo > > > >-------- Mensaje original -------- >Asunto: I-D Action: draft-ietf-conex-abstract-mech-11.txt >Fecha: Thu, 13 Mar 2014 14:31:54 -0700 >De: internet-drafts@ietf.org >Responder a: internet-drafts@ietf.org >Para: i-d-announce@ietf.org >CC: conex@ietf.org > > > >A New Internet-Draft is available from the on-line Internet-Drafts >directories. > This draft is a work item of the Congestion Exposure Working Group > of the IETF. > > Title : Congestion Exposure (ConEx) Concepts and > Abstract Mechanism > Authors : Matt Mathis > Bob Briscoe > Filename : draft-ietf-conex-abstract-mech-11.txt > Pages : 29 > Date : 2014-03-13 > >Abstract: > This document describes an abstract mechanism by which senders inform > the network about the congestion encountered by packets earlier in > the same flow. Today, network elements at any layer may signal > congestion to the receiver by dropping packets or by ECN markings, > and the receiver passes this information back to the sender in > transport-layer feedback. The mechanism described here enables the > sender to also relay this congestion information back into the > network in-band at the IP layer, such that the total amount of > congestion from all elements on the path is revealed to all IP > elements along the path, where it could, for example, be used to > provide input to traffic management. This mechanism is called > congestion exposure or ConEx. The companion document "ConEx Concepts > and Use Cases" provides the entry-point to the set of ConEx > documentation. > > >The IETF datatracker status page for this draft is: >https://datatracker.ietf.org/doc/draft-ietf-conex-abstract-mech/ > >There's also a htmlized version available at: >http://tools.ietf.org/html/draft-ietf-conex-abstract-mech-11 > >A diff from the previous version is available at: >http://www.ietf.org/rfcdiff?url2=draft-ietf-conex-abstract-mech-11 > > >Please note that it may take a couple of minutes from the time of submission >until the htmlized version and diff are available at tools.ietf.org. > >Internet-Drafts are also available by anonymous FTP at: >ftp://ftp.ietf.org/internet-drafts/ > >_______________________________________________ >I-D-Announce mailing list >I-D-Announce@ietf.org >https://www.ietf.org/mailman/listinfo/i-d-announce >Internet-Draft directories: http://www.ietf.org/shadow.html >or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > >_______________________________________________ >conex mailing list >conex@ietf.org >https://www.ietf.org/mailman/listinfo/conex ________________________________________________________________ Bob Briscoe, BT