In Mark Handley's talk on what the IETF should do about DDoS in Int-AREA just now, he mentioned an ad hoc BoF on re-ECN.
The invite and proposed agenda is below. Note, the second hour will be a re-run of the general presentation on what the architectural intent is (from Prague IETF), for those that missed it.
Bob
Date: Tue, 17 Jul 2007 13:38:13 +0100
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Re-ECN meeting in Chicago
Thread-Index: AcfIb1dcZj34MKodRHiY9C/kzgz8ww==
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
X-OriginalArrivalTime: 17 Jul 2007 12:38:03.0374 (UTC)
FILETIME=[5144D8E0:01C7C86F]
X-Spam-Score: 0.131 () HTML_50_60,HTML_MESSAGE
X-Scan-Signature: 33cc095b503da4365ce57c727e553cf1
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: [re-ECN] Re-ECN meeting in Chicago
X-BeenThere: [EMAIL PROTECTED]
X-Mailman-Version: 2.1.5
Reply-To: [EMAIL PROTECTED]
List-Id: re-inserted explicit congestion notification <re-ecn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/re-ecn>,
<mailto:[EMAIL PROTECTED]>
List-Archive: <http://www1.ietf.org/pipermail/re-ecn>
List-Post: <mailto:[EMAIL PROTECTED]>
List-Help: <mailto:[EMAIL PROTECTED]>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/re-ecn>,
<mailto:[EMAIL PROTECTED]>
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C7C86F.50BE3E6A"
All,
There will be another re-ECN unofficial "Bar BoF" happening at IETF69 in Chicago next Wednesday July 25th. It will be at 1300-1500 in the Red Lacquar room. This is a follow on to the meeting held in Prague in March (slides and notes for which can be found at <http://www.cs.ucl.ac.uk/staff/B.Briscoe/projects/refb/#Presentations>)
The aim of the meeting will be to discuss the next steps that need to be taken to move re-ECN forward. The draft agenda is as follows. If anyone would like to add any items please contact me on or off list.
5 mins Administrivia
25 mins presentation and discussion on encoding in IP v4 and v6 (rationale behind current choices,
alternatives, etc)
10 mins How to deploy experimentally (open mic)
10 mins Deployment Scenarios
10 mins Next Steps:
- format of the encoding (in v4, in v6)
- mechanics of the protocol in TCP/IP
- implementation of the dropper and the policer
- extension for use by TCP proxies or other congestion control proxies
- extension for use by other transports
- etc
For those that missed it, we could use the second hour of the session to do a repeat of the presentation given in Prague in March. This was intended to present the architectural intent behind re-ECN as well as explaining how the base protocol works.
All Internet drafts and other documentation relevant to re-ECN can be found at: <http://www.cs.ucl.ac.uk/staff/B.Briscoe/projects/refb/> including draft-briscoe-tsvwg-re-ecn-tcp which describes the protocol and the rationale behind it.
Please could you address any replies to this message to the unofficial IETF mailing list [EMAIL PROTECTED]
Toby Moncaster
____________________________________________________________________________
Toby Moncaster, <[EMAIL PROTECTED]> Networks Research Centre, BT Research
B54/70 Adastral Park, Martlesham Heath, Ipswich, IP53RE, UK. +44 1473 648734
_______________________________________________
re-ECN mailing list
[EMAIL PROTECTED]
https://www1.ietf.org/mailman/listinfo/re-ecn
Bob Briscoe, <[EMAIL PROTECTED]> Networks Research Centre, BT Research
B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK. +44 1473 645196
_______________________________________________ Int-area mailing list [email protected] https://www1.ietf.org/mailman/listinfo/int-area
