From tsvwg-bounces@ietf.org Tue Jul 03 04:46:51 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5e21-0006Mi-Cm; Tue, 03 Jul 2007 04:46:45 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I5e20-0006Lz-Lq
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 03 Jul 2007 04:46:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5e20-0006Ln-Bn; Tue, 03 Jul 2007 04:46:44 -0400
Received: from drew.ipv6.franken.de ([2001:638:a02:a001:20e:cff:fe4a:feaa]
	helo=mail-n.franken.de) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I5e1o-0005GM-8M; Tue, 03 Jul 2007 04:46:44 -0400
Received: from [192.168.1.17] (p508FD6B6.dip.t-dialin.net [80.143.214.182])
	by mail-n.franken.de (Postfix) with ESMTP id 072ED800009B;
	Tue,  3 Jul 2007 10:46:27 +0200 (CEST)
	(KNF-authenticated sender: macmic)
In-Reply-To: <F9824F69-0C5F-4557-B2C4-0173BD99643A@nokia.com>
References: <46828A44.1050804@icann.org>
	<F9824F69-0C5F-4557-B2C4-0173BD99643A@nokia.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <EDB88FD7-B685-466B-8A60-0088072A6CEA@lurchi.franken.de>
Content-Transfer-Encoding: 7bit
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Tsvwg] IANA issue with RFC2960/draft-ietf-tsvwg-2960bis
Date: Tue, 3 Jul 2007 10:46:28 +0200
To: Lars Eggert <lars.eggert@nokia.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 1.8 (+)
X-Scan-Signature: f884eb1d4ec5a230688d7edc526ea665
Cc: tsvwg IETF list <tsvwg@ietf.org>, IESG IESG <iesg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi Lars,

sounds good to me. Just two questions:
1. 2960bis is in the RFC editor queue. How will this change of text  
happen?
2. Do I need to write an ID or RFC to register a port? Or can I just  
contact
    IANA? I'm asking this only for registration of port numbers which  
are
    registered for TCP and/or UDP for a similar service like the discard
    port you use as an example.

Best regards
Michael

On Jun 28, 2007, at 7:53 PM, Lars Eggert wrote:

> Hi,
>
> during a second IANA review of the IANA considerations section in  
> draft-ietf-tsvwg-2960bis during the RFC Editor's "IANA" state, a  
> discrepancy has been identified. Basically, the text that describes  
> the port number assignment procedure - which had been taken  
> verbatim from RFC2960 - wasn't describing the procedure that IANA  
> has actually used since RFC2960 was published seven years ago.
>
> The IANA instructions in draft-ietf-tsvwg-2960bis and RFC2960  
> basically say "for each existing TCP/UDP port assignment, create a  
> similar entry in the SCTP port number registry", i.e., a blanket  
> assignment of SCTP port numbers for all existing TCP/UDP assignments.
>
> What appears to have happened is that the ADs at the time  
> identified an issue with the text that was in the ID that became  
> RFC2960 and instructed IANA to follow a different procedure,  
> namely, to not perform a blanket assignment and instead create  
> individual entries in the SCTP port number registry on request,  
> similar to how IANA handles requests for TCP/UDP and DCCP port  
> numbers. Unfortunately, the text in RFC2960 was never updated to  
> reflect this change in procedure.
>
> When I reviewed 2960bis I didn't question this, because it was what  
> I thought the policy was, and it wasn't for the -bis document to  
> change the policy. Now that we've found out that the IANA  
> procedures in RFC2960 were actually modified by the ADs at the  
> time, the situation has changed.
>
> In my (and Magnus) opinion, we should change the IANA  
> considerations text in 2960bis to describe the allocation policy  
> that has actually been in effect for the last seven years, i.e.,  
> allocate individual SCTP ports by request, instead of the blanket  
> registration that the text currently describes.
>
> I'll propose some text changes to 2960bis to that effect below,  
> which I'd like TSVWG and the IESG to review, but let me first  
> explain why I think this is the correct approach:
>
> 	(1) I find myself agreeing with the old ADs' argumentation.
> 	SCTP and TCP (and UDP) have different requirements, and it
> 	is not obvious that an application can substitute one transport
> 	protocol for another. (And yes, the current practice of allocating
> 	both TCP and UDP ports for an application if it requests either
> 	UDP or TCP only is for that reason also problematic, but let's get
> 	to that another time.)
>
> 	(2) For our other recent transport protocol (DCCP), we also didn't
> 	do a blanket port reservation for all existing TCP and UDP ports
> 	and instead require individual registrations, although one could
> 	similarly argue that UDP apps can simply migrate to DCCP. Doing
> 	something different for SCTP is inconsistent.
>
> 	(3) The scope of 2960bis was clarification and fixes. For that
> 	reason, the IANA registration that is used in practice should
> 	be described as part of 2960bis, i.e., 2960bis should "fix" that
> 	error in RFC2960.
>
> Several applications already use SCTP on port numbers that have  
> been assigned to them for TCP or UDP, because the authors were not  
> aware that they would need to request an allocation from IANA. I  
> propose that the change to the IANA Considerations section in  
> 2960bis register the SCTP ports of those applications, to "bless"  
> those existing uses.
>
> All that said, below is the proposal to update 2960bis. The text  
> mirrors the allocation procedure for DCCP ports (thanks, RFC4340  
> authors!)
>
> Please comment. IANA has agreed to put a hold on the document until  
> this issue has been clarified.
>
> Lars
>
>
> OLD TEXT:
>
> 14.  IANA Considerations
>
>    This protocol will require port reservation like TCP for the use of
>    "well known" servers within the Internet.  All current TCP ports
>    shall be automatically reserved in the SCTP port address space.   
> New
>    requests should follow IANA's current mechanisms for TCP.
>
>    This protocol may also be extended through IANA in three ways:
>
>    --   through definition of additional chunk types,
>    --   through definition of additional parameter types, or
>    --   through definition of additional cause codes within ERROR  
> chunks
>
>    In the case where a particular ULP using SCTP desires to have  
> its own
>    ports, the ULP should be responsible for registering with IANA for
>    getting its ports assigned.
>
>
> NEW TEXT:
>
> 14.  IANA Considerations
>
>    SCTP defines three registries that IANA maintains:
>
>    --   through definition of additional chunk types,
>    --   through definition of additional parameter types, or
>    --   through definition of additional cause codes within ERROR  
> chunks
>
>    SCTP requires that the IANA Port Numbers registry be opened for  
> SCTP
>    port registrations; Section 14.5 describes how.
>
>
> 14.5  Port Numbers Registry
>
>    SCTP services may use contact port numbers to provide service to
>    unknown callers, as in TCP and UDP.  IANA is therefore requested to
>    open the existing Port Numbers registry for SCTP using the  
> following
>    rules, which we intend to mesh well with existing Port Numbers
>    registration procedures.
>
>    Port numbers are divided into three ranges.  The Well Known  
> Ports are
>    those from 0 through 1023, the Registered Ports are those from 1024
>    through 49151, and the Dynamic and/or Private Ports are those from
>    49152 through 65535.  Well Known and Registered Ports are intended
>    for use by server applications that desire a default contact  
> point on
>    a system.  On most systems, Well Known Ports can only be used by
>    system (or root) processes or by programs executed by privileged
>    users, while Registered Ports can be used by ordinary user  
> processes
>    or programs executed by ordinary users.  Dynamic and/or Private  
> Ports
>    are intended for temporary use, including client-side ports, out- 
> of-
>    band negotiated ports, and application testing prior to  
> registration
>    of a dedicated port; they MUST NOT be registered.
>
>    The Port Numbers registry should accept registrations for SCTP  
> ports
>    in the Well Known Ports and Registered Ports ranges.  Well Known  
> and
>    Registered Ports SHOULD NOT be used without registration.  Although
>    in some cases -- such as porting an application from TCP to SCTP --
>    it may seem natural to use a SCTP port before registration  
> completes,
>    we emphasize that IANA will not guarantee registration of  
> particular
>    Well Known and Registered Ports.  Registrations should be requested
>    as early as possible.
>
>    Each port registration SHALL include the following information:
>
>    o  A short port name, consisting entirely of letters (A-Z and a-z),
>       digits (0-9), and punctuation characters from "-_+./*" (not
>       including the quotes).
>
>    o  The port number that is requested to be registered.
>
>    o  A short English phrase describing the port's purpose.
>
>    o  Name and contact information for the person or entity performing
>       the registration, and possibly a reference to a document  
> defining
>       the port's use.  Registrations coming from IETF working groups
>       need only name the working group, but indicating a contact  
> person
>       is recommended.
>
>    Registrants are encouraged to follow these guidelines when  
> submitting
>    a registration.
>
>    o  A port name SHOULD NOT be registered for more than one SCTP port
>       number.
>
>    o  A port name registered for TCP MAY be registered for SCTP as  
> well.
>       Any such registration SHOULD use the same port number as the
>       existing TCP registration.
>
>    o  Concrete intent to use a port SHOULD precede port registration.
>       For example, existing TCP ports SHOULD NOT be registered in
>       advance of any intent to use those ports for SCTP.
>
>    This document registers the following ports.  (These registrations
>    should be considered models to follow for future allocation  
> requests.)
>
>            discard  9/sctp  Discard  # IETF TSVWG
>                                      # Randall Stewart <rrs@cisco.com>
>                                      # [draft-ietf-tsvwg-2960bis-05]
>
>            The discard service, which accepts SCTP connections on
>            port 9, discards all incoming application data and sends
>            no data in response. Thus, SCTP's discard port is analogous
>            to TCP's discard port, and might be used to check the
>            health of a SCTP stack.
>
>    <add further registrations here>






From tsvwg-bounces@ietf.org Tue Jul 03 04:54:07 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5e98-0004Y6-0h; Tue, 03 Jul 2007 04:54:06 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I5e96-0004Xo-DL
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 03 Jul 2007 04:54:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5e95-0004XQ-OF; Tue, 03 Jul 2007 04:54:03 -0400
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I5e8u-0007m1-Qo; Tue, 03 Jul 2007 04:54:03 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l638roaX026024; Tue, 3 Jul 2007 11:53:50 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 3 Jul 2007 11:53:43 +0300
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 3 Jul 2007 11:53:42 +0300
Received: from mgw-int01.ntc.nokia.com ([172.21.143.96]) by
	esebh101.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 3 Jul 2007 11:53:42 +0300
Received: from [172.21.34.200] (esdhcp034200.research.nokia.com
	[172.21.34.200])
	by mgw-int01.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l638rf30016033; Tue, 3 Jul 2007 11:53:41 +0300
In-Reply-To: <EDB88FD7-B685-466B-8A60-0088072A6CEA@lurchi.franken.de>
References: <46828A44.1050804@icann.org>
	<F9824F69-0C5F-4557-B2C4-0173BD99643A@nokia.com>
	<EDB88FD7-B685-466B-8A60-0088072A6CEA@lurchi.franken.de>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-5--1012814422;
	protocol="application/pkcs7-signature"
Message-Id: <08A60276-68DF-4CAD-91B8-2DC6B77B9230@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
Subject: Re: [Tsvwg] IANA issue with RFC2960/draft-ietf-tsvwg-2960bis
Date: Tue, 3 Jul 2007 11:53:35 +0300
To: "ext Michael Tuexen" <Michael.Tuexen@lurchi.franken.de>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 03 Jul 2007 08:53:42.0747 (UTC)
	FILETIME=[A853AAB0:01C7BD4F]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: tsvwg IETF list <tsvwg@ietf.org>, IESG IESG <iesg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org


--Apple-Mail-5--1012814422
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

On 2007-7-3, at 11:46, ext Michael Tuexen wrote:
> sounds good to me. Just two questions:
> 1. 2960bis is in the RFC editor queue. How will this change of text  
> happen?

It's currently in the "IANA" state, and I asked IANA to hold it there  
until this issue is resolved. Once we have agreed on a procedure, we  
can update the text with an RFC Editor Note.

> 2. Do I need to write an ID or RFC to register a port? Or can I  
> just contact
>    IANA?

No ID needed, the idea is to use "First Come First Served" as an  
allocation policy, similar to UDP and TCP ports. I should probably  
make that explicit in the text.

(Also, note that the process IANA currently uses requires an Expert  
Review. I'm still trying to determine what the rationale for that was  
and if this should be continued. The current proposal does not have  
such an Expert Review stage.)

> I'm asking this only for registration of port numbers which are
>    registered for TCP and/or UDP for a similar service like the  
> discard
>    port you use as an example.

Under the current proposal, you don't ever need a draft, whether this  
is for a port number with an existing UDP/TCP registration or for one  
without.

Lars
--Apple-Mail-5--1012814422
Content-Transfer-Encoding: base64
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGQDCCAvkw
ggJioAMCAQICEGtxkLFHQu1g67hlmYfwPuIwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ
ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA3MDEwNDE2MTE1NFoXDTA4MDEwNDE2MTE1
NFowXDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVnZ2Vy
dDEkMCIGCSqGSIb3DQEJARYVbGFycy5lZ2dlcnRAbm9raWEuY29tMIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEA26hjntVPZMiwh4d8tyuk9KiucvG92BVUGArk5zO1jhmq7tLFgU1mqcIg
VGumfQqjkAzIuh83kxIiqBrB05Wvxp85apwt4sUCvzMe8mQWzZZZYp0rBzwpOj+VC5pxsMRYtYW+
BaTFBEmvFr7D7C7roZUk0lDppS5SZFs4SQbEe9ykB9aeUf1iTiw2+ikyP2+JEYto14WYCoxFWbms
FbQ1uaaK+yn1WH2YHhyMfi0IOxuT0jtbsngjHJMpWIqq334zBhj+rPSUug47YBHr41FCDMHbbbjv
WbyTyDYneOW3WY8LY8bGWVlAknQGB7lgduShe6e0RI/7SL/VE6X27lM9LwIDAQABozIwMDAgBgNV
HREEGTAXgRVsYXJzLmVnZ2VydEBub2tpYS5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUF
AAOBgQCx3nxxTg/WowobVTRXBiXUEEZj4LBiunWbuAnR0UbJIgijvq3JbiJvZo2gUGiW9LPaHSBz
4oxT1VR/S/6O0a4e87oV5cOQm6ReB68o9rDfUzxHTwoCfv2wwMwBrXyzQMjyQK4Lt8siV41gmZpm
rSXMhjTJdd9uYYNoZKQLq+VM+TCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJ
BgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgG
A1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMg
RGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3
DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3
MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5
KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTCBnzAN
BgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9
fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+
uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMB
Af8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3
dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgG
A1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcP
f6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH
2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8x
ggMQMIIDDAIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAo
UHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ
a3GQsUdC7WDruGWZh/A+4jAJBgUrDgMCGgUAoIIBbzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcB
MBwGCSqGSIb3DQEJBTEPFw0wNzA3MDMwODUzMzZaMCMGCSqGSIb3DQEJBDEWBBSHRww2dX7cu1+j
HCbbwNYXA8R8SDCBhQYJKwYBBAGCNxAEMXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0ECEGtxkLFHQu1g67hlmYfwPuIwgYcGCyqGSIb3DQEJEAILMXigdjBiMQsw
CQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UE
AxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEGtxkLFHQu1g67hlmYfwPuIw
DQYJKoZIhvcNAQEBBQAEggEAohYa6MpwE1rSskjbSH/kGqxglrUZRQtGqnny+ZIMcIU/V/IG7o68
bOSucHqIoll0wCX24IqGbrikBwKZQou21VEQvdE9nb2Cs71zfXTYKNhoXVWBXKA8h70yX3umarcc
6MsFnqbn3rXWk3X4QWRdnLaCd/pD4rGEJCWg6gvoSmmgTe3NgkdD68pRUsFV4FVdnh9kdSGnq9k9
g8SIkwrHU9ja898d+c85iXUa+4d7EG2AZIEoqAMLaOKIIESdt9HhfyiAXRB7EnlgW7Xkg/Q6wz7y
VWkXYq5VVcU64LgGOhtTxjS809X1RqfheZpU0U4vOjU3x0ObF0HEj0Dilq2pNQAAAAAAAA==

--Apple-Mail-5--1012814422--





From tsvwg-bounces@ietf.org Tue Jul 03 08:46:52 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5hmA-00025O-C5; Tue, 03 Jul 2007 08:46:38 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I5hm8-0001zU-VW
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 03 Jul 2007 08:46:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5hm8-0001xG-Kq
	for tsvwg@ietf.org; Tue, 03 Jul 2007 08:46:36 -0400
Received: from pork.icsi.berkeley.edu ([192.150.186.19])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5hm3-0007S3-6f
	for tsvwg@ietf.org; Tue, 03 Jul 2007 08:46:36 -0400
Received: from guns.icir.org (adsl-69-222-35-58.dsl.bcvloh.ameritech.net
	[69.222.35.58])
	by pork.ICSI.Berkeley.EDU (8.12.11.20060308/8.12.11) with ESMTP id
	l63CkQ1k015623; Tue, 3 Jul 2007 05:46:26 -0700
Received: from lawyers.icir.org (adsl-69-222-35-58.dsl.bcvloh.ameritech.net
	[69.222.35.58]) by guns.icir.org (Postfix) with ESMTP id 8FA8FC69A1D;
	Tue,  3 Jul 2007 08:46:21 -0400 (EDT)
Received: from lawyers.icir.org (localhost [127.0.0.1])
	by lawyers.icir.org (Postfix) with ESMTP id 0289924F293;
	Tue,  3 Jul 2007 08:45:29 -0400 (EDT)
To: "Lars Eggert" <lars.eggert@nokia.com>, gorry@erg.abdn.ac.uk
From: Mark Allman <mallman@icir.org>
Organization: ICSI Center for Internet Research (ICIR)
Song-of-the-Day: Centerfield
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_bOundary";
	micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 03 Jul 2007 08:45:29 -0400
Message-Id: <20070703124529.0289924F293@lawyers.icir.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: tsvwg@ietf.org
Subject: [Tsvwg] udp guidelines draft: small comments
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: mallman@icir.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

--=_bOundary
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline


Gorry, Lars-
 
I read through the UDP guidelines draft yesterday.  Overall I think it
is in good shape and to me it seems like it is getting close to ready to
forward.  I flagged some small things, which I list below.  No
showstoppers, IMO.

I hope this is helpful.

allman



Sec 1: "unreliable, message-passing" -> "unreliable, best-effort,
message-passing"

Sec 3: spell out "PMTU" on first use

Sec 3.1: The first paragraph is a bit fuzzy, I think.  In particular,
you are advocating that all traffic to a "destination" be controlled
together.  This brings to mind two questions.  First, what is a
"destination"?  A host?  A host+port?  Second, this isn't how the
nominal congestion controller (TCP) does things.  I.e., you say that if
multiple processes are forked then CC should be performed across all of
them (assuming their traffic is going to the same "destination").  That
seems to be different from what TCP might do in this case.  I would like
to see this guidance be more crisp and concrete.  (That said, I am
sitting here at a sort of loss for how to do it.  Maybe I just need more
coffee.)

Sec 3.1.1: "SHOULD consider implementing TCP-friendly" -> "SHOULD
implement TCP-friendly"  (i.e., get rid of the "consider" wiggle word)

Sec 3.1.1: "in Section 3.1," -> "in Section 3.1 because TFRC naturally
addresses them,"

Sec 3.1.2: You note that apps will not benefit from CC if they only send
a small amount of data.  I am not sure I think the key point is
application benefit.  I think of the key point as the network seeing no
benefit from such applications implementing CC.

Sec 3.2: "not to do so SHOULD NOT" -> "not to adapt the packet size
SHOULD NOT" 

Sec 3.3: "send order" -> "transmission order"

Sec 3.4: "includes a 16-bit" -> "includes an optional 16-bit"

Sec 3.4: "where appropriate" -> something clearer   I.e., you might note
that not "where appropriate", but "where data integrity is important" to
scope it to the actual benefit gained by using a stronger check.

Sec 3.5: "typically perform a" -> "typically performs a"




--=_bOundary
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFGikTpWyrrWs4yIs4RAkPOAJ0YzvdwNe4bGLA6yVgF2SC4gj1h8QCfWI3K
+n7X8Cm5/s64iM/glRCXlJc=
=GXmk
-----END PGP SIGNATURE-----
--=_bOundary--





From tsvwg-bounces@ietf.org Tue Jul 03 09:09:42 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5i8R-0000vj-FC; Tue, 03 Jul 2007 09:09:39 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I5i8Q-0000qO-3J
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 03 Jul 2007 09:09:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5i8P-0000mn-Ma
	for tsvwg@ietf.org; Tue, 03 Jul 2007 09:09:37 -0400
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5i8L-0005HA-2k
	for tsvwg@ietf.org; Tue, 03 Jul 2007 09:09:37 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l63D8w1C008619; Tue, 3 Jul 2007 16:09:27 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 3 Jul 2007 16:09:15 +0300
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 3 Jul 2007 16:09:15 +0300
Received: from mgw-int01.ntc.nokia.com ([172.21.143.96]) by
	esebh101.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 3 Jul 2007 16:09:15 +0300
Received: from [172.21.34.200] (esdhcp034200.research.nokia.com
	[172.21.34.200])
	by mgw-int01.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l63D9EkY031984; Tue, 3 Jul 2007 16:09:14 +0300
In-Reply-To: <20070703124529.0289924F293@lawyers.icir.org>
References: <20070703124529.0289924F293@lawyers.icir.org>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-5--997481573;
	protocol="application/pkcs7-signature"
Message-Id: <8AF8AF60-C0FF-44E9-A887-8B88A21859C9@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
Date: Tue, 3 Jul 2007 16:09:08 +0300
To: mallman@icir.org
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 03 Jul 2007 13:09:15.0633 (UTC)
	FILETIME=[5B706610:01C7BD73]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Cc: gorry@erg.abdn.ac.uk, tsvwg@ietf.org
Subject: [Tsvwg] Re: udp guidelines draft: small comments
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org


--Apple-Mail-5--997481573
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

Hi,

thanks for the feedback. I'll fix the nits you have identified, but  
there is one issue that the WG should discuss some more:

On 2007-7-3, at 15:45, ext Mark Allman wrote:
> Sec 3.1: The first paragraph is a bit fuzzy, I think.  In particular,
> you are advocating that all traffic to a "destination" be controlled
> together.  This brings to mind two questions.  First, what is a
> "destination"?  A host?  A host+port?  Second, this isn't how the
> nominal congestion controller (TCP) does things.  I.e., you say  
> that if
> multiple processes are forked then CC should be performed across  
> all of
> them (assuming their traffic is going to the same "destination").   
> That
> seems to be different from what TCP might do in this case.  I would  
> like
> to see this guidance be more crisp and concrete.  (That said, I am
> sitting here at a sort of loss for how to do it.  Maybe I just need  
> more
> coffee.)

The motivation for this text came from seeing a number of request- 
response protocols, where a client shoots off many parallel requests  
to the same server, maybe from different threads or processes. UDP  
has no connections and so it's easy to say "well, it's just one  
request and one response per (application-level) connection, so  
there's no way to do CC", which is inaccurate. Some of these  
protocols initially talked about allowing hundreds of parallel  
requests, at which point CC over the aggregate becomes very desirable.

I agree that the definition of "destination" is weak. If "destination  
IP address + port", that might create some UDP traffic aggregate  
comparable to a TCP flow, if TCP was used by the application. (If  
"destination IP address" only, that might end up looking like  
something that TCB sharing or the Congestion Manager would have  
created, had they seen deployment.)

I'd be very happy to make this more clear in the text, but first the  
WG should come to consensus on whether we want to keep the  
recommendation to perform CC on aggregate traffic to a destination or  
not.

Lars
--Apple-Mail-5--997481573
Content-Transfer-Encoding: base64
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGQDCCAvkw
ggJioAMCAQICEGtxkLFHQu1g67hlmYfwPuIwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ
ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA3MDEwNDE2MTE1NFoXDTA4MDEwNDE2MTE1
NFowXDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVnZ2Vy
dDEkMCIGCSqGSIb3DQEJARYVbGFycy5lZ2dlcnRAbm9raWEuY29tMIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEA26hjntVPZMiwh4d8tyuk9KiucvG92BVUGArk5zO1jhmq7tLFgU1mqcIg
VGumfQqjkAzIuh83kxIiqBrB05Wvxp85apwt4sUCvzMe8mQWzZZZYp0rBzwpOj+VC5pxsMRYtYW+
BaTFBEmvFr7D7C7roZUk0lDppS5SZFs4SQbEe9ykB9aeUf1iTiw2+ikyP2+JEYto14WYCoxFWbms
FbQ1uaaK+yn1WH2YHhyMfi0IOxuT0jtbsngjHJMpWIqq334zBhj+rPSUug47YBHr41FCDMHbbbjv
WbyTyDYneOW3WY8LY8bGWVlAknQGB7lgduShe6e0RI/7SL/VE6X27lM9LwIDAQABozIwMDAgBgNV
HREEGTAXgRVsYXJzLmVnZ2VydEBub2tpYS5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUF
AAOBgQCx3nxxTg/WowobVTRXBiXUEEZj4LBiunWbuAnR0UbJIgijvq3JbiJvZo2gUGiW9LPaHSBz
4oxT1VR/S/6O0a4e87oV5cOQm6ReB68o9rDfUzxHTwoCfv2wwMwBrXyzQMjyQK4Lt8siV41gmZpm
rSXMhjTJdd9uYYNoZKQLq+VM+TCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJ
BgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgG
A1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMg
RGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3
DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3
MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5
KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTCBnzAN
BgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9
fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+
uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMB
Af8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3
dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgG
A1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcP
f6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH
2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8x
ggMQMIIDDAIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAo
UHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ
a3GQsUdC7WDruGWZh/A+4jAJBgUrDgMCGgUAoIIBbzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcB
MBwGCSqGSIb3DQEJBTEPFw0wNzA3MDMxMzA5MDhaMCMGCSqGSIb3DQEJBDEWBBQaV98C+AQAGvHY
8rNJVsT3mMA34DCBhQYJKwYBBAGCNxAEMXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0ECEGtxkLFHQu1g67hlmYfwPuIwgYcGCyqGSIb3DQEJEAILMXigdjBiMQsw
CQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UE
AxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEGtxkLFHQu1g67hlmYfwPuIw
DQYJKoZIhvcNAQEBBQAEggEASr5+NvoSp2K6/0hBvOAahpK55RX0fYarXPC+KP0T20uU5W8VNH7/
jcutZn2KcxSwCT0dD1dWHqX1NPvznhfH1nnQipYEGGNWPWod1XK7IM6wdAPyeKxg3pgS5JS9axVU
BqaO2x5qJb9zHxSi1kbdXKmq72zivK7vuzKaI6ih2kD0/Kpao7waO5eFCWZEsWZCOv/VrBn2lE+o
qKTfLk5OSIciAghEQwEgvhft35wzAljBPcvZlFPMVtjTx/OJHWwClFpA4w6pzOXi5RXZATZj10ch
TrJFAXj9URtyLX3tH6VJeObNPn0oc6ZUJ9we8LjoDemwN7HmaVJAEs5q82COGwAAAAAAAA==

--Apple-Mail-5--997481573--





From tsvwg-bounces@ietf.org Tue Jul 03 10:03:47 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5iyo-0008L3-KM; Tue, 03 Jul 2007 10:03:46 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I5iym-0008HI-Rl
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 03 Jul 2007 10:03:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5iym-0008GH-I2; Tue, 03 Jul 2007 10:03:44 -0400
Received: from mail-n.franken.de ([193.175.24.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I5ixn-0002rt-GT; Tue, 03 Jul 2007 10:03:44 -0400
Received: from [192.168.1.17] (p508FD6B6.dip.t-dialin.net [80.143.214.182])
	by mail-n.franken.de (Postfix) with ESMTP id 9298F8006DA4;
	Tue,  3 Jul 2007 16:02:41 +0200 (CEST)
	(KNF-authenticated sender: macmic)
In-Reply-To: <08A60276-68DF-4CAD-91B8-2DC6B77B9230@nokia.com>
References: <46828A44.1050804@icann.org>
	<F9824F69-0C5F-4557-B2C4-0173BD99643A@nokia.com>
	<EDB88FD7-B685-466B-8A60-0088072A6CEA@lurchi.franken.de>
	<08A60276-68DF-4CAD-91B8-2DC6B77B9230@nokia.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <5C2B6E41-B747-4ACF-B428-646E6E50D1BB@lurchi.franken.de>
Content-Transfer-Encoding: 7bit
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Tsvwg] IANA issue with RFC2960/draft-ietf-tsvwg-2960bis
Date: Tue, 3 Jul 2007 16:02:42 +0200
To: Lars Eggert <lars.eggert@nokia.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: tsvwg IETF list <tsvwg@ietf.org>, IESG IESG <iesg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi Lars,

then I'm fine with your proposal.

Best regards
Michael

On Jul 3, 2007, at 10:53 AM, Lars Eggert wrote:

> On 2007-7-3, at 11:46, ext Michael Tuexen wrote:
>> sounds good to me. Just two questions:
>> 1. 2960bis is in the RFC editor queue. How will this change of  
>> text happen?
>
> It's currently in the "IANA" state, and I asked IANA to hold it  
> there until this issue is resolved. Once we have agreed on a  
> procedure, we can update the text with an RFC Editor Note.
>
>> 2. Do I need to write an ID or RFC to register a port? Or can I  
>> just contact
>>    IANA?
>
> No ID needed, the idea is to use "First Come First Served" as an  
> allocation policy, similar to UDP and TCP ports. I should probably  
> make that explicit in the text.
>
> (Also, note that the process IANA currently uses requires an Expert  
> Review. I'm still trying to determine what the rationale for that  
> was and if this should be continued. The current proposal does not  
> have such an Expert Review stage.)
>
>> I'm asking this only for registration of port numbers which are
>>    registered for TCP and/or UDP for a similar service like the  
>> discard
>>    port you use as an example.
>
> Under the current proposal, you don't ever need a draft, whether  
> this is for a port number with an existing UDP/TCP registration or  
> for one without.
>
> Lars






From tsvwg-bounces@ietf.org Tue Jul 03 14:12:52 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5mrk-00038T-6t; Tue, 03 Jul 2007 14:12:44 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I5mri-00038L-AQ
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 03 Jul 2007 14:12:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5mri-00038D-0t; Tue, 03 Jul 2007 14:12:42 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I5mrd-0004gz-MZ; Tue, 03 Jul 2007 14:12:42 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 03 Jul 2007 11:12:33 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAIouikarR7PD/2dsb2JhbAA
X-IronPort-AV: i="4.16,493,1175497200"; 
	d="scan'208"; a="176208963:sNHT193005441"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l63ICUfC030953; 
	Tue, 3 Jul 2007 11:12:30 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l63ICGnM001770;
	Tue, 3 Jul 2007 18:12:30 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 3 Jul 2007 11:12:20 -0700
Received: from [10.32.241.68] ([10.32.241.68]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 3 Jul 2007 11:12:19 -0700
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Transfer-Encoding: 7bit
Message-Id: <C6135E72-1044-415C-A827-24C86DB6D411@cisco.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: tsvwg <tsvwg@ietf.org>, l3vpn@ietf.org
From: Bruce Davie <bdavie@cisco.com>
Date: Tue, 3 Jul 2007 14:12:13 -0400
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 03 Jul 2007 18:12:20.0043 (UTC)
	FILETIME=[B23129B0:01C7BD9D]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=897; t=1183486350;
	x=1184350350; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=bdavie@cisco.com;
	z=From:=20Bruce=20Davie=20<bdavie@cisco.com>
	|Subject:=20draft-davie-tsvwg-rsvp-l3vpn-00.txt |Sender:=20;
	bh=6NTBvLKLS2upb2+1zD5bAfSnWnzDWjV6rNUojj2SYjw=;
	b=nqJr4fzu9zMUPeBsDZX2HAIMtj0i5ZGcYlezxL7ulOYZXxlBFH6DXrskYNW8KkPeJCHF5vu9
	U2GMTa+Ri4xNacpkq6YjfZzMEY9K7OkGlJiUbE3AWin6ePkG9rUk9/9m;
Authentication-Results: sj-dkim-3; header.From=bdavie@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: 
Subject: [Tsvwg] draft-davie-tsvwg-rsvp-l3vpn-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

I've posted a draft that may be of interest to the TSVWG and L3VPN  
working groups. While it percolates through the ID system, you can  
get a copy from

ftp://ftpeng.cisco.com/bdavie/draft-davie-tsvwg-rsvp-l3vpn-00.txt

I've asked for a slot in both WGs in Chicago, with the intention of  
deciding afterwards which group (if any) might be the more  
appropriate home.

Abstract

    RFC 4364 defines an approach to building provider-provisioned  
Layer 3
    VPNs.  It may be desirable to use RSVP to perform admission control
    on the links between CE and PE routers.  This document specifies
    procedures by which RSVP messages travelling from CE to CE across an
    L3VPN may be appropriately handled by PE routers so that admission
    control can be performed on PE-CE links.  Optionally, admission
    control across the provider's backbone may also be supported.





From tsvwg-bounces@ietf.org Wed Jul 04 06:35:41 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I62Cv-0005Sx-C7; Wed, 04 Jul 2007 06:35:37 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I62Cu-0005Sn-Si
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 04 Jul 2007 06:35:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I62Cu-0005Sd-Ej; Wed, 04 Jul 2007 06:35:36 -0400
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I62Cp-00088O-Vd; Wed, 04 Jul 2007 06:35:36 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l64AYohQ018159; Wed, 4 Jul 2007 13:35:14 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 4 Jul 2007 13:34:50 +0300
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by
	esebh104.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 4 Jul 2007 13:34:49 +0300
Received: from [172.21.34.161] (esdhcp034161.research.nokia.com
	[172.21.34.161])
	by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l64AYlnT023391; Wed, 4 Jul 2007 13:34:48 +0300
In-Reply-To: <0E46EBE9-1C13-44B6-9C04-476D418F5A6D@nokia.com>
References: <200702111621.l1BGL6mw029875@venus.xmundo.net>
	<0E46EBE9-1C13-44B6-9C04-476D418F5A6D@nokia.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <A6CE6259-646E-4C35-9DA3-8911A8CB2B54@nokia.com>
Content-Transfer-Encoding: 7bit
From: Lars Eggert <lars.eggert@nokia.com>
Subject: Re: [Tsvwg] Re: [tcpm] Revision of
	draft-larsen-tsvwg-port-randomization
Date: Wed, 4 Jul 2007 13:34:42 +0300
To: tsvwg WG <tsvwg@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 04 Jul 2007 10:34:49.0993 (UTC)
	FILETIME=[F319AF90:01C7BE26]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: tcpm@ietf.org, DCCP mailing list <dccp@ietf.org>,
	ext Fernando Gont <fernando@gont.com.ar>, TSV Dir <tsv-dir@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: tsvwg WG <tsvwg@ietf.org>
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

On 2007-5-31, at 17:51, ext Lars Eggert wrote:
> The concepts in this draft are likely relevant to most of our  
> transport protocols, and hence would be in scope for TSVWG. The  
> TSVWG chairs are interested in comments on whether there is group  
> interest in this draft - please comment on tsvwg@ietf.org.

We've received some positive feedback on adopting this draft, but I'd  
like to see a stronger show of support, because this draft impacts  
several of our transport protocols at the same time.

Please comment on tsvwg@ietf.org - reply-to set accordingly.

Lars





From tsvwg-bounces@ietf.org Wed Jul 04 11:32:06 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I66pl-00013e-Bn; Wed, 04 Jul 2007 11:32:01 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I66pk-00010I-EA
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 04 Jul 2007 11:32:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I66pk-0000y4-3J
	for tsvwg@ietf.org; Wed, 04 Jul 2007 11:32:00 -0400
Received: from ug-out-1314.google.com ([66.249.92.168])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I66pg-0003Ak-Or
	for tsvwg@ietf.org; Wed, 04 Jul 2007 11:32:00 -0400
Received: by ug-out-1314.google.com with SMTP id u2so811676uge
	for <tsvwg@ietf.org>; Wed, 04 Jul 2007 08:31:56 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type;
	b=I46NFaVsB8lZGIF36bwopxj0x9wxWctv7jZBbnVoW6FZmvAWy18nTMrqUREos5KzvYQ/Rf1ThDyZPYBn7B1aZnYgpL32jSMjlXJYSD/2tGgSZr6PQ2ZyqPKlaJmLI62Oqi36ZfHtQx/wKGEmClXvFBq1bRd0Mk0wXEpodackwH4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:mime-version:content-type;
	b=kNPz1qmqt+Ss5hJI6+2Eo0JunmBzvgx+MrnsptLorhT2yRGEJkqRB31QEHFlKdJhpfhOIC3GhmaI673bfgkisIZ2QfWLFlE2JgboQ6OyJagzXgpAbMIw29onycza9zZ9EfhMr8zRCpx4sw2APxSy5r913ST+cVQPq2s/yBQBiak=
Received: by 10.67.88.17 with SMTP id q17mr1256877ugl.1183563115989;
	Wed, 04 Jul 2007 08:31:55 -0700 (PDT)
Received: by 10.66.236.6 with HTTP; Wed, 4 Jul 2007 08:31:55 -0700 (PDT)
Message-ID: <c2461cd60707040831k3855c2b0hd5c205fa910a9ee6@mail.gmail.com>
Date: Wed, 4 Jul 2007 16:31:55 +0100
From: "arif khan" <arif15jan@gmail.com>
To: tsvwg@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_48160_15525115.1183563115957"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Subject: [Tsvwg] Configuration of 2 local as with single asp in signle
	exchange
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

------=_Part_48160_15525115.1183563115957
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,

i want to rout message using two opc=X and opc=Y using m3ua stack
configuration of adding two local AS with opc X and opc Y to dpc Z.

The side having opc X and Y and the side having dpc Z is in ASP-ASP
configuration in single exchange both the side.
I added following configuration at m3ua:
side X and Y:
==========
added asp (aspid 1)
added remote asp(remaspid 1)
added remote as (remote asid=1,rc=1,dpc=Z)
added local as (asid= 1,rc=1,opc=X)
added local as (asid=2,rc=2,opc=Y)

side z:
=======
added asp (aspid 1)
added remote asp(remoteaspid=1)
added remote as (remoteasid=1,rc=1,dpc=X)
added remote as (remoteasid=2,rc=2,dpc=Y)
added local as (asid=1,rc=1,opc=Z)

what i am missing in the configuration and what should be the correct
configuration according to rfc and maintaining interoperability of the
asp-asp in single exchange.

tia
ar

------=_Part_48160_15525115.1183563115957
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>Hi,</div>
<div>&nbsp;</div>
<div>i want to rout message&nbsp;using two opc=X and opc=Y using m3ua stack configuration of adding two local&nbsp;AS with opc X and opc Y to dpc Z.</div>
<div>&nbsp;</div>
<div>The side having opc X and Y and the side having dpc Z is in ASP-ASP configuration in single exchange both the side.</div>
<div>I added following configuration at m3ua:</div>
<div>side X and Y:</div>
<div>==========</div>
<div>added asp&nbsp;(aspid 1)</div>
<div>added remote asp(remaspid 1)</div>
<div>added remote as (remote asid=1,rc=1,dpc=Z)</div>
<div>added local as (asid= 1,rc=1,opc=X)</div>
<div>added local as (asid=2,rc=2,opc=Y)</div>
<div>&nbsp;</div>
<div>side z:</div>
<div>=======</div>
<div>added asp (aspid 1)</div>
<div>added remote asp(remoteaspid=1)</div>
<div>added&nbsp;remote as (remoteasid=1,rc=1,dpc=X)</div>
<div>added remote as (remoteasid=2,rc=2,dpc=Y)</div>
<div>added local as (asid=1,rc=1,opc=Z)</div>
<div>&nbsp;</div>
<div>what i am missing in the configuration and what should be the correct configuration according to rfc and maintaining interoperability of the asp-asp in single exchange.</div>
<div>&nbsp;</div>
<div>tia</div>
<div>ar</div>
<div>&nbsp;</div>
<div>&nbsp;</div>

------=_Part_48160_15525115.1183563115957--





From tsvwg-bounces@ietf.org Thu Jul 05 09:06:24 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6R2K-0004Tf-9o; Thu, 05 Jul 2007 09:06:20 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I6R2I-0004Po-WB
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 05 Jul 2007 09:06:19 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6R2H-0004NC-PT
	for tsvwg@ietf.org; Thu, 05 Jul 2007 09:06:18 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I6R2F-0005Fd-EW
	for tsvwg@ietf.org; Thu, 05 Jul 2007 09:06:17 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 05 Jul 2007 15:05:21 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAHmIjEaQ/uCKh2dsb2JhbACCY4xKAQEBCA4s
X-IronPort-AV: i="4.16,503,1175464800"; d="scan'208,217";
	a="147317164:sNHT58827879592"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l65D5KbK025944; 
	Thu, 5 Jul 2007 15:05:20 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l65D5DTM016685; 
	Thu, 5 Jul 2007 13:05:20 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 5 Jul 2007 15:05:17 +0200
Received: from [144.254.53.89] ([144.254.53.89]) by xfe-ams-332.cisco.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 5 Jul 2007 15:05:16 +0200
In-Reply-To: <46E7B21EF4A45749B2432ABDCDE6FEA101D83790@MCLNEXVS12.resource.ds.bah.com>
References: <46E7B21EF4A45749B2432ABDCDE6FEA101D83790@MCLNEXVS12.resource.ds.bah.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: multipart/alternative; boundary=Apple-Mail-29--825086141
Message-Id: <A10C4CDD-FCAC-4578-A2F5-0A53674B01D9@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
Subject: Re: [Tsvwg] RSVP proxy approaches
Date: Thu, 5 Jul 2007 15:02:23 +0200
To: "Christou, Christos" <christou_chris@bah.com>, Fred Baker <fred@cisco.com>,
	Bose Pratik <pratik.bose@lmco.com>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 05 Jul 2007 13:05:16.0478 (UTC)
	FILETIME=[21B7BDE0:01C7BF05]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=33982; t=1183640720;
	x=1184504720; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.com>
	|Subject:=20Re=3A=20[Tsvwg]=20RSVP=20proxy=20approaches
	|Sender:=20; bh=oKMgWITq/3VCWlZM1aZnOAX3+3YgoI0QuUkCYlMBDBo=;
	b=kB0x1SFFKRINOFYHs+HmKF44ZbzBkHrukN4CSIzLTxvuFzrymt/HO6wumNFV/apFJOlfZWkX
	Qn2DRc9GFc/sPoFGUDUMN/zdDCttlC7NITIUVsykyoCkCE7+F3+3BBBm;
Authentication-Results: ams-dkim-1; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 87e958510a39f65fbeb5ae8b5e360e3b
Cc: tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org


--Apple-Mail-29--825086141
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

Chris, Fred, Pratik and all,

Please see below:

On 19 Jun 2007, at 20:40, Christou, Christos wrote:

> Francois,
>
> Yes, I do think this works.
>
> Thanks,
>
> Chris
>
> From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]
> Sent: Tuesday, June 19, 2007 11:22 AM
> To: Christou, Christos
> Cc: Francois Le Faucheur IMAP; tsvwg@ietf.org
> Subject: Re: [Tsvwg] RSVP proxy approaches
>
> Chris and all,
>
> I'm started editing rsvp-proxy-approaches to reflect all discussed  
> changes.
>
> Regarding the input below, I would propose that we incorporate it  
> as a new section under Appendix A (eg "A.5 RSVP-based Voice/Video  
> CAC in IPsec environments"). This seems reasonable since:
> * Appendix A is dedicated to describing use cases for the RSVP  
> Proxy approaches described in the main sections of the I-D .
> * the fundamental approach used in this scenario is already  
> described in the main sections of the I-D. The text below focuses  
> on some details specific to when the approach is used in the  
> presence of IPsec.
>

Below is the text I put together for the new Appendix A.5.
I added material to explain how this relates to [I-D.ietf-tsvwg-vpn- 
signaled-preemption].
If you want to send comments/suggestions by the end of today I could  
address those before posting.
Francois



A.5.  RSVP Proxies for Reservations in the presence of IPsec Gateways

    [I-D.ietf-tsvwg-vpn-signaled-preemption] discusses how resource
    reservation can be supported end-to-end in a nested VPN environment.
    At each VPN level, VPN Routers behave as [RFC4301] security gateways
    between a plaintext domain and a cyphertext domain.  To achieve end-
    to-end resource reservation, the VPN Routers process RSVP signaling
    on the plaintext side, perform aggregation of plaintext  
reservations,
    and maintain the corresponding aggregate RSVP reservations on the
    cyphertext side.  Each aggregate reservation is established on  
behalf
    of multiple encrypted end-to-end sessions sharing the same ingress
    and egress VPN Routers.  These aggregate reservations can be as
    specified in [RFC3175] or [RFC4860].

    Section 3 of [I-D.ietf-tsvwg-vpn-signaled-preemption] discusses the
    necessary data flows within a VPN Router to achieve the behavior
    described in the previous paragraph.  Two mechanisms are  
described to
    achieve such data flows.  Section 3.1 presents the case where the  
VPN
    Router carries data across the cryptographic boundary.  Section 3.2
    discusses the case where the VPN router uses a Network-Guard.

    Where such mechanisms are not supported by the VPN Routers, the
    approach for end-to-end reservation presented in
    [I-D.ietf-tsvwg-vpn-signaled-preemption] cannot be deployed.  An
    alternative approach to support resource reservations within the
    cyphertext core is to use the "Application_Entity-Controlled Proxy"
    approach (as defined in Section 4.5) in the following way:

    o  the RSVP Proxies are located inside the cyphertext domain and use
       aggregate RSVP reservations,

    o  the Application Entity exchange application level signaling with
       the end systems in the plaintext domain,

    o  the Application Entity controls the RSVP Proxies in the  
cyphertext
       domain via an RSVP Proxy control interface

    This is illustrated in Figure 17 in the case where the  
application is
    SIP-based multimedia communications.



          |-------|                                    |-------|
          |SIP    |///////////////////\\\\\\\\\\\\\\\\\|SIP    |
         /|Server/|                                    |Server/|\
        / |Proxy  |                                    |Proxy  | \
       /  |-------|                                    |-------|  \
      /      ^    \\                                  //   ^       \
     /       ^     \\                                //    ^        \
    /        ^      \\                              //     ^         \
|---|   |------|  |--------|   ***   ***   |--------|  |------|   |---|
| S |---|IPsec |--|  ARSVP |---*r*---*r*---| ARSVP  |--|IPsec |---| R |
|---|   | GW   |  | Sender |   ***   ***   |Receiver|  | GW   |   |---|
         |------|  |  Proxy |               | Proxy  |  |------|
                   |--------|               |--------|

      ***PT*****> **********************CT****************> ****PT***>

      =====>                                                   =====>

                             =====ARSVP======>



|----| RSVP-capable      |----| RSVP-capable         ***
| S  | Sender            | R  | Receiver             *r* regular RSVP
|----|                   |----|                      *** router

|------|
|IPsec | IPsec gateway
| GW   |
|------|

ARSVP Aggregate RSVP

***>  media flow

==>   segment of flow path protected by RSVP reservation

/ \   SIP signaling

   ^    Network management interface between SIP Server/Proxy
        and IPsec device

//    control interface between SIP Server/Proxy and ARSVP Proxy

PT    Plaintext network

CT    Cyphertext network


      Figure 17: RSVP Proxies for Reservations in the Presence of IPsec
                                  Gateways

    Where the sender and receiver are RSVP capable, they may also use
    RSVP signaling.  This achieves resource reservation on the plaintext
    segments of the end-to-end i.e. :

    o  from the sender to the ingress IPsec gateway and

    o  from the egress IPsec gateway to the receiver.

    In this use case, because the VPN Routers do not support any RSVP
    specific mechanism, the end-to-end RSVP signaling is effectively
    hidden by the IPsec gateways on the cyphertext segment of the end- 
to-
    end path.

    As with the "Application_Entity-Controlled Proxy" approach (defined
    in Section 4.5), the solution here for synchronizing RSVP signaling
    with application-level signaling is to rely on an application-level
    signaling device that controls an on-path RSVP Proxy function.
    However, in the present use case, the RSVP Proxies are a  
component of
    a cyphertext network where all user (bearer) traffic is IPsec
    encrypted.  This has a number of implications including the
    following:

    1.  encrypted flows can not be identified in the cyphertext  
domain so
        that network nodes can only classify traffic based on IP address
        and DiffServ Code Points (DSCPs).  As a result, only aggregate
        RSVP reservations (such as those specified in [RFC3175] or
        [RFC4860] ) can be used.  This is similar to
        [I-D.ietf-tsvwg-vpn-signaled-preemption].

    2.  Determining the RSVP Sender proxy and RSVP receiver Proxy to be
        used for aggregation of a given flow from sender to receiver
        creates a number of challenges.  Details on how this may be
        achieved are beyond the scope of this document.  We observe  
that,
        as illustrated in Figure 17, this may be facilitated by a  
network
        management interface between the application entity and the  
IPsec
        gateways.  For example, this interface may be used by the
        application entity to obtain information about which IPsec
        gateway is on the path of a given end-to-end flow.  Then, the
        application entity may maintain awareness of which RSVP Proxy is
        on the cyphertext path between a given pair of IPsec gateways.
        How such awareness is achieved is beyond the scope of this
        document.  We simply observe that such awareness can be easily
        achieved through simple configuration in the particular case
        where a single (physical or logical) Proxy device is fronting a
        given IPsec gateway.  We also observe that when awareness of the
        RSVP Receiver Proxy for a particular egress IPsec gateway (or
        end-to-end flow) is not available, the aggregate reservation may
        be signaled by the RSVP Sender Proxy to the destination address
        of the egress IPsec gateway and then proxied by the RSVP  
Receiver
        Proxy.

    Different flavors of operations are possible in terms of aggregate
    reservation sizing.  For example, the application entity can  
initiate
    an aggregate reservation of fixed size a priori and then simply keep
    count of the bandwidth used by sessions and reject sessions that
    would result in excess usage of an aggregate reservation.  The
    application entity could also re-size the aggregate reservations  
on a
    session by session basis.  Alternatively, the application entity
    could re-size the aggregate reservations in step increments  
typically
    corresponding to the bandwidth requirement of multiple sessions.





--Apple-Mail-29--825086141
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; ">Chris, Fred, Pratik and =
all,<DIV><BR class=3D"khtml-block-placeholder"></DIV><DIV>Please see =
below:</DIV><DIV><BR><DIV><DIV>On 19 Jun 2007, at 20:40, Christou, =
Christos wrote:</DIV><BR class=3D"Apple-interchange-newline"><BLOCKQUOTE =
type=3D"cite">  <DIV dir=3D"ltr" align=3D"left">Francois,</DIV> <DIV =
dir=3D"ltr" align=3D"left">=A0</DIV> <DIV dir=3D"ltr" align=3D"left">Yes, =
I do think this works.</DIV> </BLOCKQUOTE><BLOCKQUOTE type=3D"cite"><DIV =
dir=3D"ltr" align=3D"left">=A0</DIV> <DIV dir=3D"ltr" =
align=3D"left">Thanks,</DIV> <DIV dir=3D"ltr" align=3D"left">=A0</DIV> =
<DIV dir=3D"ltr" align=3D"left">Chris</DIV><BR> <DIV =
class=3D"OutlookMessageHeader" lang=3D"en-us" dir=3D"ltr" align=3D"left"> =
 From: Francois Le Faucheur IMAP [<A =
href=3D"mailto:flefauch@cisco.com">mailto:flefauch@cisco.com</A>] =
<BR>Sent: Tuesday, June 19, 2007 11:22 AM<BR>To: Christou, =
Christos<BR>Cc: Francois Le Faucheur IMAP; <A =
href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</A><BR>Subject: Re: =
[Tsvwg] RSVP proxy approaches<BR><BR></DIV> <DIV></DIV>Chris and all, =
<DIV><BR class=3D"khtml-block-placeholder"></DIV> <DIV>I'm started =
editing rsvp-proxy-approaches to reflect all discussed changes.</DIV> =
<DIV><BR class=3D"khtml-block-placeholder"></DIV> <DIV>Regarding the =
input below, I would propose that we incorporate it as a new section =
under Appendix A (eg "A.5 RSVP-based Voice/Video CAC in IPsec =
environments"). This seems reasonable since:</DIV> <DIV><SPAN =
class=3D"Apple-tab-span" style=3D"WHITE-SPACE: pre"></SPAN>*=A0Appendix =
A is dedicated to describing use cases for the RSVP Proxy approaches =
described in the main sections of the I-D .</DIV> <DIV><SPAN =
class=3D"Apple-tab-span" style=3D"WHITE-SPACE: pre"></SPAN>* the =
fundamental approach used in this scenario is already described in the =
main sections of the I-D. The text below focuses on some details =
specific to when the approach is used in the presence of IPsec.=A0</DIV> =
<DIV><BR class=3D"khtml-block-placeholder"></DIV></BLOCKQUOTE><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Arial">Below is the text I put =
together for the new Appendix A.5.</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Arial">I added material to explain =
how this relates to=A0<FONT class=3D"Apple-style-span" =
face=3D"Courier">[I-D.ietf-tsvwg-vpn-signaled-preemption].</FONT></FONT></=
DIV><DIV><FONT class=3D"Apple-style-span" face=3D"Arial">If you want to =
send comments/suggestions by the end of today I could address those =
before posting.</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Arial">Francois</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">A.5.=A0 RSVP Proxies for =
Reservations in the presence of IPsec Gateways</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 =
[I-D.ietf-tsvwg-vpn-signaled-preemption] discusses how =
resource</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier">=A0=A0 reservation can be supported end-to-end in a =
nested VPN environment.</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier">=A0=A0 At each VPN level, VPN Routers behave as =
[RFC4301] security gateways</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 between a plaintext =
domain and a cyphertext domain.=A0 To achieve =
end-</FONT></DIV><DIV><FONT class=3D"Apple-style-span" face=3D"Courier">=A0=
=A0 to-end resource reservation, the VPN Routers process RSVP =
signaling</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier">=A0=A0 on the plaintext side, perform aggregation of =
plaintext reservations,</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier">=A0=A0 and maintain the corresponding aggregate RSVP =
reservations on the</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier">=A0=A0 cyphertext side.=A0 Each aggregate reservation =
is established on behalf</FONT></DIV><DIV><FONT class=3D"Apple-style-span"=
 face=3D"Courier">=A0=A0 of multiple encrypted end-to-end sessions =
sharing the same ingress</FONT></DIV><DIV><FONT class=3D"Apple-style-span"=
 face=3D"Courier">=A0=A0 and egress VPN Routers.=A0 These aggregate =
reservations can be as</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier">=A0=A0 specified in [RFC3175] or =
[RFC4860].</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 Section 3 of =
[I-D.ietf-tsvwg-vpn-signaled-preemption] discusses =
the</FONT></DIV><DIV><FONT class=3D"Apple-style-span" face=3D"Courier">=A0=
=A0 necessary data flows within a VPN Router to achieve the =
behavior</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier">=A0=A0 described in the previous paragraph.=A0 Two =
mechanisms are described to</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 achieve such data =
flows.=A0 Section 3.1 presents the case where the =
VPN</FONT></DIV><DIV><FONT class=3D"Apple-style-span" face=3D"Courier">=A0=
=A0 Router carries data across the cryptographic boundary.=A0 Section =
3.2</FONT></DIV><DIV><FONT class=3D"Apple-style-span" face=3D"Courier">=A0=
=A0 discusses the case where the VPN router uses a =
Network-Guard.</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 Where such mechanisms =
are not supported by the VPN Routers, the</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 approach for =
end-to-end reservation presented in</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 =
[I-D.ietf-tsvwg-vpn-signaled-preemption] cannot be deployed.=A0 =
An</FONT></DIV><DIV><FONT class=3D"Apple-style-span" face=3D"Courier">=A0=A0=
 alternative approach to support resource reservations within =
the</FONT></DIV><DIV><FONT class=3D"Apple-style-span" face=3D"Courier">=A0=
=A0 cyphertext core is to use the "Application_Entity-Controlled =
Proxy"</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier">=A0=A0 approach (as defined in Section 4.5) in the =
following way:</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 o=A0 the RSVP Proxies =
are located inside the cyphertext domain and use</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0 =A0 =A0 aggregate RSVP =
reservations,</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 o=A0 the Application =
Entity exchange application level signaling with</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0 =A0 =A0 the end systems =
in the plaintext domain,</FONT></DIV><DIV><FONT class=3D"Apple-style-span"=
 face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 o=A0 the Application =
Entity controls the RSVP Proxies in the =
cyphertext</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier">=A0 =A0 =A0 domain via an RSVP Proxy control =
interface</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 This is illustrated =
in Figure 17 in the case where the application is</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 SIP-based multimedia =
communications.</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0 =A0 =A0 =A0=A0 =
|-------|=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 |-------|</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier">=A0 =A0 =A0 =A0=A0 |SIP=A0 =A0 =
|///////////////////\\\\\\\\\\\\\\\\\|SIP=A0 =A0 =
|</FONT></DIV><DIV><FONT class=3D"Apple-style-span" face=3D"Courier">=A0 =
=A0 =A0 =A0 /|Server/|=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 |Server/|\</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0 =A0 =A0=A0 / |Proxy=A0 =
|=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
|Proxy=A0 | \</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier">=A0 =A0 =A0 /=A0 |-------|=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |-------|=A0 =
\</FONT></DIV><DIV><FONT class=3D"Apple-style-span" face=3D"Courier">=A0 =
=A0=A0 /=A0 =A0 =A0 ^=A0 =A0 \\=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 //=A0=A0 ^=A0 =A0 =A0=A0 =
\</FONT></DIV><DIV><FONT class=3D"Apple-style-span" face=3D"Courier">=A0 =
=A0 /=A0 =A0 =A0=A0 ^=A0 =A0=A0 \\=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 //=A0 =A0 ^=A0 =A0 =A0 =A0 =
\</FONT></DIV><DIV><FONT class=3D"Apple-style-span" face=3D"Courier">=A0=A0=
 /=A0 =A0 =A0 =A0 ^=A0 =A0 =A0 \\=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 //=A0 =A0=A0 ^=A0 =A0 =A0 =A0=A0 =
\</FONT></DIV><DIV><FONT class=3D"Apple-style-span" face=3D"Courier"> =
|---|=A0=A0 |------|=A0 |--------|=A0=A0 ***=A0=A0 ***=A0=A0 |--------|=A0=
 |------|=A0=A0 |---|</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier"> | S |---|IPsec |--|=A0 ARSVP |---*r*---*r*---| ARSVP=A0 =
|--|IPsec |---| R |</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier"> |---|=A0=A0 | GW=A0=A0 |=A0 | Sender |=A0=A0 ***=A0=A0 =
***=A0=A0 |Receiver|=A0 | GW=A0=A0 |=A0=A0 |---|</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0 =A0 =A0=A0 =A0|------|=A0 =
|=A0 Proxy |=A0 =A0 =A0 =A0 =A0 =A0 =A0=A0 | Proxy=A0 |=A0 =
|------|</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier">=A0 =A0=A0 =A0=A0 =A0=A0 =A0=A0 =A0=A0 =A0|--------|=A0 =
=A0 =A0 =A0 =A0 =A0 =A0=A0 |--------|</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0 =A0=A0 ***PT*****&gt; =
**********************CT****************&gt; =
****PT***&gt;</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0 =A0=A0 =3D=3D=3D=3D=3D&gt;=
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0=A0 =3D=3D=3D=3D=3D&gt;</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =3D=3D=3D=3D=3DARSVP=3D=3D=3D=3D=3D=3D&gt;</FO=
NT></DIV><DIV><FONT class=3D"Apple-style-span" face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"> |----| RSVP-capable=A0 =A0 =
=A0 |----| RSVP-capable=A0 =A0 =A0 =A0=A0 ***</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"> | S=A0 | Sender=A0 =A0 =A0 =
=A0 =A0 =A0 | R=A0 | Receiver=A0 =A0 =A0 =A0 =A0 =A0=A0 *r* regular =
RSVP</FONT></DIV><DIV><FONT class=3D"Apple-style-span" face=3D"Courier"> =
|----|=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=A0 |----|=A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 *** router</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"> =
|------|</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier"> |IPsec | IPsec gateway</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"> | GW=A0=A0 =
|</FONT></DIV><DIV><FONT class=3D"Apple-style-span" face=3D"Courier"> =
|------|</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"> ARSVP Aggregate =
RSVP</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"> ***&gt;=A0 media =
flow</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"> =3D=3D&gt;=A0=A0 segment of =
flow path protected by RSVP reservation</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"> / \=A0=A0 SIP =
signaling</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0 ^=A0 =A0 Network =
management interface between SIP Server/Proxy</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0 =A0 =A0=A0 and IPsec =
device</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"> //=A0 =A0 control interface =
between SIP Server/Proxy and ARSVP Proxy</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"> PT=A0 =A0 Plaintext =
network</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"> CT=A0 =A0 Cyphertext =
network</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0 =A0=A0 Figure 17: RSVP =
Proxies for Reservations in the Presence of IPsec</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=A0 Gateways</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 Where the sender and =
receiver are RSVP capable, they may also use</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 RSVP signaling.=A0 =
This achieves resource reservation on the =
plaintext</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier">=A0=A0 segments of the end-to-end i.e. =
:</FONT></DIV><DIV><FONT class=3D"Apple-style-span" face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 o=A0 from the sender =
to the ingress IPsec gateway and</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 o=A0 from the egress =
IPsec gateway to the receiver.</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 In this use case, =
because the VPN Routers do not support any RSVP</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 specific mechanism, =
the end-to-end RSVP signaling is effectively</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 hidden by the IPsec =
gateways on the cyphertext segment of the end-to-</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 end =
path.</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 As with the =
"Application_Entity-Controlled Proxy" approach =
(defined</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier">=A0=A0 in Section 4.5), the solution here for =
synchronizing RSVP signaling</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 with =
application-level signaling is to rely on an =
application-level</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier">=A0=A0 signaling device that controls an on-path RSVP =
Proxy function.</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier">=A0=A0 However, in the present use case, the RSVP =
Proxies are a component of</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 a cyphertext network =
where all user (bearer) traffic is IPsec</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 encrypted.=A0 This =
has a number of implications including the</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 =
following:</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 1.=A0 encrypted flows =
can not be identified in the cyphertext domain so</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0 =A0 =A0=A0 that network =
nodes can only classify traffic based on IP =
address</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier">=A0 =A0 =A0=A0 and DiffServ Code Points (DSCPs).=A0 As =
a result, only aggregate</FONT></DIV><DIV><FONT class=3D"Apple-style-span"=
 face=3D"Courier">=A0 =A0 =A0=A0 RSVP reservations (such as those =
specified in [RFC3175] or</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0 =A0 =A0=A0 [RFC4860] ) =
can be used.=A0 This is similar to</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0 =A0 =A0=A0 =
[I-D.ietf-tsvwg-vpn-signaled-preemption].</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 2.=A0 Determining the =
RSVP Sender proxy and RSVP receiver Proxy to be</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0 =A0 =A0=A0 used for =
aggregation of a given flow from sender to =
receiver</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier">=A0 =A0 =A0=A0 creates a number of challenges.=A0 =
Details on how this may be</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0 =A0 =A0=A0 achieved are =
beyond the scope of this document.=A0 We observe =
that,</FONT></DIV><DIV><FONT class=3D"Apple-style-span" face=3D"Courier">=A0=
 =A0 =A0=A0 as illustrated in Figure 17, this may be facilitated by a =
network</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier">=A0 =A0 =A0=A0 management interface between the =
application entity and the IPsec</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0 =A0 =A0=A0 gateways.=A0 =
For example, this interface may be used by the</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0 =A0 =A0=A0 application =
entity to obtain information about which IPsec</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0 =A0 =A0=A0 gateway is on =
the path of a given end-to-end flow.=A0 Then, the</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0 =A0 =A0=A0 application =
entity may maintain awareness of which RSVP Proxy =
is</FONT></DIV><DIV><FONT class=3D"Apple-style-span" face=3D"Courier">=A0 =
=A0 =A0=A0 on the cyphertext path between a given pair of IPsec =
gateways.</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier">=A0 =A0 =A0=A0 How such awareness is achieved is beyond =
the scope of this</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier">=A0 =A0 =A0=A0 document.=A0 We simply observe that such =
awareness can be easily</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier">=A0 =A0 =A0=A0 achieved through simple configuration in =
the particular case</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier">=A0 =A0 =A0=A0 where a single (physical or logical) =
Proxy device is fronting a</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0 =A0 =A0=A0 given IPsec =
gateway.=A0 We also observe that when awareness of =
the</FONT></DIV><DIV><FONT class=3D"Apple-style-span" face=3D"Courier">=A0=
=A0 =A0=A0 =A0RSVP Receiver Proxy for a particular egress IPsec gateway =
(or</FONT></DIV><DIV><FONT class=3D"Apple-style-span" face=3D"Courier">=A0=
 =A0 =A0=A0 end-to-end flow) is not available, the aggregate reservation =
may</FONT></DIV><DIV><FONT class=3D"Apple-style-span" face=3D"Courier">=A0=
 =A0 =A0=A0 be signaled by the RSVP Sender Proxy to the destination =
address</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier">=A0 =A0 =A0=A0 of the egress IPsec gateway and then =
proxied by the RSVP Receiver</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0 =A0 =A0=A0 =
Proxy.</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 Different flavors of =
operations are possible in terms of aggregate</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 reservation sizing.=A0 =
For example, the application entity can initiate</FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier">=A0=A0 an aggregate =
reservation of fixed size a priori and then simply =
keep</FONT></DIV><DIV><FONT class=3D"Apple-style-span" face=3D"Courier">=A0=
=A0 count of the bandwidth used by sessions and reject sessions =
that</FONT></DIV><DIV><FONT class=3D"Apple-style-span" face=3D"Courier">=A0=
=A0 would result in excess usage of an aggregate reservation.=A0 =
The</FONT></DIV><DIV><FONT class=3D"Apple-style-span" face=3D"Courier">=A0=
=A0 application entity could also re-size the aggregate reservations on =
a</FONT></DIV><DIV><FONT class=3D"Apple-style-span" face=3D"Courier">=A0=A0=
 session by session basis.=A0 Alternatively, the application =
entity</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier">=A0=A0 could re-size the aggregate reservations in step =
increments typically</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier">=A0=A0 corresponding to the bandwidth requirement of =
multiple sessions.</FONT></DIV><DIV><FONT class=3D"Apple-style-span" =
face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><DIV><FONT =
class=3D"Apple-style-span" face=3D"Courier"><BR =
class=3D"khtml-block-placeholder"></FONT></DIV><FONT =
class=3D"Apple-style-span" =
face=3D"Courier"><BR></FONT></DIV><BR></DIV></BODY></HTML>=

--Apple-Mail-29--825086141--





From tsvwg-bounces@ietf.org Thu Jul 05 13:06:29 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6Umg-0002as-72; Thu, 05 Jul 2007 13:06:26 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I6Umf-0002XJ-Dm
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 05 Jul 2007 13:06:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6Umf-0002Vg-3W
	for tsvwg@ietf.org; Thu, 05 Jul 2007 13:06:25 -0400
Received: from mtagate1.de.ibm.com ([195.212.29.150])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6UmI-0005Ol-JT
	for tsvwg@ietf.org; Thu, 05 Jul 2007 13:06:25 -0400
Received: from d12nrmr1607.megacenter.de.ibm.com
	(d12nrmr1607.megacenter.de.ibm.com [9.149.167.49])
	by mtagate1.de.ibm.com (8.13.8/8.13.8) with ESMTP id l65H62vb097414
	for <tsvwg@ietf.org>; Thu, 5 Jul 2007 17:06:02 GMT
Received: from d12av04.megacenter.de.ibm.com (d12av04.megacenter.de.ibm.com
	[9.149.165.229])
	by d12nrmr1607.megacenter.de.ibm.com (8.13.8/8.13.8/NCO v8.3) with
	ESMTP id l65H615v2097394
	for <tsvwg@ietf.org>; Thu, 5 Jul 2007 19:06:01 +0200
Received: from d12av04.megacenter.de.ibm.com (loopback [127.0.0.1])
	by d12av04.megacenter.de.ibm.com (8.12.11.20060308/8.13.3) with ESMTP
	id l65H61C5012898
	for <tsvwg@ietf.org>; Thu, 5 Jul 2007 19:06:01 +0200
Received: from d12mc102.megacenter.de.ibm.com (d12mc102.megacenter.de.ibm.com
	[9.149.167.114])
	by d12av04.megacenter.de.ibm.com (8.12.11.20060308/8.12.11) with ESMTP
	id l65H603g012854
	for <tsvwg@ietf.org>; Thu, 5 Jul 2007 19:06:01 +0200
From: Julian Satran <Julian_Satran@il.ibm.com>
To: tsvwg@ietf.org
Message-ID: <OFFAA7E857.ED258FD8-ONC225730F.005DEE82-C225730F.005DEE82@il.ibm.com>
Date: Thu, 5 Jul 2007 20:05:59 +0300
X-MIMETrack: Serialize by Router on D12MC102/12/M/IBM(Release 7.0.2HF71 |
	November 3, 2006) at 05/07/2007 20:06:00
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Subject: [Tsvwg] Julian Satran/Haifa/IBM is out of the office.
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org


I will be out of the office starting  05/07/2007 and will not return until
15/07/2007.

I have no access to e-mail. If your message is important  please resend it
close to July 17. For urgent matters you may contact me through my
assistant - Daphne Maor-Belsky.






From tsvwg-bounces@ietf.org Thu Jul 05 18:02:54 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6ZPP-0003Vn-TX; Thu, 05 Jul 2007 18:02:43 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I6ZPP-0003Vi-Es
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 05 Jul 2007 18:02:43 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6ZPP-0003Va-2x
	for tsvwg@ietf.org; Thu, 05 Jul 2007 18:02:43 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I6ZPO-0002o8-RW
	for tsvwg@ietf.org; Thu, 05 Jul 2007 18:02:42 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 05 Jul 2007 18:02:00 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAPsGjUZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,505,1175486400"; 
	d="scan'208"; a="125320423:sNHT3194703578"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l65M1x06007694
	for <tsvwg@ietf.org>; Thu, 5 Jul 2007 18:01:59 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l65M1x6a027795
	for <tsvwg@ietf.org>; Thu, 5 Jul 2007 22:01:59 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 5 Jul 2007 18:01:59 -0400
Received: from jmpolk-wxp.cisco.com ([10.89.16.78]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 5 Jul 2007 18:01:58 -0400
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 05 Jul 2007 17:02:01 -0500
To: tsvwg <tsvwg@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-ID: <XFE-RTP-202e4fDGCl9000002ec@xfe-rtp-202.amer.cisco.com>
X-OriginalArrivalTime: 05 Jul 2007 22:01:58.0782 (UTC)
	FILETIME=[1BC961E0:01C7BF50]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1108; t=1183672919;
	x=1184536919; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jmpolk@cisco.com;
	z=From:=20=22James=20M.=20Polk=22=20<jmpolk@cisco.com>
	|Subject:=20New=20ID=3A=20draft-polk-tsvwg-signaled-domain-id-00
	|Sender:=20 |To:=20tsvwg=20<tsvwg@ietf.org>;
	bh=icHdd6w/t8IQzS+lS4hmF381aPfBc/JuHT6jHtzvC9I=;
	b=JF+3LyjG31n0rREkwZHi7eYc0+/ELBhbn/pkLhXtLIvIMyqhhW7pi3KkZ7IUj+fy2O3lYOrV
	2TrCoTXmaEYUTDu43vJ6+hgC/Es96937VEVbHYOYZbmJkIefMi7b4UPb;
Authentication-Results: rtp-dkim-1; header.From=jmpolk@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: 
Subject: [Tsvwg] New ID: draft-polk-tsvwg-signaled-domain-id-00
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

TSVWG

Here is a new ID we just submitted, creating a new element to be used 
to make domain and/or subdomain CAC decisions based upon. These 
identifiers apply to individual reservation flows, as well as tunnels 
and aggregates.

Comments are appreciated

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-polk-tsvwg-signaled-domain-id-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts
directories.

	Title		: Signaled Domain and Sub-domain Identification Element
	Author(s)	: J. Polk, S. Dhesikan
	Filename	: draft-polk-tsvwg-signaled-domain-id-00.txt
	Pages		: 10
	Date		: 2007-7-5
	
    This document defines a domain and a sub-domain identification
    element for use by signaled policy based admission protocols such as
    Resource ReSerVation Protocol (RSVP) and Common Open Policy Service
    (COPS).  This element identifies the domain and sub-domain to which
    the reservation belongs and is used, along with the PREEMPTION_PRI
    element, to make capacity-based admission control (CAC) decisions.

Thanks
James





From tsvwg-bounces@ietf.org Fri Jul 06 10:08:09 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6oSm-0000Oz-56; Fri, 06 Jul 2007 10:07:12 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I6oSk-0000O1-T2
	for tsvwg-confirm+ok@megatron.ietf.org; Fri, 06 Jul 2007 10:07:10 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6oSk-0000Nt-2F
	for tsvwg@ietf.org; Fri, 06 Jul 2007 10:07:10 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I6oSi-0002xY-Rt
	for tsvwg@ietf.org; Fri, 06 Jul 2007 10:07:09 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 06 Jul 2007 16:06:58 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAKDpjUaQ/uCKh2dsb2JhbACCZIxQAQEJDiw
X-IronPort-AV: i="4.16,508,1175464800"; 
	d="scan'208,217"; a="147420373:sNHT59505784"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l66E6vww015210; 
	Fri, 6 Jul 2007 16:06:57 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l66E6sTC012846; 
	Fri, 6 Jul 2007 14:06:54 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 6 Jul 2007 16:06:54 +0200
Received: from [144.254.53.89] ([144.254.53.89]) by xfe-ams-331.emea.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 6 Jul 2007 16:06:54 +0200
Mime-Version: 1.0 (Apple Message framework v752.3)
References: <E1I400A-0005PX-DQ@stiedprstage1.ietf.org>
Content-Type: multipart/alternative; boundary=Apple-Mail-20--734990203
Message-Id: <CB3E86CE-5A05-43B4-81AC-443B727F14D4@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
Subject: Fwd: [Tsvwg] I-D ACTION:draft-ietf-tsvwg-rsvp-proxy-proto-01.txt 
Date: Fri, 6 Jul 2007 16:03:59 +0200
To: tsvwg tsvwg <tsvwg@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 06 Jul 2007 14:06:54.0201 (UTC)
	FILETIME=[E8253E90:01C7BFD6]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=22815; t=1183730817;
	x=1184594817; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.com>
	|Subject:=20Fwd=3A=20[Tsvwg]=20I-D=20ACTION=3Adraft-ietf-tsvwg-rsvp-proxy
	-proto-01.txt=20 |Sender:=20;
	bh=bxuuTEPAg4FMqMkQiZPZF8YEAR/8Wk6GtJ+30j6pAmE=;
	b=dbkeWMEWG4o2t8XK29LO1ZJN9gzUZQr+jlGQuHaaMxnAOwaOUw7Txt755NKRt9AYQ95bR48B
	fhVmRgxYohx/AyukYyIN2q4NKDvVLrOmSUcQ6RA1RyVzhwuQBxrzkvEh;
Authentication-Results: ams-dkim-1; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: 0.2 (/)
X-Scan-Signature: abb8110dde048486ea2be9c769692569
Cc: Ashok Narayanan <ashokn@cisco.com>,
	Allan GUILLOU <allan.guillou@neufcegetel.fr>,
	Jukka Manner MJ <jmanner@cs.Helsinki.FI>, hemant.malik@airtel.in
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org


--Apple-Mail-20--734990203
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

Hello,

This updated version of rsvp-proxy-proto addresses all the comments  
received to date including:
	* outcome of the list discussion with John Drake: added new section  
"3.1.4 Use of PathErr by Regular Receivers
	* outcome of discussion with Lou Berger: added new section "3.1.3  
Use of Path_State_Removed Flag"
	* as announced/discussed on the list: description of a an new  
optional method for sender notification based on NOTIFY: added new  
section "3.2 Sender Notification via Notify Message"

This version also includes the following additional changes:
	* wrote full-blown Security Considerations
	* Completed the IANA considerations section.
	* added specification for Error Value (for "Unrecoverable Receiver  
Proxy Error" Error Code)
	* added text on handling of InPlace" flag

So, from the authors viewpoint, the document is now pretty much ready.

We welcome feedback before we propose to move this document further  
in teh process.

Cheers

Francois

Begin forwarded message:

> From: Internet-Drafts@ietf.org
> Date: 28 June 2007 21:50:02 GMT+02:00
> To: i-d-announce@ietf.org
> Cc: tsvwg@ietf.org
> Subject: [Tsvwg] I-D ACTION:draft-ietf-tsvwg-rsvp-proxy-proto-01.txt
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Transport Area Working Group  
> Working Group of the IETF.
>
> 	Title		: RSVP Extensions for Path-Triggered RSVP Receiver Proxy
> 	Author(s)	: F. Le Faucheur, et al.
> 	Filename	: draft-ietf-tsvwg-rsvp-proxy-proto-01.txt
> 	Pages		: 25
> 	Date		: 2007-6-28
> 	
> RSVP signaling can be used to make end-to-end resource reservations
>    in an IP network in order to guarantee the QoS required by certain
>    flows.  With conventional RSVP, both the data sender and  
> receiver of
>    a given flow take part in RSVP signaling.  Yet, there are many use
>    cases where resource reservation is required, but the receiver, the
>    sender, or both, is not RSVP-capable.  Where the receiver is not
>    RSVP-capable, an RSVP router may behave as an RSVP Receiver Proxy
>    thereby performing RSVP signaling on behalf of the receiver.  This
>    allows resource reservations to be established on the segment of  
> the
>    end-to-end path from the sender to the RSVP Receiver Proxy.   
> However,
>    as discussed in the companion document presenting RSVP Proxy
>    approaches, RSVP extensions are needed to facilitate operations  
> with
>    an RSVP Receiver Proxy whose signaling is triggered by receipt of
>    RSVP Path messages from the sender.  This document specifies these
>    extensions.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rsvp-proxy- 
> proto-01.txt
>
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body of
> the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>
> Internet-Drafts are also available by anonymous FTP. Login with the
> username "anonymous" and a password of your e-mail address. After
> logging in, type "cd internet-drafts" and then
> "get draft-ietf-tsvwg-rsvp-proxy-proto-01.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-tsvwg-rsvp-proxy-proto-01.txt".
> 	
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> Content-Type: text/plain
> Content-ID: <2007-6-28132603.I-D@ietf.org>
>


--Apple-Mail-20--734990203
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; ">Hello,<DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>This updated version of =
rsvp-proxy-proto addresses all the comments received to date =
including:</DIV><DIV><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>* outcome of the list discussion =
with John Drake: added new section "3.1.4 Use of PathErr by Regular =
Receivers</DIV><DIV><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>* outcome of discussion with Lou =
Berger: added new section "3.1.3 Use of Path_State_Removed =
Flag"</DIV><DIV><SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>* as announced/discussed on the list: description of a an new =
optional method for sender notification based on NOTIFY: added new =
section "3.2 Sender Notification via Notify Message"</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>This version also includes =
the following additional changes:</DIV><DIV><SPAN class=3D"Apple-tab-span"=
 style=3D"white-space:pre">	</SPAN>* wrote full-blown Security =
Considerations</DIV><DIV><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>* Completed the IANA =
considerations section.</DIV><DIV><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>* added specification for Error =
Value (for "Unrecoverable Receiver Proxy Error" Error =
Code)</DIV><DIV><SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>* added text on handling of InPlace" flag</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>So, from the authors =
viewpoint, the document is now pretty much ready.=A0</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>We welcome feedback before =
we propose to move this document further in teh process.</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Cheers</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Francois</DIV><DIV><DIV><BR><=
DIV>Begin forwarded message:</DIV><BR =
class=3D"Apple-interchange-newline"><BLOCKQUOTE type=3D"cite"><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 18.0px Helvetica; color: #000000"><B>From: =
</B></FONT><FONT face=3D"Helvetica" size=3D"5" style=3D"font: 18.0px =
Helvetica"><A =
href=3D"mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</A></FON=
T></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" =
color=3D"#000000" style=3D"font: 18.0px Helvetica; color: =
#000000"><B>Date: </B></FONT><FONT face=3D"Helvetica" size=3D"5" =
style=3D"font: 18.0px Helvetica">28 June 2007 21:50:02 =
GMT+02:00</FONT></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><FONT face=3D"Helvetica" =
size=3D"5" color=3D"#000000" style=3D"font: 18.0px Helvetica; color: =
#000000"><B>To: </B></FONT><FONT face=3D"Helvetica" size=3D"5" =
style=3D"font: 18.0px Helvetica"><A =
href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</A></FONT></DI=
V><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 18.0px Helvetica; color: #000000"><B>Cc: </B></FONT><FONT =
face=3D"Helvetica" size=3D"5" style=3D"font: 18.0px Helvetica"><A =
href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</A></FONT></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 18.0px Helvetica; color: #000000"><B>Subject: =
</B></FONT><FONT face=3D"Helvetica" size=3D"5" style=3D"font: 18.0px =
Helvetica"><B>[Tsvwg] I-D =
ACTION:draft-ietf-tsvwg-rsvp-proxy-proto-01.txt<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></B></FONT></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV> <DIV style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">A New =
Internet-Draft is available from the on-line Internet-Drafts<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">directories.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">This draft is a work item of the =
Transport Area Working Group Working Group of the IETF.</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>Title<SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN><SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>: RSVP Extensions for Path-Triggered RSVP Receiver =
Proxy</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>Author(s)<SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>: F. Le =
Faucheur, et al.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>Filename<SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>: =
draft-ietf-tsvwg-rsvp-proxy-proto-01.txt</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>Pages<SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN><SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>: 25</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>Date<SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>: 2007-6-28</DIV><P =
style=3D"margin: 0.0px 0.0px 0.0px 0.0px; min-height: 14.0px"><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN><BR =
class=3D"khtml-block-placeholder"></P><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">RSVP =
signaling can be used to make end-to-end resource reservations</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0=A0 =
</SPAN>in an IP network in order to guarantee the QoS required by =
certain</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>flows.<SPAN =
class=3D"Apple-converted-space">=A0 </SPAN>With conventional RSVP, both =
the data sender and receiver of</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>a given flow take part in =
RSVP signaling.<SPAN class=3D"Apple-converted-space">=A0 </SPAN>Yet, =
there are many use</DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>cases where resource =
reservation is required, but the receiver, the</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0=A0 =
</SPAN>sender, or both, is not RSVP-capable.<SPAN =
class=3D"Apple-converted-space">=A0 </SPAN>Where the receiver is =
not</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>RSVP-capable, an RSVP =
router may behave as an RSVP Receiver Proxy</DIV><DIV style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>thereby performing RSVP =
signaling on behalf of the receiver.<SPAN =
class=3D"Apple-converted-space">=A0 </SPAN>This</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0=A0 =
</SPAN>allows resource reservations to be established on the segment of =
the</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>end-to-end path from the =
sender to the RSVP Receiver Proxy.<SPAN class=3D"Apple-converted-space">=A0=
 </SPAN>However,</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>as discussed in the =
companion document presenting RSVP Proxy</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>approaches, RSVP =
extensions are needed to facilitate operations with</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0=A0 =
</SPAN>an RSVP Receiver Proxy whose signaling is triggered by receipt =
of</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0=A0 =
</SPAN>RSVP Path messages from the sender.<SPAN =
class=3D"Apple-converted-space">=A0 </SPAN>This document specifies =
these</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>extensions.</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">A URL =
for this Internet-Draft is:</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A =
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rsvp-proxy-pr=
oto-01.txt">http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rsvp-prox=
y-proto-01.txt</A></DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">To remove yourself from the I-D =
Announcement list, send a message to<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A =
href=3D"mailto:i-d-announce-request@ietf.org">i-d-announce-request@ietf.or=
g</A> with the word unsubscribe in the body of<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">the =
message.<SPAN class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">You can also visit <A =
href=3D"https://www1.ietf.org/mailman/listinfo/I-D-announce">https://www1.=
ietf.org/mailman/listinfo/I-D-announce</A><SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">to =
change your subscription settings.</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Internet-Drafts are also =
available by anonymous FTP. Login with the<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">username =
"anonymous" and a password of your e-mail address. After<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">logging =
in, type "cd internet-drafts" and then<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">"get =
draft-ietf-tsvwg-rsvp-proxy-proto-01.txt".</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">A list of =
Internet-Drafts directories can be found in</DIV><DIV style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A =
href=3D"http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</=
A><SPAN class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">or <A =
href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/ietf=
/1shadow-sites.txt</A></DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Internet-Drafts can also be =
obtained by e-mail.</DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Send a message to:</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN><A =
href=3D"mailto:mailserv@ietf.org">mailserv@ietf.org</A>.</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">In the body type:</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>"FILE =
/internet-drafts/draft-ietf-tsvwg-rsvp-proxy-proto-01.txt".</DIV><P =
style=3D"margin: 0.0px 0.0px 0.0px 0.0px; min-height: 14.0px"><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN><BR =
class=3D"khtml-block-placeholder"></P><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">NOTE:<SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>The mail =
server at ietf.org can return the document in</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>MIME-encoded form by using the =
"mpack" utility.<SPAN class=3D"Apple-converted-space">=A0 </SPAN>To use =
this</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>feature, insert the command =
"ENCODING mime" before the "FILE"</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>command.<SPAN class=3D"Apple-converted-space">=A0 </SPAN>To =
decode the response(s), you will need "munpack" or</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>a MIME-compliant mail =
reader.<SPAN class=3D"Apple-converted-space">=A0 </SPAN>Different =
MIME-compliant mail readers</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>exhibit =
different behavior, especially when dealing with</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>"multipart" MIME messages (i.e. =
documents which have been split</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>up into =
multiple messages), so check your local documentation on</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>how to manipulate these =
messages.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Below is the data which will enable a MIME compliant =
mail reader</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">implementation to automatically =
retrieve the ASCII version of the</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">Internet-Draft.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Content-Type: =
text/plain</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Content-ID: &lt;<A =
href=3D"mailto:2007-6-28132603.I-D@ietf.org">2007-6-28132603.I-D@ietf.org<=
/A>&gt;</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV> =
</BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>=

--Apple-Mail-20--734990203--





From tsvwg-bounces@ietf.org Fri Jul 06 14:34:40 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6sdb-00038I-6k; Fri, 06 Jul 2007 14:34:39 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I6sda-00037d-2s
	for tsvwg-confirm+ok@megatron.ietf.org; Fri, 06 Jul 2007 14:34:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6sdZ-00037C-Oo
	for tsvwg@ietf.org; Fri, 06 Jul 2007 14:34:37 -0400
Received: from mta4.iomartmail.com ([62.128.193.154])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6sdV-00049V-AP
	for tsvwg@ietf.org; Fri, 06 Jul 2007 14:34:37 -0400
Received: from mta4.iomartmail.com (localhost.localdomain [127.0.0.1])
	by mta4.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id
	l66IYQUd024148; Fri, 6 Jul 2007 19:34:26 +0100
Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com
	[81.140.15.32]) (authenticated bits=0)
	by mta4.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id
	l66IYMNe024033; Fri, 6 Jul 2007 19:34:26 +0100
Message-ID: <02d001c7bffc$450d93d0$0200a8c0@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "tsvwg" <tsvwg@ietf.org>, "James M. Polk" <jmpolk@cisco.com>
References: <XFE-RTP-202e4fDGCl9000002ec@xfe-rtp-202.amer.cisco.com>
Subject: Re: [Tsvwg] New ID: draft-polk-tsvwg-signaled-domain-id-00
Date: Fri, 6 Jul 2007 19:34:16 +0100
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: 
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi James,

I think it would be helpful if you added some text explaining what a 
"domain" is. This may be obvious to the cognoscenti, but coming from 
outside, I initially wondered if you were referring specifically to ASes. 
Then I saw the reference to 3181 and decided you meant "policy domain", and 
then I got to the IANA section and wondered if you are creating a whole new 
thing.

Thanks,
Adrian
----- Original Message ----- 
From: "James M. Polk" <jmpolk@cisco.com>
To: "tsvwg" <tsvwg@ietf.org>
Sent: Thursday, July 05, 2007 11:02 PM
Subject: [Tsvwg] New ID: draft-polk-tsvwg-signaled-domain-id-00


> TSVWG
>
> Here is a new ID we just submitted, creating a new element to be used to 
> make domain and/or subdomain CAC decisions based upon. These identifiers 
> apply to individual reservation flows, as well as tunnels and aggregates.
>
> Comments are appreciated
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-polk-tsvwg-signaled-domain-id-00.txt
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
> Title : Signaled Domain and Sub-domain Identification Element
> Author(s) : J. Polk, S. Dhesikan
> Filename : draft-polk-tsvwg-signaled-domain-id-00.txt
> Pages : 10
> Date : 2007-7-5
>
>    This document defines a domain and a sub-domain identification
>    element for use by signaled policy based admission protocols such as
>    Resource ReSerVation Protocol (RSVP) and Common Open Policy Service
>    (COPS).  This element identifies the domain and sub-domain to which
>    the reservation belongs and is used, along with the PREEMPTION_PRI
>    element, to make capacity-based admission control (CAC) decisions.
>
> Thanks
> James
>
>
> 







From tsvwg-bounces@ietf.org Fri Jul 06 17:37:35 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6vUa-00086O-FO; Fri, 06 Jul 2007 17:37:32 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I6vUZ-00086I-0m
	for tsvwg-confirm+ok@megatron.ietf.org; Fri, 06 Jul 2007 17:37:31 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6vUY-00086A-LU
	for tsvwg@ietf.org; Fri, 06 Jul 2007 17:37:30 -0400
Received: from mail130.messagelabs.com ([216.82.250.163])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1I6vUY-0006Ua-2J
	for tsvwg@ietf.org; Fri, 06 Jul 2007 17:37:30 -0400
X-VirusChecked: Checked
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-14.tower-130.messagelabs.com!1183757832!5244694!1
X-StarScan-Version: 5.5.12.11; banners=-,-,-
X-Originating-IP: [20.137.52.151]
Received: (qmail 14387 invoked from network); 6 Jul 2007 21:37:13 -0000
Received: from amer-mta07.csc.com (HELO amer-mta07.csc.com) (20.137.52.151)
	by server-14.tower-130.messagelabs.com with AES256-SHA encrypted SMTP;
	6 Jul 2007 21:37:13 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245])
	by amer-mta07.csc.com (Switch-3.1.6/Switch-3.1.7) with ESMTP id
	l66LbOuv012834; Fri, 6 Jul 2007 17:37:24 -0400 (EDT)
In-Reply-To: <02d001c7bffc$450d93d0$0200a8c0@your029b8cecfe>
To: Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: [Tsvwg] New ID: draft-polk-tsvwg-signaled-domain-id-00
MIME-Version: 1.0
X-Mailer: Lotus Notes 652HF83 November 04, 2004
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OF0929B7E6.548C4260-ON85257310.00760F2D-85257310.0076C1D2@csc.com>
Date: Fri, 6 Jul 2007 17:37:08 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 7.0.2FP1
	HF180|March 29, 2007) at 07/06/2007 05:35:51 PM,
	Serialize complete at 07/06/2007 05:35:51 PM
Content-Type: multipart/alternative;
	boundary="=_alternative 0076BF7385257310_="
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2a76bcd37b1c8a21336eb0a1ea6bbf48
Cc: "James M. Polk" <jmpolk@cisco.com>, tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

This is a multipart message in MIME format.
--=_alternative 0076BF7385257310_=
Content-Type: text/plain; charset="US-ASCII"

Adrian,

As I understand it, it is analogous to the MLPP Service Domain in SS7. The 
"service domain" is a purely logical structure which identifies the 
"closed community" of calls which are permitted to preempt each other.  A 
high priority call can preempt a lower priority call IN THE SAME SERVICE 
DOMAIN, but cannot preempt a lower priority call which is part of a 
DIFFERENT SERVICE DOMAIN.

You can have multiple "service domains" within a single AS.  You can have 
multiple "service domains" within a single policy domain.

Janet

"Adrian Farrel" <adrian@olddog.co.uk> wrote on 07/06/2007 02:34:16 PM:

> Hi James,
> 
> I think it would be helpful if you added some text explaining what a 
> "domain" is. This may be obvious to the cognoscenti, but coming from 
> outside, I initially wondered if you were referring specifically to 
ASes. 
> Then I saw the reference to 3181 and decided you meant "policy domain", 
and 
> then I got to the IANA section and wondered if you are creating a whole 
new 
> thing.
> 
> Thanks,
> Adrian
> ----- Original Message ----- 
> From: "James M. Polk" <jmpolk@cisco.com>
> To: "tsvwg" <tsvwg@ietf.org>
> Sent: Thursday, July 05, 2007 11:02 PM
> Subject: [Tsvwg] New ID: draft-polk-tsvwg-signaled-domain-id-00
> 
> 
> > TSVWG
> >
> > Here is a new ID we just submitted, creating a new element to be used 
to 
> > make domain and/or subdomain CAC decisions based upon. These 
identifiers 
> > apply to individual reservation flows, as well as tunnels and 
aggregates.
> >
> > Comments are appreciated
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-polk-tsvwg-signaled-
> domain-id-00.txt
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> >
> > Title : Signaled Domain and Sub-domain Identification Element
> > Author(s) : J. Polk, S. Dhesikan
> > Filename : draft-polk-tsvwg-signaled-domain-id-00.txt
> > Pages : 10
> > Date : 2007-7-5
> >
> >    This document defines a domain and a sub-domain identification
> >    element for use by signaled policy based admission protocols such 
as
> >    Resource ReSerVation Protocol (RSVP) and Common Open Policy Service
> >    (COPS).  This element identifies the domain and sub-domain to which
> >    the reservation belongs and is used, along with the PREEMPTION_PRI
> >    element, to make capacity-based admission control (CAC) decisions.
> >
> > Thanks
> > James
> >
> >
> > 
> 
> 
> 
> 

--=_alternative 0076BF7385257310_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif"><br>
Adrian,</font>
<br><font size=2 face="sans-serif"><br>
As I understand it, it is analogous to the MLPP Service Domain in SS7.
&nbsp;The &quot;service domain&quot; is a purely logical structure which
identifies the &quot;closed community&quot; of calls which are permitted
to preempt each other. &nbsp;A high priority call can preempt a lower priority
call IN THE SAME SERVICE DOMAIN, but cannot preempt a lower priority call
which is part of a DIFFERENT SERVICE DOMAIN.</font>
<br>
<br><font size=2 face="sans-serif">You can have multiple &quot;service
domains&quot; within a single AS. &nbsp;You can have multiple &quot;service
domains&quot; within a single policy domain.</font>
<br>
<br><font size=2 face="sans-serif">Janet</font>
<br>
<br><font size=2><tt>&quot;Adrian Farrel&quot; &lt;adrian@olddog.co.uk&gt;
wrote on 07/06/2007 02:34:16 PM:<br>
<br>
&gt; Hi James,<br>
&gt; <br>
&gt; I think it would be helpful if you added some text explaining what
a <br>
&gt; &quot;domain&quot; is. This may be obvious to the cognoscenti, but
coming from <br>
&gt; outside, I initially wondered if you were referring specifically to
ASes. <br>
&gt; Then I saw the reference to 3181 and decided you meant &quot;policy
domain&quot;, and <br>
&gt; then I got to the IANA section and wondered if you are creating a
whole new <br>
&gt; thing.<br>
&gt; <br>
&gt; Thanks,<br>
&gt; Adrian<br>
&gt; ----- Original Message ----- <br>
&gt; From: &quot;James M. Polk&quot; &lt;jmpolk@cisco.com&gt;<br>
&gt; To: &quot;tsvwg&quot; &lt;tsvwg@ietf.org&gt;<br>
&gt; Sent: Thursday, July 05, 2007 11:02 PM<br>
&gt; Subject: [Tsvwg] New ID: draft-polk-tsvwg-signaled-domain-id-00<br>
&gt; <br>
&gt; <br>
&gt; &gt; TSVWG<br>
&gt; &gt;<br>
&gt; &gt; Here is a new ID we just submitted, creating a new element to
be used to <br>
&gt; &gt; make domain and/or subdomain CAC decisions based upon. These
identifiers <br>
&gt; &gt; apply to individual reservation flows, as well as tunnels and
aggregates.<br>
&gt; &gt;<br>
&gt; &gt; Comments are appreciated<br>
&gt; &gt;<br>
&gt; &gt; A URL for this Internet-Draft is:<br>
&gt; &gt; http://www.ietf.org/internet-drafts/draft-polk-tsvwg-signaled-<br>
&gt; domain-id-00.txt<br>
&gt; &gt;<br>
&gt; &gt; A New Internet-Draft is available from the on-line Internet-Drafts<br>
&gt; &gt; directories.<br>
&gt; &gt;<br>
&gt; &gt; Title : Signaled Domain and Sub-domain Identification Element<br>
&gt; &gt; Author(s) : J. Polk, S. Dhesikan<br>
&gt; &gt; Filename : draft-polk-tsvwg-signaled-domain-id-00.txt<br>
&gt; &gt; Pages : 10<br>
&gt; &gt; Date : 2007-7-5<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp;This document defines a domain and a sub-domain
identification<br>
&gt; &gt; &nbsp; &nbsp;element for use by signaled policy based admission
protocols such as<br>
&gt; &gt; &nbsp; &nbsp;Resource ReSerVation Protocol (RSVP) and Common
Open Policy Service<br>
&gt; &gt; &nbsp; &nbsp;(COPS). &nbsp;This element identifies the domain
and sub-domain to which<br>
&gt; &gt; &nbsp; &nbsp;the reservation belongs and is used, along with
the PREEMPTION_PRI<br>
&gt; &gt; &nbsp; &nbsp;element, to make capacity-based admission control
(CAC) decisions.<br>
&gt; &gt;<br>
&gt; &gt; Thanks<br>
&gt; &gt; James<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
</tt></font>
--=_alternative 0076BF7385257310_=--





From tsvwg-bounces@ietf.org Sun Jul 08 16:50:16 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7dhq-0000Ep-FN; Sun, 08 Jul 2007 16:50:10 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I7dhp-0000EF-BO
	for tsvwg-confirm+ok@megatron.ietf.org; Sun, 08 Jul 2007 16:50:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7dhp-0000Ds-1O
	for tsvwg@ietf.org; Sun, 08 Jul 2007 16:50:09 -0400
Received: from smtpout.mac.com ([17.250.248.174])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7dhk-0006eR-J8
	for tsvwg@ietf.org; Sun, 08 Jul 2007 16:50:09 -0400
Received: from mac.com (smtpin05-en2 [10.13.10.150])
	by smtpout.mac.com (Xserve/smtpout04/MantshX 4.0) with ESMTP id
	l68KnhSt005915; Sun, 8 Jul 2007 13:49:43 -0700 (PDT)
Received: from [192.168.1.64] (adsl-70-132-1-225.dsl.snfc21.sbcglobal.net
	[70.132.1.225]) (authenticated bits=0)
	by mac.com (Xserve/smtpin05/MantshX 4.0) with ESMTP id l68KnfLs026883; 
	Sun, 8 Jul 2007 13:49:41 -0700 (PDT)
In-Reply-To: <E1I7b8n-0007Ot-TZ@palace.statslab.cam.ac.uk>
References: <E1I7b8n-0007Ot-TZ@palace.statslab.cam.ac.uk>
Mime-Version: 1.0 (Apple Message framework v624)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <c80bf8a6242f6445ff9c0a7b8a121ec8@mac.com>
Content-Transfer-Encoding: 7bit
From: Sally Floyd <sallyfloyd@mac.com>
Date: Sun, 8 Jul 2007 13:49:41 -0700
To: Frank Kelly <F.P.Kelly@statslab.cam.ac.uk>
X-Mailer: Apple Mail (2.624)
X-Brightmail-Tracker: AAAAAA==
X-Brightmail-scanned: yes
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: tsvwg@ietf.org, mallman@icir.org
Subject: [Tsvwg] Re: RTT fairness
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Frank -

> A quick comment prompted by a paragraph in
> "Comments on the Usefulness of Simple Best-Effort Traffic"
> http://www.icir.org/floyd/papers/draft-floyd-tsvwg-besteffort-00b.txt
>
> The paragraph reads
> "RTT-fairness: What is the desired relationship between flow
> bandwidth and round-trip times, for best-effort traffic?  As shown in
> Section 3.3 of [FJ92], it would be straightforward to modify TCP's
> congestion control so that flows with similar packet drop rates
> but different round-trip times would receive roughly the same
> throughput."
>
> I don't think it would be that straightforward!
> There would be an impact on the stability or speed of convergence
> of the control loop: the modification in [FJ92] would, I think,
> lead to instability on routes where the ratio RTT/rate is large,
> or convergence that is slower than necessary on routes
> where the ratio is small. More detail on why I think this is in
> Section 5.1 of
> "Fairness and stability of end-to-end congestion control"
> http://www.statslab.cam.ac.uk/~frank/PAPERS/fse2ecc.html

Just to be clear, I think it would be a *terrible* idea to make
the change in Section 3.3 of [FJ92], towards long-RTT and
short-RTT flows trying to get the same throughput.  [FJ92]
*never* recommended the change - it just noted how one
would remove the RTT-bias if one wanted to.  It goes on to
say the following"

"There are many open questions concerning alternatives to the TCP
window modification algorithms. If the goal is for each connection
to increase its rate by c pkts/sec each second, how do we choose c?
What would be the impact of connections with large maximum windows
increasing their window much more rapidly than they do now?
...
And the ultimate difficult question: What is the meaning of fair?
At the moment, this section is intended only to suggest that the
current network bias in favor of connections with shorter roundtrip
times is a result of the TCP window increase algorithm, and not of
the performance of Random Drop or of Drop Tail gateways."

I have on my web page "http://www.icir.org/floyd/papers.html",
in the list of internet-drafts on my TODO list, a draft
entitled "Why RTT-Fairness would be Bad for Congestion Control",
along with an abstract, at
"http://www.icir.org/floyd/papers/draft-floyd-tmrg-rtt-fairness 
-00a.txt".

I might or might not ever make it to finish that draft, but if I do,
I will certainly add a pointer to your paper on
"Fairness and stability of end-to-end congestion control".

- Sally
http://www.icir.org/floyd/






From tsvwg-bounces@ietf.org Mon Jul 09 05:50:11 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7psb-0006ZN-CJ; Mon, 09 Jul 2007 05:50:05 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I7psY-0006Z3-71
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 09 Jul 2007 05:50:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7psX-0006Yv-Pf; Mon, 09 Jul 2007 05:50:01 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I7psX-0001De-Fj; Mon, 09 Jul 2007 05:50:01 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 6FC963290A;
	Mon,  9 Jul 2007 09:50:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I7psX-0004oc-Bu; Mon, 09 Jul 2007 05:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I7psX-0004oc-Bu@stiedprstage1.ietf.org>
Date: Mon, 09 Jul 2007 05:50:01 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: tsvwg@ietf.org
Subject: [Tsvwg] I-D Action:draft-ietf-tsvwg-udp-guidelines-02.txt 
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Transport Area Working Group Working Group of the IETF.

                                                                                           
        Title           : UDP Usage Guidelines for Application Designers
        Author(s)       : L. Eggert, G. Fairhurst
        Filename        : draft-ietf-tsvwg-udp-guidelines-02.txt
        Pages           : 15
        Date            : 2007-07-09
                                                                                           
The User Datagram Protocol (UDP) provides a minimal, message-passing
transport that has no inherent congestion control mechanisms.
Because congestion control is critical to the stable operation of the
Internet, applications and upper-layer protocols that choose to use
UDP as an Internet transport must employ mechanisms to prevent
congestion collapse and establish some degree of fairness with
concurrent traffic.  This document provides guidelines on the use of
UDP for the designers of such applications and upper-layer protocols
that cover congestion-control and other topics, including message
sizes, reliability, checksums and middlebox traversal.
                                                                                           
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-udp-guidelines-02.txt
                                                                                           
To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.
                                                                                           
                                                                                           
Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
        "get draft-ietf-tsvwg-udp-guidelines-02.txt".
                                                                                           
A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
                                                                                           
                                                                                           
Internet-Drafts can also be obtained by e-mail.
                                                                                           
Send a message to:
        mailserv@ietf.org.
In the body type:
        "FILE /internet-drafts/draft-ietf-tsvwg-udp-guidelines-02.txt".
                                                                                           
NOTE:   The mail server at ietf.org can return the document in
        MIME-encoded form by using the "mpack" utility.  To use this
        feature, insert the command "ENCODING mime" before the "FILE"
        command.  To decode the response(s), you will need "munpack" or
        a MIME-compliant mail reader.  Different MIME-compliant mail readers
        exhibit different behavior, especially when dealing with
        "multipart" MIME messages (i.e. documents which have been split
        up into multiple messages), so check your local documentation on
        how to manipulate these messages.
                                                                                           
                                                                                           
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
                                                                                           
--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"
Content-Type: text/plain
Content-ID: <2007-07-09054927.I-D@ietf.org>


ENCODING mime
FILE /internet-drafts/draft-ietf-tsvwg-udp-guidelines-02.txt
                                                                                           
--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-tsvwg-udp-guidelines-02.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"
Content-Type: text/plain
Content-ID: <2007-07-09054927.I-D\@ietf.org>



--OtherAccess--
                                                                                           
--NextPart--





From tsvwg-bounces@ietf.org Mon Jul 09 08:14:29 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7s8B-0001Bf-AD; Mon, 09 Jul 2007 08:14:19 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I7bBL-0000Kv-GX
	for tsvwg-confirm+ok@megatron.ietf.org; Sun, 08 Jul 2007 14:08:27 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I7bBL-0000JW-6g
	for tsvwg@ietf.org; Sun, 08 Jul 2007 14:08:27 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7b9c-0004MK-91
	for tsvwg@ietf.org; Sun, 08 Jul 2007 14:06:40 -0400
Received: from palace.statslab.cam.ac.uk ([131.111.20.12])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7b9N-000119-VK
	for tsvwg@ietf.org; Sun, 08 Jul 2007 14:06:40 -0400
Received: from frank by palace.statslab.cam.ac.uk with local (Exim 4.50)
	id 1I7b8n-0007Ot-TZ; Sun, 08 Jul 2007 19:05:49 +0100
To: rbriscoe@jungle.bt.co.uk, mallman@icir.org, sallyfloyd@mac.com
Date: Sun, 8 Jul 2007 19:05:49 +0100 (BST)
X-Mailer: ELM [version 2.4ME+ PL95 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
Message-Id: <E1I7b8n-0007Ot-TZ@palace.statslab.cam.ac.uk>
From: Frank Kelly <F.P.Kelly@statslab.cam.ac.uk>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
X-TMDA-Confirmed: Sun, 08 Jul 2007 14:08:27 -0400
X-Mailman-Approved-At: Mon, 09 Jul 2007 08:14:16 -0400
Cc: tsvwg@ietf.org
Subject: [Tsvwg] RTT fairness
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Mark, Sally, Bob

A quick comment prompted by a paragraph in
"Comments on the Usefulness of Simple Best-Effort Traffic"
http://www.icir.org/floyd/papers/draft-floyd-tsvwg-besteffort-00b.txt

The paragraph reads
"RTT-fairness: What is the desired relationship between flow
bandwidth and round-trip times, for best-effort traffic?  As shown in
Section 3.3 of [FJ92], it would be straightforward to modify TCP's
congestion control so that flows with similar packet drop rates
but different round-trip times would receive roughly the same
throughput."

I don't think it would be that straightforward!
There would be an impact on the stability or speed of convergence 
of the control loop: the modification in [FJ92] would, I think, 
lead to instability on routes where the ratio RTT/rate is large, 
or convergence that is slower than necessary on routes
where the ratio is small. More detail on why I think this is in
Section 5.1 of 
"Fairness and stability of end-to-end congestion control"
http://www.statslab.cam.ac.uk/~frank/PAPERS/fse2ecc.html

Frank







From tsvwg-bounces@ietf.org Mon Jul 09 10:20:33 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7u6G-0003t2-Jw; Mon, 09 Jul 2007 10:20:28 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I7u6F-0003sm-8i
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 09 Jul 2007 10:20:27 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7u6E-0003sU-Ph; Mon, 09 Jul 2007 10:20:26 -0400
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I7u67-0000Bx-S1; Mon, 09 Jul 2007 10:20:26 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l69EJnX8014992; Mon, 9 Jul 2007 17:19:57 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 9 Jul 2007 17:19:49 +0300
Received: from mgw-int01.ntc.nokia.com ([172.21.143.96]) by
	esebh104.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Mon, 9 Jul 2007 17:19:49 +0300
Received: from [172.21.34.250] (esdhcp034250.research.nokia.com
	[172.21.34.250])
	by mgw-int01.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l69EJm3Q010061; Mon, 9 Jul 2007 17:19:48 +0300
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <7C820D53-0415-4A29-856E-624E643D2A2E@nokia.com>
References: <26B285A9-3D4C-43B1-9C32-37EBC4AF39BE@nokia.com><0260FF1D-E29B-4D91-991D-612E77F53970@nokia.com>
	<36B3B805-BCD5-4490-9F5F-87BC56FC5453@nokia.com>
	<7C820D53-0415-4A29-856E-624E643D2A2E@nokia.com>
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-34--474849771;
	protocol="application/pkcs7-signature"
Message-Id: <3B3EC442-3C31-4785-A6B2-44064C00BF17@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
Subject: Re: [Iccrg] Re: [Tsvwg] Re: [tsv-area] consensus call: bringing new
	congestion control to the IETF
Date: Mon, 9 Jul 2007 17:19:40 +0300
To: TSV Area <tsv-area@ietf.org>, iccrg <iccrg@cs.ucl.ac.uk>,
	tsvwg WG <tsvwg@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 09 Jul 2007 14:19:49.0897 (UTC)
	FILETIME=[35BC4F90:01C7C234]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: 
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org


--Apple-Mail-34--474849771
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

On 2007-6-14, at 18:02, ext Lars Eggert wrote:
> This ION has since been discussed by the IESG and several changes  
> have been suggested that I have rolled into a new revision. Mostly,  
> these changes clarify that the expert review in the ICCRG that the  
> ION describes is a mechanism that the transport ADs are free to  
> employ anyway for documents that the area produces. It only  
> clarifies that for new congestion control schemes, the ADs _will_  
> request such an expert review.
>
> I'd like to double-check that the area still has consensus on the  
> revised ION, before I bring it back to the IESG for final approval.  
> Please send comments by next Friday, June 22.

FYI, the IESG has approved this ION during the last telechat.

Lars
--Apple-Mail-34--474849771
Content-Transfer-Encoding: base64
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGQDCCAvkw
ggJioAMCAQICEGtxkLFHQu1g67hlmYfwPuIwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ
ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA3MDEwNDE2MTE1NFoXDTA4MDEwNDE2MTE1
NFowXDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVnZ2Vy
dDEkMCIGCSqGSIb3DQEJARYVbGFycy5lZ2dlcnRAbm9raWEuY29tMIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEA26hjntVPZMiwh4d8tyuk9KiucvG92BVUGArk5zO1jhmq7tLFgU1mqcIg
VGumfQqjkAzIuh83kxIiqBrB05Wvxp85apwt4sUCvzMe8mQWzZZZYp0rBzwpOj+VC5pxsMRYtYW+
BaTFBEmvFr7D7C7roZUk0lDppS5SZFs4SQbEe9ykB9aeUf1iTiw2+ikyP2+JEYto14WYCoxFWbms
FbQ1uaaK+yn1WH2YHhyMfi0IOxuT0jtbsngjHJMpWIqq334zBhj+rPSUug47YBHr41FCDMHbbbjv
WbyTyDYneOW3WY8LY8bGWVlAknQGB7lgduShe6e0RI/7SL/VE6X27lM9LwIDAQABozIwMDAgBgNV
HREEGTAXgRVsYXJzLmVnZ2VydEBub2tpYS5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUF
AAOBgQCx3nxxTg/WowobVTRXBiXUEEZj4LBiunWbuAnR0UbJIgijvq3JbiJvZo2gUGiW9LPaHSBz
4oxT1VR/S/6O0a4e87oV5cOQm6ReB68o9rDfUzxHTwoCfv2wwMwBrXyzQMjyQK4Lt8siV41gmZpm
rSXMhjTJdd9uYYNoZKQLq+VM+TCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJ
BgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgG
A1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMg
RGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3
DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3
MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5
KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTCBnzAN
BgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9
fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+
uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMB
Af8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3
dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgG
A1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcP
f6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH
2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8x
ggMQMIIDDAIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAo
UHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ
a3GQsUdC7WDruGWZh/A+4jAJBgUrDgMCGgUAoIIBbzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcB
MBwGCSqGSIb3DQEJBTEPFw0wNzA3MDkxNDE5NDBaMCMGCSqGSIb3DQEJBDEWBBQ8B4NV5xAGg/jV
hfVpWyGMyxUu1DCBhQYJKwYBBAGCNxAEMXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0ECEGtxkLFHQu1g67hlmYfwPuIwgYcGCyqGSIb3DQEJEAILMXigdjBiMQsw
CQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UE
AxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEGtxkLFHQu1g67hlmYfwPuIw
DQYJKoZIhvcNAQEBBQAEggEAVD6s/vvT23hsGsHf2p39+BtAA32zDb5ZbPj7TpW0kR3vQSJi0z8Y
GQOSQjThNfx+sEvAhq7wD9W6iuKkraSNwCgIZ7YlDxOLyS122CqMSihxfbQB7Ih9+Kbtv6J8OzNR
XlExWibLywIMpifFg9nyvqFW3pb4J1qSlqt0zA2WwR4RnLgNtU3onAiO8IPLh2afi9DmbD4tDeeV
8wBAb4D7Wjuvz2PpZF5TSfY/CCCIkEX2QOAOSz/rnfoKCLo7djT5rzV9YeWb7chaCF13sVd3D8t9
u4oWEoPdj931dGpuNVi2U22MAM0EzCRxY8N8eKrwucX3wJXpDRdFJ9YrohWGiwAAAAAAAA==

--Apple-Mail-34--474849771--





From tsvwg-bounces@ietf.org Mon Jul 09 10:27:00 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7uCX-0001rw-18; Mon, 09 Jul 2007 10:26:57 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I7uCV-0001oB-LG
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 09 Jul 2007 10:26:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7uCV-0001o1-BO
	for tsvwg@ietf.org; Mon, 09 Jul 2007 10:26:55 -0400
Received: from rwcrmhc12.comcast.net ([216.148.227.152])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7uCR-0000eR-10
	for tsvwg@ietf.org; Mon, 09 Jul 2007 10:26:55 -0400
Received: from [192.168.1.2]
	(c-69-250-218-72.hsd1.md.comcast.net[69.250.218.72])
	by comcast.net (rwcrmhc12) with SMTP
	id <20070709142648m12004oti3e>; Mon, 9 Jul 2007 14:26:50 +0000
In-Reply-To: <CB3E86CE-5A05-43B4-81AC-443B727F14D4@cisco.com>
References: <E1I400A-0005PX-DQ@stiedprstage1.ietf.org>
	<CB3E86CE-5A05-43B4-81AC-443B727F14D4@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <6D1FB7A5-37E0-4708-A0F7-61B05251BFE4@g11.org.uk>
Content-Transfer-Encoding: 7bit
From: ken carlberg <carlberg@g11.org.uk>
Subject: Re: [Tsvwg] I-D ACTION:draft-ietf-tsvwg-rsvp-proxy-proto-01.txt 
Date: Mon, 9 Jul 2007 10:26:46 -0400
To: Francois Le Faucheur IMAP <flefauch@cisco.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: Ashok Narayanan <ashokn@cisco.com>, hemant.malik@airtel.in,
	Allan GUILLOU <allan.guillou@neufcegetel.fr>, tsvwg tsvwg <tsvwg@ietf.org>,
	Jukka Manner MJ <jmanner@cs.Helsinki.FI>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Francois,

the draft is quite nice.  Most of the comments below are suggestions  
for added clarity.  A number of these are nits, so feel free to  
discard or modify those as you see fit.

1) It may be helpful to move the Terminology section up so that it is  
directly under the first paragraph of section 1.  In section 2, you  
start off with terminology specific to this draft (eg, "RSVP receiver  
Proxy"), and then later describe what it is in the Terminology  
section below.

You should also add a description of what is a "regular receiver" in  
the Terminology section, and to state that it refers to an RSVP  
capable end-host in the classic end-to-end model.

It may also be helpful to state as early as possible, either in the  
Introduction or in the Terminology section, that for this document  
the Sender always refers to the RSVP capable node that originates  
Path messages.  And that the receiver always refers to the RSVP  
capable node that originates RESV messages and is a proxy.  My  
confusion on this matter came up in the first sentence of page 5,  
when you state "...some notifications about reservation state (...)  
are only sent to the receiver".  I presume you mean the RSVP proxy  
receiver, as opposed to the destination end host that may also be an  
RSVP capable receiver.

2) just a nit, but I would feel more comfortable using the term  
"intermediary" instead of "slave" in the third paragraph of page 4.

3) nit.  Section 3, first paragraph, change "of the sender" to "to  
the sender"

4) Page 9, 1'st paragraph.  Could you add a sentence or two stating  
what are the benefits of ensuring that the sender gets a prompt  
failure notification?

I may also be reading the following two paragraphs of that page  
incorrectly, but if an implementation MUST support the method of 3.1,  
why would I add support for 3.2?  Is it rather a case of MUST support  
3.1  *or*  3.2, with the latter being more efficient but requiring  
support of rfc-3473?  Or am I using poor terminology and should the  
text say something like, "must support the method of 3.1, and  
optionally 3.2, but may deploy/use either method"?

5) Finally, this may be a nit, but it might be helpful to add a  
Considerations section at the end of the document that mentions the  
possible scenario of proxy reservations being established and yet the  
end-host destination being unreachable/non-existent?  Proxy RSVP  
routers will know if the downstream leaf router is reachable, but  
they won't necessarily know if the last hop to the end host is  
reachable.  And since the proxy segment may be part of an asymmetric  
path, one can't rely on upstream data to give a hint to the proxy  
receiver that the destination is up.

I don't think this is major liability, but just something that needs  
to be mentioned to those that choose to deploy this work.

-ken









From tsvwg-bounces@ietf.org Tue Jul 10 16:16:17 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8M86-00082a-MC; Tue, 10 Jul 2007 16:16:14 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I8M7R-0006ct-Ji
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 10 Jul 2007 16:15:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8M7P-0006YA-VR; Tue, 10 Jul 2007 16:15:31 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I8M7P-0000B9-Kh; Tue, 10 Jul 2007 16:15:31 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 97D5D32A23;
	Tue, 10 Jul 2007 20:15:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I8M6v-0004Vy-Eq; Tue, 10 Jul 2007 16:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I8M6v-0004Vy-Eq@stiedprstage1.ietf.org>
Date: Tue, 10 Jul 2007 16:15:01 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: tsvwg@ietf.org
Subject: [Tsvwg] I-D ACTION:draft-ietf-tsvwg-sctpsocket-15.txt 
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Transport Area Working Group Working Group of the IETF.

	Title		: Sockets API Extensions for Stream Control Transmission Protocol (SCTP)
	Author(s)	: R. Stewart, et al.
	Filename	: draft-ietf-tsvwg-sctpsocket-15.txt
	Pages		: 87
	Date		: 2007-7-10
	
This document describes a mapping of the Stream Control Transmission
   Protocol SCTP into a sockets API.  The benefits of this mapping
   include compatibility for TCP applications, access to new SCTP
   features and a consolidated error and event notification scheme.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-sctpsocket-15.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-tsvwg-sctpsocket-15.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-tsvwg-sctpsocket-15.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-7-10151336.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-tsvwg-sctpsocket-15.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-tsvwg-sctpsocket-15.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-7-10151336.I-D@ietf.org>


--OtherAccess--

--NextPart--





From tsvwg-bounces@ietf.org Wed Jul 11 12:19:00 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8etv-0008Bh-OU; Wed, 11 Jul 2007 12:18:51 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I8etq-00080C-KS
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 11 Jul 2007 12:18:47 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8etp-0007vC-Gk
	for tsvwg@ietf.org; Wed, 11 Jul 2007 12:18:45 -0400
Received: from atlrel7.hp.com ([156.153.255.213])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8eta-0004x6-7w
	for tsvwg@ietf.org; Wed, 11 Jul 2007 12:18:45 -0400
Received: from smtp1.fc.hp.com (smtp.cnd.hp.com [15.15.136.127])
	by atlrel7.hp.com (Postfix) with ESMTP id 799743552F;
	Wed, 11 Jul 2007 12:17:21 -0400 (EDT)
Received: from [16.116.113.226] (galen.zko.hp.com [16.116.113.226])
	by smtp1.fc.hp.com (Postfix) with ESMTP id E0D331489DE;
	Wed, 11 Jul 2007 16:17:02 +0000 (UTC)
Message-ID: <4695027E.3040109@hp.com>
Date: Wed, 11 Jul 2007 12:17:02 -0400
From: Vlad Yasevich <vladislav.yasevich@hp.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070604)
MIME-Version: 1.0
To: tsvwg <tsvwg@ietf.org>
X-Enigmail-Version: 0.95.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
	Randall Stewart <rrs@cisco.com>
Subject: [Tsvwg] sctp-auth questions
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi

I was going through the 08 draft and planning for the implementation
and had some questions.

Section 6.1 states:

>    An SCTP endpoint has a list of chunks it only accepts if they are
>    received in an authenticated way.  This list is included in the INIT
>    and INIT-ACK and MAY be omitted if it is empty.  Since this list does
>    not change during the lifetime of there is no problem in case of INIT
>    collision.

Lifetime of what?  Association, endpoint?


Section 6.2 states:

>    If the endpoint has no endpoint pair shared key for the peer, it MUST
>    use Shared Key Identifier 0 with an empty endpoint pair shared key.
>    If there are multiple endpoint shared keys the sender selects one and
>    uses the corresponding Shared Key Identifier.

The phrase of "endpoint pair shared key for the peer" gives an impression that
each peer of the sctp endpoint can have it's own set of shared keys.  As an
example:  a single endpoint may be used to connect to different systems and has
a specific shared key for each system.  This is somewhat misleading.  All the
keys really belong to the endpoint and it's up to the ULP (userspace) to specify
which key to use.  I would suggest that "for the peer" be deleted.


Section 6.3
> The out of the blue handling MUST be
>    based on the packet without taking the AUTH chunk into account.

What is this requirement supposed to refer to?


>    Requiring ABORT chunks and COOKIE-ECHO chunks to be authenticated
>    makes it impossible for an attacker to bring down or restart an
>    association as long as the attacker does not know the association
>    shared key.  But it should also be noted that if an endpoint accepts
>    ABORT chunks only in an authenticated way, it may take longer to
>    detect that the peer is no longer available.  If an endpoint accepts

If the receiver requires ABORT chunks to be authenticated, wouldn't OOTB
ABORTS be dropped?

Thanks
-vlad






From tsvwg-bounces@ietf.org Wed Jul 11 12:40:29 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8fEn-0005Wc-18; Wed, 11 Jul 2007 12:40:25 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I8fEl-0005WR-9I
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 11 Jul 2007 12:40:23 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8fEk-0005VT-U1
	for tsvwg@ietf.org; Wed, 11 Jul 2007 12:40:22 -0400
Received: from exprod7og61.obsmtp.com ([64.18.2.177])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8fEk-0006KH-Gj
	for tsvwg@ietf.org; Wed, 11 Jul 2007 12:40:22 -0400
Received: from source ([67.96.16.11]) (using TLSv1) by exprod7ob61.obsmtp.com
	([64.18.6.12]) with SMTP; Wed, 11 Jul 2007 09:39:49 PDT
Received: from ETSMSG-CINAV02.etsmsg.org ([65.90.82.49]) by
	naout-cinexs01.nasmtpout.emrsn.com with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 11 Jul 2007 12:51:10 -0400
Received: from etsmsg-cinexs02.etsmsg.org ([65.90.82.49]) by
	ETSMSG-CINAV02.etsmsg.org with InterScan Message Security Suite;
	Wed, 11 Jul 2007 12:39:48 -0400
Received: from etsmsg-cinexs04.etsmsg.org ([65.90.82.28]) by
	etsmsg-cinexs02.etsmsg.org with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 11 Jul 2007 12:39:48 -0400
Received: from ant.artesyncp.com ([65.90.82.49]) by etsmsg-cinexs04.etsmsg.org
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 11 Jul 2007 12:39:47 -0400
Received: from stephane by ant.artesyncp.com with local (Exim 4.67)
	(envelope-from <stephane@artesyncp.com>) id 1I8fEB-0005HU-36
	for tsvwg@ietf.org; Wed, 11 Jul 2007 17:39:47 +0100
Date: Wed, 11 Jul 2007 17:39:47 +0100
From: Stephane Chazelas <stephane@artesyncp.com>
To: tsvwg <tsvwg@ietf.org>
Message-ID: <20070711163947.GD6418@artesyncp.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: mutt-ng/devel-r562 (Linux)
X-OriginalArrivalTime: 11 Jul 2007 16:39:47.0745 (UTC)
	FILETIME=[1811B910:01C7C3DA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Subject: [Tsvwg] comments and questions on draft-ietf-tsvwg-sctpsocket-15
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi guys,

while looking at the details of what should be done upon send*()
with no data, I found some areas of the Socket draft that
confused me.

Could you please help me clarify them?

3.1.5: (knitpicking)
  > To gracefully shutdown a specific association represented by the one-
  > to-many style socket, an application should use the sendmsg() call,
  > and including the SCTP_EOF flag.  A user may optionally terminate an
  > association non-gracefully by sending with the SCTP_ABORT flag and
  > possibly passing a user specified abort code in the data field.  Both

  What "data field"? 5.2.2 indicates that that's msg_iov, but that field
  is described as "scatter/gather array", not "data".

  > flags SCTP_EOF and SCTP_ABORT are passed with ancillary data (see
  > Section 5.2.2) in the sendmsg call.

5.1:

  > The scatter/gather buffers, or I/O vectors (pointed to by the msg_iov
  > field) are treated as a single SCTP data chunk, rather than multiple
  > chunks, for both sendmsg() and recvmsg().

  possible confusion with protocol DATA chunks. Shouldn't it be "single
  SCTP message". A stack may still fragment the message into several
  DATA chunks to fit in the MTU. All those DATA chunks would have the
  same SSN.

5.2:

  > There are two kinds of ancillary data used by SCTP: initialization
  > data, and, header information (SNDRCV).  Initialization data (one-to-
  > many style only) sets protocol parameters for new associations.
  > Section 5.2.1 provides more details.  Header information can set or
  > report parameters on individual messages in a stream.  See
  > Section 5.2.2 for how to use SNDRCV ancillary data.

  Why 1-to-many only? Especially when 4.1.5 mentions explicitely that you
  can use an SCTP_INIT if you want to send data at the same time as you
  connect?:

  > Note that SCTP allows data exchange, similar to T/TCP RFC1644
  > [RFC1644], during the association set up phase.  If an application
  > wants to do this, it cannot use connect() call.  Instead, it should
			           ^
                                  the
  > use sendto() or sendmsg() to initiate an association.  If it uses
  > sendto() and it wants to change initialization behavior, it needs to
  > use the SCTP_INITMSG socket option before calling sendto().  Or it
  > can use SCTP_INIT type sendmsg() to initiate an association without
  > doing the setsockopt().

  Inconsistency?

6.1:
  > Note, if an application calls a send function with no user data and
  > no ancillary data the SCTP implementation should reject the request
  > with an appropriate error message.  An implementation is NOT allowed
  > to send a Data chunk with no user data RFC2960 [RFC2960].

  OK, but then what about a sendmsg() with ancillary data and no user
  data?

  The draft suggests that we may send a SCTP_SNDRCV structure with
  SCTP_EOF and no data if we want to close a 1-to-many association.

  It suggests as well that we may be able to use SCTP_ABORT with no data
  if we want to abort an association without giving a reason.

  But what about the other possible usages of SCTP_SNDRCV and SCTP_INIT?

  If we do a sendmsg() with an SCTP_INIT and no user data,
  should it automatically start an association without sending
  data?

  If yes, then why not allowing a user to do a sendmsg() with neither
  data nor ancillary data, to allow him to establish an association
  using the default init parameters?

  Also, what about a sendmsg() with SCTP_ABORT (or SCTP_EOF and no data)
  to a destination to which we're not associated yet? Should it
  establish and then close an association?

Best regards,
Stephane





From tsvwg-bounces@ietf.org Wed Jul 11 12:44:57 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8fJB-00082h-0I; Wed, 11 Jul 2007 12:44:57 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I8fJ9-00082M-HS
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 11 Jul 2007 12:44:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8fJ9-00082B-7Q
	for tsvwg@ietf.org; Wed, 11 Jul 2007 12:44:55 -0400
Received: from drew.ipv6.franken.de ([2001:638:a02:a001:20e:cff:fe4a:feaa]
	helo=mail-n.franken.de) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I8fJ4-0006I9-MN
	for tsvwg@ietf.org; Wed, 11 Jul 2007 12:44:55 -0400
Received: from [192.168.1.17] (p508FC255.dip.t-dialin.net [80.143.194.85])
	by mail-n.franken.de (Postfix) with ESMTP id 1A829800008C;
	Wed, 11 Jul 2007 18:44:49 +0200 (CEST)
	(KNF-authenticated sender: macmic)
In-Reply-To: <4695027E.3040109@hp.com>
References: <4695027E.3040109@hp.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <A4E4BE23-2187-484D-B6BA-4B6B1DE756DB@lurchi.franken.de>
Content-Transfer-Encoding: 7bit
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Date: Wed, 11 Jul 2007 18:44:53 +0200
To: Vlad Yasevich <vladislav.yasevich@hp.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: Randall Stewart <rrs@cisco.com>, tsvwg <tsvwg@ietf.org>
Subject: [Tsvwg] Re: sctp-auth questions
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi Vlan,

see my comments in-line.

Best regards
Michael

On Jul 11, 2007, at 6:17 PM, Vlad Yasevich wrote:

> Hi
>
> I was going through the 08 draft and planning for the implementation
> and had some questions.
>
> Section 6.1 states:
>
>>    An SCTP endpoint has a list of chunks it only accepts if they are
>>    received in an authenticated way.  This list is included in the  
>> INIT
>>    and INIT-ACK and MAY be omitted if it is empty.  Since this  
>> list does
>>    not change during the lifetime of there is no problem in case  
>> of INIT
>>    collision.
>
> Lifetime of what?  Association, endpoint?
End-point.
>
>
> Section 6.2 states:
>
>>    If the endpoint has no endpoint pair shared key for the peer,  
>> it MUST
>>    use Shared Key Identifier 0 with an empty endpoint pair shared  
>> key.
>>    If there are multiple endpoint shared keys the sender selects  
>> one and
>>    uses the corresponding Shared Key Identifier.
>
> The phrase of "endpoint pair shared key for the peer" gives an  
> impression that
> each peer of the sctp endpoint can have it's own set of shared  
> keys.  As an
> example:  a single endpoint may be used to connect to different  
> systems and has
> a specific shared key for each system.  This is somewhat  
> misleading.  All the
> keys really belong to the endpoint and it's up to the ULP  
> (userspace) to specify
> which key to use.  I would suggest that "for the peer" be deleted.
I'm not sure what you mean... The shared keys are for end-point  
pairs. So if you
have one end-point (lets say a 1-to-many style socket), you can have  
different end-point
pair shared keys for each peer. That is why you have an sca_assoc_id  
in the
SCTP_AUTH_KEY socket option.

So I think the text is correct.
>
>
> Section 6.3
>> The out of the blue handling MUST be
>>    based on the packet without taking the AUTH chunk into account.
>
> What is this requirement supposed to refer to?
No ABORT in response to a packet which contains AUTH;ABORT, for example.
>
>
>>    Requiring ABORT chunks and COOKIE-ECHO chunks to be authenticated
>>    makes it impossible for an attacker to bring down or restart an
>>    association as long as the attacker does not know the association
>>    shared key.  But it should also be noted that if an endpoint  
>> accepts
>>    ABORT chunks only in an authenticated way, it may take longer to
>>    detect that the peer is no longer available.  If an endpoint  
>> accepts
>
> If the receiver requires ABORT chunks to be authenticated, wouldn't  
> OOTB
> ABORTS be dropped?
Yes, that is why it may take longer to figure out that your peer died.
>
> Thanks
> -vlad
>
>






From tsvwg-bounces@ietf.org Wed Jul 11 12:58:06 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8fVr-0006l1-HD; Wed, 11 Jul 2007 12:58:03 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I8fVp-0006kw-Hy
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 11 Jul 2007 12:58:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8fVp-0006ko-8Q
	for tsvwg@ietf.org; Wed, 11 Jul 2007 12:58:01 -0400
Received: from atlrel7.hp.com ([156.153.255.213])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8fVk-0006pi-Qc
	for tsvwg@ietf.org; Wed, 11 Jul 2007 12:58:01 -0400
Received: from smtp2.fc.hp.com (smtp.cnd.hp.com [15.11.136.114])
	by atlrel7.hp.com (Postfix) with ESMTP id B6129356CE;
	Wed, 11 Jul 2007 12:57:34 -0400 (EDT)
Received: from [16.116.113.226] (galen.zko.hp.com [16.116.113.226])
	by smtp2.fc.hp.com (Postfix) with ESMTP id 0215B190599;
	Wed, 11 Jul 2007 16:57:31 +0000 (UTC)
Message-ID: <46950BFB.9070006@hp.com>
Date: Wed, 11 Jul 2007 12:57:31 -0400
From: Vlad Yasevich <vladislav.yasevich@hp.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070604)
MIME-Version: 1.0
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
References: <4695027E.3040109@hp.com>
	<A4E4BE23-2187-484D-B6BA-4B6B1DE756DB@lurchi.franken.de>
In-Reply-To: <A4E4BE23-2187-484D-B6BA-4B6B1DE756DB@lurchi.franken.de>
X-Enigmail-Version: 0.95.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: Randall Stewart <rrs@cisco.com>, tsvwg <tsvwg@ietf.org>
Subject: [Tsvwg] Re: sctp-auth questions
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Michael Tuexen wrote:
> Hi Vlan,
> 
> see my comments in-line.
> 
> Best regards
> Michael
> 
> On Jul 11, 2007, at 6:17 PM, Vlad Yasevich wrote:
> 
>> Hi
>>
>> I was going through the 08 draft and planning for the implementation
>> and had some questions.
>>
>> Section 6.1 states:
>>
>>>    An SCTP endpoint has a list of chunks it only accepts if they are
>>>    received in an authenticated way.  This list is included in the INIT
>>>    and INIT-ACK and MAY be omitted if it is empty.  Since this list does
>>>    not change during the lifetime of there is no problem in case of INIT
>>>    collision.
>>
>> Lifetime of what?  Association, endpoint?
> End-point.

Can that be put the draft.  The last sentence is incomplete.

>>
>>
>> Section 6.2 states:
>>
>>>    If the endpoint has no endpoint pair shared key for the peer, it MUST
>>>    use Shared Key Identifier 0 with an empty endpoint pair shared key.
>>>    If there are multiple endpoint shared keys the sender selects one and
>>>    uses the corresponding Shared Key Identifier.
>>
>> The phrase of "endpoint pair shared key for the peer" gives an
>> impression that
>> each peer of the sctp endpoint can have it's own set of shared keys. 
>> As an
>> example:  a single endpoint may be used to connect to different
>> systems and has
>> a specific shared key for each system.  This is somewhat misleading. 
>> All the
>> keys really belong to the endpoint and it's up to the ULP (userspace)
>> to specify
>> which key to use.  I would suggest that "for the peer" be deleted.
> I'm not sure what you mean... The shared keys are for end-point pairs.
> So if you
> have one end-point (lets say a 1-to-many style socket), you can have
> different end-point
> pair shared keys for each peer. That is why you have an sca_assoc_id in the
> SCTP_AUTH_KEY socket option.
> 
> So I think the text is correct.

Well, the endpoint doesn't know which of it's keys is which peer.   All it has
is a list keys it knows.  The API specifies which key to use.

BTW, having an ancillary data option to specify the key id along with the sendmsg
might also be useful, but that's a topic for the API spec.

Saying "shared for the peer" give an impression that there is knowledge that
specific keys apply to specific peers, while there isn't such thing.

>>
>>
>> Section 6.3
>>> The out of the blue handling MUST be
>>>    based on the packet without taking the AUTH chunk into account.
>>
>> What is this requirement supposed to refer to?
> No ABORT in response to a packet which contains AUTH;ABORT, for example.

Ah.  That's not really clear in that particular section.  Any way to clear
it up.

>>
>>
>>>    Requiring ABORT chunks and COOKIE-ECHO chunks to be authenticated
>>>    makes it impossible for an attacker to bring down or restart an
>>>    association as long as the attacker does not know the association
>>>    shared key.  But it should also be noted that if an endpoint accepts
>>>    ABORT chunks only in an authenticated way, it may take longer to
>>>    detect that the peer is no longer available.  If an endpoint accepts
>>
>> If the receiver requires ABORT chunks to be authenticated, wouldn't OOTB
>> ABORTS be dropped?
> Yes, that is why it may take longer to figure out that your peer died.

Ok.  Any way to add this example in?

Thanks
-vlad





From tsvwg-bounces@ietf.org Wed Jul 11 13:12:03 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8fjJ-0005k8-J3; Wed, 11 Jul 2007 13:11:57 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I8fjI-0005ju-LT
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 11 Jul 2007 13:11:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8fjI-0005je-BI
	for tsvwg@ietf.org; Wed, 11 Jul 2007 13:11:56 -0400
Received: from drew.ipv6.franken.de ([2001:638:a02:a001:20e:cff:fe4a:feaa]
	helo=mail-n.franken.de) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I8fjD-00078V-EZ
	for tsvwg@ietf.org; Wed, 11 Jul 2007 13:11:56 -0400
Received: from [192.168.1.17] (p508FC255.dip.t-dialin.net [80.143.194.85])
	by mail-n.franken.de (Postfix) with ESMTP id 338EB801AC04;
	Wed, 11 Jul 2007 19:11:50 +0200 (CEST)
	(KNF-authenticated sender: macmic)
In-Reply-To: <46950BFB.9070006@hp.com>
References: <4695027E.3040109@hp.com>
	<A4E4BE23-2187-484D-B6BA-4B6B1DE756DB@lurchi.franken.de>
	<46950BFB.9070006@hp.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <82DC7FDA-F1EA-45F4-9066-A8486203387E@lurchi.franken.de>
Content-Transfer-Encoding: 7bit
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Date: Wed, 11 Jul 2007 19:11:54 +0200
To: Vlad Yasevich <vladislav.yasevich@hp.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 21bf7a2f1643ae0bf20c1e010766eb78
Cc: Randall Stewart <rrs@cisco.com>, tsvwg <tsvwg@ietf.org>
Subject: [Tsvwg] Re: sctp-auth questions
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

On Jul 11, 2007, at 6:57 PM, Vlad Yasevich wrote:

> Michael Tuexen wrote:
>> Hi Vlan,
>>
>> see my comments in-line.
>>
>> Best regards
>> Michael
>>
>> On Jul 11, 2007, at 6:17 PM, Vlad Yasevich wrote:
>>
>>> Hi
>>>
>>> I was going through the 08 draft and planning for the implementation
>>> and had some questions.
>>>
>>> Section 6.1 states:
>>>
>>>>    An SCTP endpoint has a list of chunks it only accepts if they  
>>>> are
>>>>    received in an authenticated way.  This list is included in  
>>>> the INIT
>>>>    and INIT-ACK and MAY be omitted if it is empty.  Since this  
>>>> list does
>>>>    not change during the lifetime of there is no problem in case  
>>>> of INIT
>>>>    collision.
>>>
>>> Lifetime of what?  Association, endpoint?
>> End-point.
>
> Can that be put the draft.  The last sentence is incomplete.
RFC 4895 will read:

    An SCTP endpoint has a list of chunks it only accepts if they are
    received in an authenticated way.  This list is included in the INIT
    and INIT-ACK, and MAY be omitted if it is empty.  Since this list
    does not change during the lifetime of the SCTP endpoint there is no
    problem in case of INIT collision.

Please note that the document is in AUTH48 and we are waiting for the
last author to give his final OK...
>
>>>
>>>
>>> Section 6.2 states:
>>>
>>>>    If the endpoint has no endpoint pair shared key for the peer,  
>>>> it MUST
>>>>    use Shared Key Identifier 0 with an empty endpoint pair  
>>>> shared key.
>>>>    If there are multiple endpoint shared keys the sender selects  
>>>> one and
>>>>    uses the corresponding Shared Key Identifier.
>>>
>>> The phrase of "endpoint pair shared key for the peer" gives an
>>> impression that
>>> each peer of the sctp endpoint can have it's own set of shared keys.
>>> As an
>>> example:  a single endpoint may be used to connect to different
>>> systems and has
>>> a specific shared key for each system.  This is somewhat misleading.
>>> All the
>>> keys really belong to the endpoint and it's up to the ULP  
>>> (userspace)
>>> to specify
>>> which key to use.  I would suggest that "for the peer" be deleted.
>> I'm not sure what you mean... The shared keys are for end-point  
>> pairs.
>> So if you
>> have one end-point (lets say a 1-to-many style socket), you can have
>> different end-point
>> pair shared keys for each peer. That is why you have an  
>> sca_assoc_id in the
>> SCTP_AUTH_KEY socket option.
>>
>> So I think the text is correct.
>
> Well, the endpoint doesn't know which of it's keys is which peer.    
> All it has
> is a list keys it knows.  The API specifies which key to use.
The list of endpoint pair keys is something you would keep on the  
STCB. It
is per association. You can set it for an end-point and it is then the
default for all new associations, but this is "an end-point pair" =  
association
thing.
>
> BTW, having an ancillary data option to specify the key id along  
> with the sendmsg
> might also be useful, but that's a topic for the API spec.
>
> Saying "shared for the peer" give an impression that there is  
> knowledge that
> specific keys apply to specific peers, while there isn't such thing.
>
>>>
>>>
>>> Section 6.3
>>>> The out of the blue handling MUST be
>>>>    based on the packet without taking the AUTH chunk into account.
>>>
>>> What is this requirement supposed to refer to?
>> No ABORT in response to a packet which contains AUTH;ABORT, for  
>> example.
>
> Ah.  That's not really clear in that particular section.  Any way  
> to clear
> it up.
As said earlier: The last call was a sometime ago...
The final text is:

    If the receiver does not find an STCB for a packet containing an  
AUTH
    chunk as the first chunk and does not find a COOKIE-ECHO chunk as  
the
    second chunk, it MUST use the chunks after the AUTH chunk to look up
    an existing association.  If no association is found, the packet  
MUST
    be considered as out of the blue.  The out of the blue handling MUST
    be based on the packet without taking the AUTH chunk into account.
    If an association is found, it MUST process the AUTH chunk using the
    STCB from the existing association as described earlier.

>
>>>
>>>
>>>>    Requiring ABORT chunks and COOKIE-ECHO chunks to be  
>>>> authenticated
>>>>    makes it impossible for an attacker to bring down or restart an
>>>>    association as long as the attacker does not know the  
>>>> association
>>>>    shared key.  But it should also be noted that if an endpoint  
>>>> accepts
>>>>    ABORT chunks only in an authenticated way, it may take longer to
>>>>    detect that the peer is no longer available.  If an endpoint  
>>>> accepts
>>>
>>> If the receiver requires ABORT chunks to be authenticated,  
>>> wouldn't OOTB
>>> ABORTS be dropped?
>> Yes, that is why it may take longer to figure out that your peer  
>> died.
>
> Ok.  Any way to add this example in?
No, I do not think so.
>
> Thanks
> -vlad
>






From tsvwg-bounces@ietf.org Wed Jul 11 13:32:26 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8g38-00060Z-2F; Wed, 11 Jul 2007 13:32:26 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I8g37-00060U-5f
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 11 Jul 2007 13:32:25 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8g36-00060M-RV
	for tsvwg@ietf.org; Wed, 11 Jul 2007 13:32:24 -0400
Received: from atlrel8.hp.com ([156.153.255.206])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8g2r-00007Z-ME
	for tsvwg@ietf.org; Wed, 11 Jul 2007 13:32:24 -0400
Received: from smtp2.fc.hp.com (smtp.fc.hp.com [15.11.136.114])
	by atlrel8.hp.com (Postfix) with ESMTP id 7E40B35E95;
	Wed, 11 Jul 2007 13:31:18 -0400 (EDT)
Received: from [16.116.113.226] (galen.zko.hp.com [16.116.113.226])
	by smtp2.fc.hp.com (Postfix) with ESMTP id 803DA19064C;
	Wed, 11 Jul 2007 17:31:08 +0000 (UTC)
Message-ID: <469513DB.4070502@hp.com>
Date: Wed, 11 Jul 2007 13:31:07 -0400
From: Vlad Yasevich <vladislav.yasevich@hp.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070604)
MIME-Version: 1.0
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
References: <4695027E.3040109@hp.com>
	<A4E4BE23-2187-484D-B6BA-4B6B1DE756DB@lurchi.franken.de>
	<46950BFB.9070006@hp.com>
	<82DC7FDA-F1EA-45F4-9066-A8486203387E@lurchi.franken.de>
In-Reply-To: <82DC7FDA-F1EA-45F4-9066-A8486203387E@lurchi.franken.de>
X-Enigmail-Version: 0.95.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: Randall Stewart <rrs@cisco.com>, tsvwg <tsvwg@ietf.org>
Subject: [Tsvwg] Re: sctp-auth questions
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Michael Tuexen wrote:
> On Jul 11, 2007, at 6:57 PM, Vlad Yasevich wrote:
> 
>> Michael Tuexen wrote:
>>> Hi Vlan,
>>>
>>> see my comments in-line.
>>>
>>> Best regards
>>> Michael
>>>
>>> On Jul 11, 2007, at 6:17 PM, Vlad Yasevich wrote:
>>>
>>>> Hi
>>>>
>>>> I was going through the 08 draft and planning for the implementation
>>>> and had some questions.
>>>>
>>>> Section 6.1 states:
>>>>
>>>>>    An SCTP endpoint has a list of chunks it only accepts if they are
>>>>>    received in an authenticated way.  This list is included in the
>>>>> INIT
>>>>>    and INIT-ACK and MAY be omitted if it is empty.  Since this list
>>>>> does
>>>>>    not change during the lifetime of there is no problem in case of
>>>>> INIT
>>>>>    collision.
>>>>
>>>> Lifetime of what?  Association, endpoint?
>>> End-point.
>>
>> Can that be put the draft.  The last sentence is incomplete.
> RFC 4895 will read:
> 
>    An SCTP endpoint has a list of chunks it only accepts if they are
>    received in an authenticated way.  This list is included in the INIT
>    and INIT-ACK, and MAY be omitted if it is empty.  Since this list
>    does not change during the lifetime of the SCTP endpoint there is no
>    problem in case of INIT collision.
> 
> Please note that the document is in AUTH48 and we are waiting for the
> last author to give his final OK...

OK.

>> Ok.  Any way to add this example in?
> No, I do not think so.

Bummer.

Thanks
-vlad





From tsvwg-bounces@ietf.org Wed Jul 11 14:15:45 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8gj0-0006g7-4I; Wed, 11 Jul 2007 14:15:42 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I8giN-0005YI-D6
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 11 Jul 2007 14:15:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8giM-0005Wj-Qv; Wed, 11 Jul 2007 14:15:02 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I8giM-000155-I6; Wed, 11 Jul 2007 14:15:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 6AC6E26EB5;
	Wed, 11 Jul 2007 18:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I8giM-0003D3-47; Wed, 11 Jul 2007 14:15:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I8giM-0003D3-47@stiedprstage1.ietf.org>
Date: Wed, 11 Jul 2007 14:15:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: tsvwg@ietf.org
Subject: [Tsvwg] I-D ACTION:draft-ietf-tsvwg-rsvp-proxy-approaches-01.txt 
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Transport Area Working Group Working Group of the IETF.

	Title		: RSVP Proxy Approaches
	Author(s)	: F. Le Faucheur, et al.
	Filename	: draft-ietf-tsvwg-rsvp-proxy-approaches-01.txt
	Pages		: 43
	Date		: 2007-7-11
	
RSVP signaling can be used to make end-to-end resource reservations
   in an IP network in order to guarantee the Quality of Service
   required by certain flows.  With conventional RSVP, both the data
   sender and receiver of a given flow take part in RSVP signaling.
   Yet, there are many use cases where resource reservation is required,
   but the receiver, the sender, or both, is not RSVP-capable.  This
   document presents RSVP Proxy behaviors allowing RSVP routers to
   perform RSVP signaling on behalf of a receiver or a sender that is
   not RSVP-capable.  This allows resource reservations to be
   established on critical parts of the end-to-end path.  This document
   reviews conceptual approaches for deploying RSVP Proxies and
   discusses how RSVP reservations can be synchronized with application
   requirements, despite the sender, receiver, or both not participating
   in RSVP.  This document also points out where extensions to RSVP (or
   to other protocols) may be needed for deployment of a given RSVP
   Proxy approach.  However, such extensions are outside the scope of
   this document.  Finally, practical use cases for RSVP Proxy are
   described.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rsvp-proxy-approaches-01.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-tsvwg-rsvp-proxy-approaches-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-tsvwg-rsvp-proxy-approaches-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-7-11133252.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-tsvwg-rsvp-proxy-approaches-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-tsvwg-rsvp-proxy-approaches-01.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-7-11133252.I-D@ietf.org>


--OtherAccess--

--NextPart--





From tsvwg-bounces@ietf.org Wed Jul 11 14:43:25 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8h9i-0005uu-Ai; Wed, 11 Jul 2007 14:43:18 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I8h9h-0005uV-R5
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 11 Jul 2007 14:43:17 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8h9h-0005uF-3Q
	for tsvwg@ietf.org; Wed, 11 Jul 2007 14:43:17 -0400
Received: from atlrel6.hp.com ([156.153.255.205])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8h9U-0003aE-TY
	for tsvwg@ietf.org; Wed, 11 Jul 2007 14:43:17 -0400
Received: from smtp2.fc.hp.com (smtp.cnd.hp.com [15.11.136.114])
	by atlrel6.hp.com (Postfix) with ESMTP id 550EA380BE;
	Wed, 11 Jul 2007 14:41:51 -0400 (EDT)
Received: from [16.116.113.226] (galen.zko.hp.com [16.116.113.226])
	by smtp2.fc.hp.com (Postfix) with ESMTP id 91FD81903EC;
	Wed, 11 Jul 2007 18:41:50 +0000 (UTC)
Message-ID: <4695246D.8020304@hp.com>
Date: Wed, 11 Jul 2007 14:41:49 -0400
From: Vlad Yasevich <vladislav.yasevich@hp.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070604)
MIME-Version: 1.0
To: Peter Lei <peter.lei@ieee.org>
Subject: Re: [Tsvwg] Re: sctp-auth questions
References: <4695027E.3040109@hp.com>	<A4E4BE23-2187-484D-B6BA-4B6B1DE756DB@lurchi.franken.de>	<46950BFB.9070006@hp.com>
	<82DC7FDA-F1EA-45F4-9066-A8486203387E@lurchi.franken.de>
	<46951FA3.8010005@ieee.org>
In-Reply-To: <46951FA3.8010005@ieee.org>
X-Enigmail-Version: 0.95.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
	Randall Stewart <rrs@cisco.com>, tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Peter Lei wrote:
>>> Well, the endpoint doesn't know which of it's keys is which peer.  
>>> All it has
>>> is a list keys it knows.  The API specifies which key to use.
>> The list of endpoint pair keys is something you would keep on the
>> STCB. It
>> is per association. You can set it for an end-point and it is then the
>> default for all new associations, but this is "an end-point pair" =
>> association
>> thing.
> 
> Right.  The set of shared keys that are set on the endpoint is
> the default set of shared keys on every association that is created
> on that endpoint; this behaves like most of the socket options.
> You can have different shared keys on a per assoc basis by using
> the API's assoc_id field to set/delete shared keys after the assoc
> is formed.

Right, the set of shared keys for an association may be different
from that for an endpoint.  However, the text in the spec talks about
the endpoint.  There is really no peer information in the endpoint,
and speaking about keys for a peer is misleading in my opinion.

> 
> This should not be confused with the actual keying material used for
> the AUTH HMAC mechanism itself, the concatenated keys, which must
> be kept on a per assoc basis since the RANDOM params are part of
> those keys (along with the HMAC_ID and CHUNKS params contents).

Nope, not confusing those.

> 
>>> BTW, having an ancillary data option to specify the key id along with
>>> the sendmsg
>>> might also be useful, but that's a topic for the API spec.
> 
> I disagree with this... why would you want/need to send individual
> SCTP messages on the same association with different keys?
>
Not the same association, but a 1-to-many endpoint.  Let's say you have
3 different keys on the endpoint.  Each association on that endpoint
would have 3 keys as well with a keying material vector for each key. 
You can then specify a different keys to use as part of sendmsg().

Another time this would be useful if when restarting with authenticated
cookie-echo chunks.  The application can issue a sendmsg() stating which
key should be used.  The restart procedure then wouldn't have to do anything
special.

-vlad








From tsvwg-bounces@ietf.org Wed Jul 11 14:50:00 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8hGB-00015W-Ct; Wed, 11 Jul 2007 14:49:59 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I8hG9-00013o-Kc
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 11 Jul 2007 14:49:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8gp8-0006rj-9s
	for tsvwg@ietf.org; Wed, 11 Jul 2007 14:22:03 -0400
Received: from alnrmhc12.comcast.net ([204.127.225.92])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8gog-0001qi-M0
	for tsvwg@ietf.org; Wed, 11 Jul 2007 14:22:01 -0400
Received: from macbookpro.lei.chicago.il.us
	(c-24-13-182-11.hsd1.il.comcast.net[24.13.182.11])
	by comcast.net (alnrmhc12) with ESMTP
	id <20070711182133b1200l5u6je>; Wed, 11 Jul 2007 18:21:33 +0000
Message-ID: <46951FA3.8010005@ieee.org>
Date: Wed, 11 Jul 2007 13:21:23 -0500
From: Peter Lei <peter.lei@ieee.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2 Mnenhy/0.7.5.0
MIME-Version: 1.0
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, 
	Vlad Yasevich <vladislav.yasevich@hp.com>
Subject: Re: [Tsvwg] Re: sctp-auth questions
References: <4695027E.3040109@hp.com>	<A4E4BE23-2187-484D-B6BA-4B6B1DE756DB@lurchi.franken.de>	<46950BFB.9070006@hp.com>
	<82DC7FDA-F1EA-45F4-9066-A8486203387E@lurchi.franken.de>
In-Reply-To: <82DC7FDA-F1EA-45F4-9066-A8486203387E@lurchi.franken.de>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
	micalg=sha1; boundary="------------ms050805080508030107010201"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b045c2b078f76b9f842d469de8a32de3
Cc: Randall Stewart <rrs@cisco.com>, tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

This is a cryptographically signed message in MIME format.

--------------ms050805080508030107010201
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Some comments in-line:

Michael Tuexen wrote:
> On Jul 11, 2007, at 6:57 PM, Vlad Yasevich wrote:
> 
>> Michael Tuexen wrote:
>>> Hi Vlan,
>>>
>>> see my comments in-line.
>>>
>>> Best regards
>>> Michael
>>>
>>> On Jul 11, 2007, at 6:17 PM, Vlad Yasevich wrote:
>>>
>>>> Hi
>>>>
>>>> I was going through the 08 draft and planning for the implementation
>>>> and had some questions.
>>>>
>>>> Section 6.1 states:
>>>>
>>>>>    An SCTP endpoint has a list of chunks it only accepts if they are
>>>>>    received in an authenticated way.  This list is included in the 
>>>>> INIT
>>>>>    and INIT-ACK and MAY be omitted if it is empty.  Since this list 
>>>>> does
>>>>>    not change during the lifetime of there is no problem in case of 
>>>>> INIT
>>>>>    collision.
>>>>
>>>> Lifetime of what?  Association, endpoint?
>>> End-point.
>>
>> Can that be put the draft.  The last sentence is incomplete.
> RFC 4895 will read:
> 
>    An SCTP endpoint has a list of chunks it only accepts if they are
>    received in an authenticated way.  This list is included in the INIT
>    and INIT-ACK, and MAY be omitted if it is empty.  Since this list
>    does not change during the lifetime of the SCTP endpoint there is no
>    problem in case of INIT collision.
> 
> Please note that the document is in AUTH48 and we are waiting for the
> last author to give his final OK...
>>
>>>>
>>>>
>>>> Section 6.2 states:
>>>>
>>>>>    If the endpoint has no endpoint pair shared key for the peer, it 
>>>>> MUST
>>>>>    use Shared Key Identifier 0 with an empty endpoint pair shared key.
>>>>>    If there are multiple endpoint shared keys the sender selects 
>>>>> one and
>>>>>    uses the corresponding Shared Key Identifier.
>>>>
>>>> The phrase of "endpoint pair shared key for the peer" gives an
>>>> impression that
>>>> each peer of the sctp endpoint can have it's own set of shared keys.
>>>> As an
>>>> example:  a single endpoint may be used to connect to different
>>>> systems and has
>>>> a specific shared key for each system.  This is somewhat misleading.
>>>> All the
>>>> keys really belong to the endpoint and it's up to the ULP (userspace)
>>>> to specify
>>>> which key to use.  I would suggest that "for the peer" be deleted.
>>> I'm not sure what you mean... The shared keys are for end-point pairs.
>>> So if you
>>> have one end-point (lets say a 1-to-many style socket), you can have
>>> different end-point
>>> pair shared keys for each peer. That is why you have an sca_assoc_id 
>>> in the
>>> SCTP_AUTH_KEY socket option.
>>>
>>> So I think the text is correct.
>>
>> Well, the endpoint doesn't know which of it's keys is which peer.   
>> All it has
>> is a list keys it knows.  The API specifies which key to use.
> The list of endpoint pair keys is something you would keep on the STCB. It
> is per association. You can set it for an end-point and it is then the
> default for all new associations, but this is "an end-point pair" = 
> association
> thing.

Right.  The set of shared keys that are set on the endpoint is
the default set of shared keys on every association that is created
on that endpoint; this behaves like most of the socket options.
You can have different shared keys on a per assoc basis by using
the API's assoc_id field to set/delete shared keys after the assoc
is formed.

This should not be confused with the actual keying material used for
the AUTH HMAC mechanism itself, the concatenated keys, which must
be kept on a per assoc basis since the RANDOM params are part of
those keys (along with the HMAC_ID and CHUNKS params contents).

>> BTW, having an ancillary data option to specify the key id along with 
>> the sendmsg
>> might also be useful, but that's a topic for the API spec.

I disagree with this... why would you want/need to send individual
SCTP messages on the same association with different keys?

--peter

>> Saying "shared for the peer" give an impression that there is 
>> knowledge that
>> specific keys apply to specific peers, while there isn't such thing.
>>
>>>>
>>>>
>>>> Section 6.3
>>>>> The out of the blue handling MUST be
>>>>>    based on the packet without taking the AUTH chunk into account.
>>>>
>>>> What is this requirement supposed to refer to?
>>> No ABORT in response to a packet which contains AUTH;ABORT, for example.
>>
>> Ah.  That's not really clear in that particular section.  Any way to 
>> clear
>> it up.
> As said earlier: The last call was a sometime ago...
> The final text is:
> 
>    If the receiver does not find an STCB for a packet containing an AUTH
>    chunk as the first chunk and does not find a COOKIE-ECHO chunk as the
>    second chunk, it MUST use the chunks after the AUTH chunk to look up
>    an existing association.  If no association is found, the packet MUST
>    be considered as out of the blue.  The out of the blue handling MUST
>    be based on the packet without taking the AUTH chunk into account.
>    If an association is found, it MUST process the AUTH chunk using the
>    STCB from the existing association as described earlier.
> 
>>
>>>>
>>>>
>>>>>    Requiring ABORT chunks and COOKIE-ECHO chunks to be authenticated
>>>>>    makes it impossible for an attacker to bring down or restart an
>>>>>    association as long as the attacker does not know the association
>>>>>    shared key.  But it should also be noted that if an endpoint 
>>>>> accepts
>>>>>    ABORT chunks only in an authenticated way, it may take longer to
>>>>>    detect that the peer is no longer available.  If an endpoint 
>>>>> accepts
>>>>
>>>> If the receiver requires ABORT chunks to be authenticated, wouldn't 
>>>> OOTB
>>>> ABORTS be dropped?
>>> Yes, that is why it may take longer to figure out that your peer died.
>>
>> Ok.  Any way to add this example in?
> No, I do not think so.
>>
>> Thanks
>> -vlad
>>
> 
> 
> 
> 

--------------ms050805080508030107010201
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJBzCC
At4wggJHoAMCAQICEFnRkKrCzpcCm7Il9L1WF6UwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE
BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT
I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA3MDQyNDA0NTY0MloX
DTA4MDQyMzA0NTY0MlowRDEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEhMB8G
CSqGSIb3DQEJARYScGV0ZXIubGVpQGllZWUub3JnMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEAu50a+sbvLQEzBhajGCsDC4hIqrEfWoVvaBV5nKxPl25h3omo1MIQX4kipB+l
Firh5iWbvNck8S69LQT8NnflXR5Bn12Z59trQAdxtTn7C05OQ5DXAOOaelsR96PA6wanyt29
OnEaMJeraujnRYKC1NUzOm8Tdh5esNEjYyfLnKTaXXKaNv85WMIzJo5HFTe1MKXVSWq/JZ5f
oF29Es4GM8xM69SxPZmnH3X2iz1+6WfCNfm7VXw6ouIyq3XgO5u4oZ6fdYRp4h++BY7smI3H
v/66VZhY0x33UHr0leiTSvh8Ydy2M99DfeDvWp/QAL0sc9qPgaaaWXEE1VcJWiZ4JQIDAQAB
oy8wLTAdBgNVHREEFjAUgRJwZXRlci5sZWlAaWVlZS5vcmcwDAYDVR0TAQH/BAIwADANBgkq
hkiG9w0BAQUFAAOBgQAoRiQhOgTbRhmT7MfkNOuv6mByra6PCcp/A5eWNxlhW0wVVZWTDP9U
AIG2I2OdR5HShv+myZd1PNTrdzE6g+MjEYq9M8JBzrkQSX7rQ3tTlev9l6v5PZjb+3bBs5HN
/XnH/130LB0EM/kdZ+61ATeGJPdS0D2ZlSz6Q/Neu/ETNTCCAt4wggJHoAMCAQICEFnRkKrC
zpcCm7Il9L1WF6UwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRo
YXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBG
cmVlbWFpbCBJc3N1aW5nIENBMB4XDTA3MDQyNDA0NTY0MloXDTA4MDQyMzA0NTY0MlowRDEf
MB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEhMB8GCSqGSIb3DQEJARYScGV0ZXIu
bGVpQGllZWUub3JnMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAu50a+sbvLQEz
BhajGCsDC4hIqrEfWoVvaBV5nKxPl25h3omo1MIQX4kipB+lFirh5iWbvNck8S69LQT8Nnfl
XR5Bn12Z59trQAdxtTn7C05OQ5DXAOOaelsR96PA6wanyt29OnEaMJeraujnRYKC1NUzOm8T
dh5esNEjYyfLnKTaXXKaNv85WMIzJo5HFTe1MKXVSWq/JZ5foF29Es4GM8xM69SxPZmnH3X2
iz1+6WfCNfm7VXw6ouIyq3XgO5u4oZ6fdYRp4h++BY7smI3Hv/66VZhY0x33UHr0leiTSvh8
Ydy2M99DfeDvWp/QAL0sc9qPgaaaWXEE1VcJWiZ4JQIDAQABoy8wLTAdBgNVHREEFjAUgRJw
ZXRlci5sZWlAaWVlZS5vcmcwDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOBgQAoRiQh
OgTbRhmT7MfkNOuv6mByra6PCcp/A5eWNxlhW0wVVZWTDP9UAIG2I2OdR5HShv+myZd1PNTr
dzE6g+MjEYq9M8JBzrkQSX7rQ3tTlev9l6v5PZjb+3bBs5HN/XnH/130LB0EM/kdZ+61ATeG
JPdS0D2ZlSz6Q/Neu/ETNTCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJ
BgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEa
MBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2Vy
dmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTEr
MCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcw
MDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUg
Q29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1h
aWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065ypla
HmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FW
y688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEE
QB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2
oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3Js
MAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0x
MzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYf
qi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amcOY6MIE9l
X5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNkMIIDYAIBATB2
MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQu
MSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQWdGQqsLO
lwKbsiX0vVYXpTAJBgUrDgMCGgUAoIIBwzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwG
CSqGSIb3DQEJBTEPFw0wNzA3MTExODIxMjNaMCMGCSqGSIb3DQEJBDEWBBRceviBSE+gQvW9
kzJE6DTGg+UQ8DBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA
gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBhQYJKwYBBAGCNxAE
MXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkg
THRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEFnR
kKrCzpcCm7Il9L1WF6UwgYcGCyqGSIb3DQEJEAILMXigdjBiMQswCQYDVQQGEwJaQTElMCMG
A1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBl
cnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEFnRkKrCzpcCm7Il9L1WF6UwDQYJKoZIhvcN
AQEBBQAEggEAZkj3jDADFrjtrNpLxBBsJ93gLIvQYPgLJeCXyz7ycKslk+/0qoy3puwEZPyz
YSPSkpfpX+KuVKtVrInCFzyTkVWGTZkDNVFT76uaGIxE/BD/Y+g5kt3v8oVf9OKO5KXa3Qyn
R1ZTRlx0jrPlHYaT3Rp3LtZ0pmjCg4hDQefH4o7KhVEU1jdJSv3VAnuQVgGMb7cKDVycHQYi
sfNgDbbUWzi7uI0mpDxJ9B86zunkcPgGzFP82mULBRbEP1DpWOAWi8YT6fdaQWiirRG7zdNI
gqqAOg3wu0idscgnPva4pbjOLQ5EKT50hSig154dp1XvvAQYGD7hGCmRE3FMtN64WgAAAAAA
AA==
--------------ms050805080508030107010201--





From tsvwg-bounces@ietf.org Wed Jul 11 14:57:54 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8hNo-0008I8-90; Wed, 11 Jul 2007 14:57:52 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I8hNm-0008I1-V0
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 11 Jul 2007 14:57:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8hNm-0008Hs-LX
	for tsvwg@ietf.org; Wed, 11 Jul 2007 14:57:50 -0400
Received: from alnrmhc11.comcast.net ([204.127.225.91])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8hNi-0003hv-B9
	for tsvwg@ietf.org; Wed, 11 Jul 2007 14:57:50 -0400
Received: from macbookpro.lei.chicago.il.us
	(c-24-13-182-11.hsd1.il.comcast.net[24.13.182.11])
	by comcast.net (alnrmhc11) with ESMTP
	id <20070711185745b1100dmmvpe>; Wed, 11 Jul 2007 18:57:45 +0000
Message-ID: <4695281D.2000404@ieee.org>
Date: Wed, 11 Jul 2007 13:57:33 -0500
From: Peter Lei <peter.lei@ieee.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2 Mnenhy/0.7.5.0
MIME-Version: 1.0
To: Vlad Yasevich <vladislav.yasevich@hp.com>
Subject: Re: [Tsvwg] Re: sctp-auth questions
References: <4695027E.3040109@hp.com>	<A4E4BE23-2187-484D-B6BA-4B6B1DE756DB@lurchi.franken.de>	<46950BFB.9070006@hp.com>	<82DC7FDA-F1EA-45F4-9066-A8486203387E@lurchi.franken.de>	<46951FA3.8010005@ieee.org>
	<4695246D.8020304@hp.com>
In-Reply-To: <4695246D.8020304@hp.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
	micalg=sha1; boundary="------------ms000402030607060108060100"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
	Randall Stewart <rrs@cisco.com>, tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

This is a cryptographically signed message in MIME format.

--------------ms000402030607060108060100
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Vlad Yasevich wrote:

>>>> BTW, having an ancillary data option to specify the key id along with
>>>> the sendmsg
>>>> might also be useful, but that's a topic for the API spec.
>> I disagree with this... why would you want/need to send individual
>> SCTP messages on the same association with different keys?
>>
> Not the same association, but a 1-to-many endpoint.  Let's say you have
> 3 different keys on the endpoint.  Each association on that endpoint
> would have 3 keys as well with a keying material vector for each key. 
> You can then specify a different keys to use as part of sendmsg().

You can set the active shared key to use on a per assoc basis (via
socket options)-- you can basically add and delete shared keys and
set the active shared key on an assoc basis and I believe you can
achieve the above without needing ancillary data.  Note this also
works for 1-to-many sockets.

> Another time this would be useful if when restarting with authenticated
> cookie-echo chunks.  The application can issue a sendmsg() stating which
> key should be used.  The restart procedure then wouldn't have to do anything
> special.

Associations cannot restart if you authenticate cookie-echo chunks
since the restarting side's new assoc will have picked a new random
parameter and might (though probably not likely) have a different
set of chunks and/or hmac ids listed.  Only the shared keys are set
by the user, not the random parameter contents.

--peter


> -vlad

--------------ms000402030607060108060100
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJBzCC
At4wggJHoAMCAQICEFnRkKrCzpcCm7Il9L1WF6UwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE
BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT
I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA3MDQyNDA0NTY0MloX
DTA4MDQyMzA0NTY0MlowRDEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEhMB8G
CSqGSIb3DQEJARYScGV0ZXIubGVpQGllZWUub3JnMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEAu50a+sbvLQEzBhajGCsDC4hIqrEfWoVvaBV5nKxPl25h3omo1MIQX4kipB+l
Firh5iWbvNck8S69LQT8NnflXR5Bn12Z59trQAdxtTn7C05OQ5DXAOOaelsR96PA6wanyt29
OnEaMJeraujnRYKC1NUzOm8Tdh5esNEjYyfLnKTaXXKaNv85WMIzJo5HFTe1MKXVSWq/JZ5f
oF29Es4GM8xM69SxPZmnH3X2iz1+6WfCNfm7VXw6ouIyq3XgO5u4oZ6fdYRp4h++BY7smI3H
v/66VZhY0x33UHr0leiTSvh8Ydy2M99DfeDvWp/QAL0sc9qPgaaaWXEE1VcJWiZ4JQIDAQAB
oy8wLTAdBgNVHREEFjAUgRJwZXRlci5sZWlAaWVlZS5vcmcwDAYDVR0TAQH/BAIwADANBgkq
hkiG9w0BAQUFAAOBgQAoRiQhOgTbRhmT7MfkNOuv6mByra6PCcp/A5eWNxlhW0wVVZWTDP9U
AIG2I2OdR5HShv+myZd1PNTrdzE6g+MjEYq9M8JBzrkQSX7rQ3tTlev9l6v5PZjb+3bBs5HN
/XnH/130LB0EM/kdZ+61ATeGJPdS0D2ZlSz6Q/Neu/ETNTCCAt4wggJHoAMCAQICEFnRkKrC
zpcCm7Il9L1WF6UwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRo
YXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBG
cmVlbWFpbCBJc3N1aW5nIENBMB4XDTA3MDQyNDA0NTY0MloXDTA4MDQyMzA0NTY0MlowRDEf
MB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEhMB8GCSqGSIb3DQEJARYScGV0ZXIu
bGVpQGllZWUub3JnMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAu50a+sbvLQEz
BhajGCsDC4hIqrEfWoVvaBV5nKxPl25h3omo1MIQX4kipB+lFirh5iWbvNck8S69LQT8Nnfl
XR5Bn12Z59trQAdxtTn7C05OQ5DXAOOaelsR96PA6wanyt29OnEaMJeraujnRYKC1NUzOm8T
dh5esNEjYyfLnKTaXXKaNv85WMIzJo5HFTe1MKXVSWq/JZ5foF29Es4GM8xM69SxPZmnH3X2
iz1+6WfCNfm7VXw6ouIyq3XgO5u4oZ6fdYRp4h++BY7smI3Hv/66VZhY0x33UHr0leiTSvh8
Ydy2M99DfeDvWp/QAL0sc9qPgaaaWXEE1VcJWiZ4JQIDAQABoy8wLTAdBgNVHREEFjAUgRJw
ZXRlci5sZWlAaWVlZS5vcmcwDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOBgQAoRiQh
OgTbRhmT7MfkNOuv6mByra6PCcp/A5eWNxlhW0wVVZWTDP9UAIG2I2OdR5HShv+myZd1PNTr
dzE6g+MjEYq9M8JBzrkQSX7rQ3tTlev9l6v5PZjb+3bBs5HN/XnH/130LB0EM/kdZ+61ATeG
JPdS0D2ZlSz6Q/Neu/ETNTCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJ
BgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEa
MBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2Vy
dmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTEr
MCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcw
MDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUg
Q29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1h
aWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065ypla
HmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FW
y688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEE
QB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2
oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3Js
MAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0x
MzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYf
qi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amcOY6MIE9l
X5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNkMIIDYAIBATB2
MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQu
MSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQWdGQqsLO
lwKbsiX0vVYXpTAJBgUrDgMCGgUAoIIBwzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwG
CSqGSIb3DQEJBTEPFw0wNzA3MTExODU3MzNaMCMGCSqGSIb3DQEJBDEWBBQMTNhlSeRFirbc
BLI1MHPkjyqowDBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA
gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBhQYJKwYBBAGCNxAE
MXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkg
THRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEFnR
kKrCzpcCm7Il9L1WF6UwgYcGCyqGSIb3DQEJEAILMXigdjBiMQswCQYDVQQGEwJaQTElMCMG
A1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBl
cnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEFnRkKrCzpcCm7Il9L1WF6UwDQYJKoZIhvcN
AQEBBQAEggEANaS4bU7cu5Z+Y4ygi4ivdNWX3ygffX6udQYW+z2Bp+e0yUOGmy7Mc99XnUDK
MVL95X5vCKPPiB+eWCFWeb049I4fF5nk88JnHaZbDxPwUxAcOnoUF5peVIKY+jsiauZF6z12
F4kd56UIY/E+OVIoZ45sycXM80PaOlBDKGus/xoUGWm4vldGp1Ogq6qWxCUat3tRvHv+9tKs
0WnZkc1+78y31I6M7CHWoLVi2cnCovz8S66yZEPq08F2eaLcG6Q+WdoZbKwoVGP5bNr6MX77
fIA7NsjfjpngGdjOxA5EJJzxBqCxKMiVaupU7QxIhm/0T8Kn+qJLs7JdtNEULK1oKQAAAAAA
AA==
--------------ms000402030607060108060100--





From tsvwg-bounces@ietf.org Wed Jul 11 15:59:32 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8iLQ-0005Pr-Ko; Wed, 11 Jul 2007 15:59:28 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I8iLP-0005Pe-OW
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 11 Jul 2007 15:59:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8iLO-0005PW-TI
	for tsvwg@ietf.org; Wed, 11 Jul 2007 15:59:26 -0400
Received: from atlrel8.hp.com ([156.153.255.206])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8iLK-000661-Fx
	for tsvwg@ietf.org; Wed, 11 Jul 2007 15:59:26 -0400
Received: from smtp1.fc.hp.com (smtp.cnd.hp.com [15.15.136.127])
	by atlrel8.hp.com (Postfix) with ESMTP id 555F934D19;
	Wed, 11 Jul 2007 15:59:05 -0400 (EDT)
Received: from [16.116.113.226] (galen.zko.hp.com [16.116.113.226])
	by smtp1.fc.hp.com (Postfix) with ESMTP id 4BD41148A52;
	Wed, 11 Jul 2007 19:58:58 +0000 (UTC)
Message-ID: <46953681.1020703@hp.com>
Date: Wed, 11 Jul 2007 15:58:57 -0400
From: Vlad Yasevich <vladislav.yasevich@hp.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070604)
MIME-Version: 1.0
To: Peter Lei <peter.lei@ieee.org>
Subject: Re: [Tsvwg] Re: sctp-auth questions
References: <4695027E.3040109@hp.com>	<A4E4BE23-2187-484D-B6BA-4B6B1DE756DB@lurchi.franken.de>	<46950BFB.9070006@hp.com>	<82DC7FDA-F1EA-45F4-9066-A8486203387E@lurchi.franken.de>	<46951FA3.8010005@ieee.org>
	<4695246D.8020304@hp.com> <4695281D.2000404@ieee.org>
In-Reply-To: <4695281D.2000404@ieee.org>
X-Enigmail-Version: 0.95.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
	Randall Stewart <rrs@cisco.com>, tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Peter Lei wrote:
> Vlad Yasevich wrote:
> 
>>>>> BTW, having an ancillary data option to specify the key id along with
>>>>> the sendmsg
>>>>> might also be useful, but that's a topic for the API spec.
>>> I disagree with this... why would you want/need to send individual
>>> SCTP messages on the same association with different keys?
>>>
>> Not the same association, but a 1-to-many endpoint.  Let's say you have
>> 3 different keys on the endpoint.  Each association on that endpoint
>> would have 3 keys as well with a keying material vector for each key.
>> You can then specify a different keys to use as part of sendmsg().
> 
> You can set the active shared key to use on a per assoc basis (via
> socket options)-- you can basically add and delete shared keys and
> set the active shared key on an assoc basis and I believe you can
> achieve the above without needing ancillary data.  Note this also
> works for 1-to-many sockets.

Yes, I now, but it's awkward to do this with socket options, if you don't
want to delete keys.

Calling setsockopt() before a send is annoying if you want to change keys.

> 
>> Another time this would be useful if when restarting with authenticated
>> cookie-echo chunks.  The application can issue a sendmsg() stating which
>> key should be used.  The restart procedure then wouldn't have to do
>> anything
>> special.
> 
> Associations cannot restart if you authenticate cookie-echo chunks
> since the restarting side's new assoc will have picked a new random
> parameter and might (though probably not likely) have a different
> set of chunks and/or hmac ids listed.  Only the shared keys are set
> by the user, not the random parameter contents.
> 

Just re-read the spec and can see how this wouldn't really work.  

What I don't understand now is how exactly the following text applies:

>                                                            In
>    case of INIT collision, the rules governing the handling of this
>    random number follow the same pattern as those for the Verification
>    Tag, as explained in section 5.2.4 of RFC2960 [5].

Does this mean that in addition to Vtag comparison in step 3, random
numbers must be compared as well?

Just checking since it's not clear.

Thanks
-vlad












From tsvwg-bounces@ietf.org Wed Jul 11 16:27:37 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8imL-0006yt-MO; Wed, 11 Jul 2007 16:27:17 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I8imK-0006yn-9m
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 11 Jul 2007 16:27:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8imK-0006yf-0G
	for tsvwg@ietf.org; Wed, 11 Jul 2007 16:27:16 -0400
Received: from drew.ipv6.franken.de ([2001:638:a02:a001:20e:cff:fe4a:feaa]
	helo=mail-n.franken.de) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I8imF-0006kQ-F8
	for tsvwg@ietf.org; Wed, 11 Jul 2007 16:27:15 -0400
Received: from [192.168.1.17] (p508FC255.dip.t-dialin.net [80.143.194.85])
	by mail-n.franken.de (Postfix) with ESMTP id 6726D8006DB9;
	Wed, 11 Jul 2007 22:27:09 +0200 (CEST)
	(KNF-authenticated sender: macmic)
In-Reply-To: <46953681.1020703@hp.com>
References: <4695027E.3040109@hp.com>	<A4E4BE23-2187-484D-B6BA-4B6B1DE756DB@lurchi.franken.de>	<46950BFB.9070006@hp.com>	<82DC7FDA-F1EA-45F4-9066-A8486203387E@lurchi.franken.de>	<46951FA3.8010005@ieee.org>
	<4695246D.8020304@hp.com> <4695281D.2000404@ieee.org>
	<46953681.1020703@hp.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <57CC3A66-0D0F-443C-A70D-9FA126A17A1D@lurchi.franken.de>
Content-Transfer-Encoding: 7bit
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Tsvwg] Re: sctp-auth questions
Date: Wed, 11 Jul 2007 22:27:14 +0200
To: Vlad Yasevich <vladislav.yasevich@hp.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 1.7 (+)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: Peter Lei <peter.lei@ieee.org>, Randall Stewart <rrs@cisco.com>,
	tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

On Jul 11, 2007, at 9:58 PM, Vlad Yasevich wrote:

> Peter Lei wrote:
>> Vlad Yasevich wrote:
>>
>>>>>> BTW, having an ancillary data option to specify the key id  
>>>>>> along with
>>>>>> the sendmsg
>>>>>> might also be useful, but that's a topic for the API spec.
>>>> I disagree with this... why would you want/need to send individual
>>>> SCTP messages on the same association with different keys?
>>>>
>>> Not the same association, but a 1-to-many endpoint.  Let's say  
>>> you have
>>> 3 different keys on the endpoint.  Each association on that endpoint
>>> would have 3 keys as well with a keying material vector for each  
>>> key.
>>> You can then specify a different keys to use as part of sendmsg().
>>
>> You can set the active shared key to use on a per assoc basis (via
>> socket options)-- you can basically add and delete shared keys and
>> set the active shared key on an assoc basis and I believe you can
>> achieve the above without needing ancillary data.  Note this also
>> works for 1-to-many sockets.
>
> Yes, I now, but it's awkward to do this with socket options, if you  
> don't
> want to delete keys.
>
> Calling setsockopt() before a send is annoying if you want to  
> change keys.
I do not think that you want to change the key for an association for
each send() call. At I do not see an application for that (right now).
So I think using the setsockopt for this is appropriate.
>
>>
>>> Another time this would be useful if when restarting with  
>>> authenticated
>>> cookie-echo chunks.  The application can issue a sendmsg()  
>>> stating which
>>> key should be used.  The restart procedure then wouldn't have to do
>>> anything
>>> special.
>>
>> Associations cannot restart if you authenticate cookie-echo chunks
>> since the restarting side's new assoc will have picked a new random
>> parameter and might (though probably not likely) have a different
>> set of chunks and/or hmac ids listed.  Only the shared keys are set
>> by the user, not the random parameter contents.
>>
>
> Just re-read the spec and can see how this wouldn't really work.
>
> What I don't understand now is how exactly the following text applies:
>
>>                                                            In
>>    case of INIT collision, the rules governing the handling of this
>>    random number follow the same pattern as those for the  
>> Verification
>>    Tag, as explained in section 5.2.4 of RFC2960 [5].
>
> Does this mean that in addition to Vtag comparison in step 3, random
> numbers must be compared as well?
In the processing of the INIT collision case you have already code
to decide which v-tags are used. You apply the same algorithm to
decide which random numbers are used.
>
> Just checking since it's not clear.
What exactly is not clear?
>
> Thanks
> -vlad
>
>
>
>
>
>
>
>






From tsvwg-bounces@ietf.org Wed Jul 11 16:49:33 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8j7r-0007ev-3a; Wed, 11 Jul 2007 16:49:31 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I8j7q-0007Z4-4X
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 11 Jul 2007 16:49:30 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8j7p-0007Tp-Lq
	for tsvwg@ietf.org; Wed, 11 Jul 2007 16:49:29 -0400
Received: from atlrel9.hp.com ([156.153.255.214])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8j7h-0000J8-G6
	for tsvwg@ietf.org; Wed, 11 Jul 2007 16:49:29 -0400
Received: from smtp1.fc.hp.com (smtp.fc.hp.com [15.15.136.127])
	by atlrel9.hp.com (Postfix) with ESMTP id B4B63355AE;
	Wed, 11 Jul 2007 16:48:12 -0400 (EDT)
Received: from [16.116.113.226] (galen.zko.hp.com [16.116.113.226])
	by smtp1.fc.hp.com (Postfix) with ESMTP id EA615146B83;
	Wed, 11 Jul 2007 20:48:11 +0000 (UTC)
Message-ID: <4695420B.3060208@hp.com>
Date: Wed, 11 Jul 2007 16:48:11 -0400
From: Vlad Yasevich <vladislav.yasevich@hp.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070604)
MIME-Version: 1.0
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Tsvwg] Re: sctp-auth questions
References: <4695027E.3040109@hp.com>	<A4E4BE23-2187-484D-B6BA-4B6B1DE756DB@lurchi.franken.de>	<46950BFB.9070006@hp.com>	<82DC7FDA-F1EA-45F4-9066-A8486203387E@lurchi.franken.de>	<46951FA3.8010005@ieee.org>
	<4695246D.8020304@hp.com> <4695281D.2000404@ieee.org>
	<46953681.1020703@hp.com>
	<57CC3A66-0D0F-443C-A70D-9FA126A17A1D@lurchi.franken.de>
In-Reply-To: <57CC3A66-0D0F-443C-A70D-9FA126A17A1D@lurchi.franken.de>
X-Enigmail-Version: 0.95.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: Peter Lei <peter.lei@ieee.org>, Randall Stewart <rrs@cisco.com>,
	tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Michael Tuexen wrote:
> On Jul 11, 2007, at 9:58 PM, Vlad Yasevich wrote:
> 
>> Peter Lei wrote:
>>> Vlad Yasevich wrote:
>>>
>>>>>>> BTW, having an ancillary data option to specify the key id along
>>>>>>> with
>>>>>>> the sendmsg
>>>>>>> might also be useful, but that's a topic for the API spec.
>>>>> I disagree with this... why would you want/need to send individual
>>>>> SCTP messages on the same association with different keys?
>>>>>
>>>> Not the same association, but a 1-to-many endpoint.  Let's say you have
>>>> 3 different keys on the endpoint.  Each association on that endpoint
>>>> would have 3 keys as well with a keying material vector for each key.
>>>> You can then specify a different keys to use as part of sendmsg().
>>>
>>> You can set the active shared key to use on a per assoc basis (via
>>> socket options)-- you can basically add and delete shared keys and
>>> set the active shared key on an assoc basis and I believe you can
>>> achieve the above without needing ancillary data.  Note this also
>>> works for 1-to-many sockets.
>>
>> Yes, I now, but it's awkward to do this with socket options, if you don't
>> want to delete keys.
>>
>> Calling setsockopt() before a send is annoying if you want to change
>> keys.
> I do not think that you want to change the key for an association for
> each send() call. At I do not see an application for that (right now).
> So I think using the setsockopt for this is appropriate.

Ok, I was an idea, and I'll drop it if it not useful.

>> Just re-read the spec and can see how this wouldn't really work.
>>
>> What I don't understand now is how exactly the following text applies:
>>
>>>                                                            In
>>>    case of INIT collision, the rules governing the handling of this
>>>    random number follow the same pattern as those for the Verification
>>>    Tag, as explained in section 5.2.4 of RFC2960 [5].
>>
>> Does this mean that in addition to Vtag comparison in step 3, random
>> numbers must be compared as well?
> In the processing of the INIT collision case you have already code
> to decide which v-tags are used. You apply the same algorithm to
> decide which random numbers are used.
>>
>> Just checking since it's not clear.
> What exactly is not clear?

Well, for one,  the section that's describing INIT collisions is 5.2.1.
If that's the section that should be referenced, then things clear up.

If 5.2.4 is the right section (Handle a COOKIE ECHO when a TCB exists),
then specifying specifics for random number comparison is necessary, IMO.

-vlad





From tsvwg-bounces@ietf.org Wed Jul 11 17:20:03 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8jbH-0000eV-JY; Wed, 11 Jul 2007 17:19:55 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I8jbG-0000at-Bs
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 11 Jul 2007 17:19:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8jbG-0000ak-2O
	for tsvwg@ietf.org; Wed, 11 Jul 2007 17:19:54 -0400
Received: from drew.ipv6.franken.de ([2001:638:a02:a001:20e:cff:fe4a:feaa]
	helo=mail-n.franken.de) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I8jbC-0007tt-CY
	for tsvwg@ietf.org; Wed, 11 Jul 2007 17:19:54 -0400
Received: from [192.168.1.17] (p508FC255.dip.t-dialin.net [80.143.194.85])
	by mail-n.franken.de (Postfix) with ESMTP id C201B80000BD;
	Wed, 11 Jul 2007 23:19:48 +0200 (CEST)
	(KNF-authenticated sender: macmic)
In-Reply-To: <4695420B.3060208@hp.com>
References: <4695027E.3040109@hp.com>	<A4E4BE23-2187-484D-B6BA-4B6B1DE756DB@lurchi.franken.de>	<46950BFB.9070006@hp.com>	<82DC7FDA-F1EA-45F4-9066-A8486203387E@lurchi.franken.de>	<46951FA3.8010005@ieee.org>
	<4695246D.8020304@hp.com> <4695281D.2000404@ieee.org>
	<46953681.1020703@hp.com>
	<57CC3A66-0D0F-443C-A70D-9FA126A17A1D@lurchi.franken.de>
	<4695420B.3060208@hp.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <AC694FBD-78AE-423C-9E3B-546D716ED424@lurchi.franken.de>
Content-Transfer-Encoding: 7bit
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Tsvwg] Re: sctp-auth questions
Date: Wed, 11 Jul 2007 23:19:54 +0200
To: Vlad Yasevich <vladislav.yasevich@hp.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 1.7 (+)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: Peter Lei <peter.lei@ieee.org>, Randall Stewart <rrs@cisco.com>,
	tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org


On Jul 11, 2007, at 10:48 PM, Vlad Yasevich wrote:

> Michael Tuexen wrote:
>> On Jul 11, 2007, at 9:58 PM, Vlad Yasevich wrote:
>>
>>> Peter Lei wrote:
>>>> Vlad Yasevich wrote:
>>>>
>>>>>>>> BTW, having an ancillary data option to specify the key id  
>>>>>>>> along
>>>>>>>> with
>>>>>>>> the sendmsg
>>>>>>>> might also be useful, but that's a topic for the API spec.
>>>>>> I disagree with this... why would you want/need to send  
>>>>>> individual
>>>>>> SCTP messages on the same association with different keys?
>>>>>>
>>>>> Not the same association, but a 1-to-many endpoint.  Let's say  
>>>>> you have
>>>>> 3 different keys on the endpoint.  Each association on that  
>>>>> endpoint
>>>>> would have 3 keys as well with a keying material vector for  
>>>>> each key.
>>>>> You can then specify a different keys to use as part of sendmsg().
>>>>
>>>> You can set the active shared key to use on a per assoc basis (via
>>>> socket options)-- you can basically add and delete shared keys and
>>>> set the active shared key on an assoc basis and I believe you can
>>>> achieve the above without needing ancillary data.  Note this also
>>>> works for 1-to-many sockets.
>>>
>>> Yes, I now, but it's awkward to do this with socket options, if  
>>> you don't
>>> want to delete keys.
>>>
>>> Calling setsockopt() before a send is annoying if you want to change
>>> keys.
>> I do not think that you want to change the key for an association for
>> each send() call. At I do not see an application for that (right  
>> now).
>> So I think using the setsockopt for this is appropriate.
>
> Ok, I was an idea, and I'll drop it if it not useful.
>
>>> Just re-read the spec and can see how this wouldn't really work.
>>>
>>> What I don't understand now is how exactly the following text  
>>> applies:
>>>
>>>>                                                            In
>>>>    case of INIT collision, the rules governing the handling of this
>>>>    random number follow the same pattern as those for the  
>>>> Verification
>>>>    Tag, as explained in section 5.2.4 of RFC2960 [5].
>>>
>>> Does this mean that in addition to Vtag comparison in step 3, random
>>> numbers must be compared as well?
>> In the processing of the INIT collision case you have already code
>> to decide which v-tags are used. You apply the same algorithm to
>> decide which random numbers are used.
>>>
>>> Just checking since it's not clear.
>> What exactly is not clear?
>
> Well, for one,  the section that's describing INIT collisions is  
> 5.2.1.
> If that's the section that should be referenced, then things clear up.
>
> If 5.2.4 is the right section (Handle a COOKIE ECHO when a TCB  
> exists),
> then specifying specifics for random number comparison is  
> necessary, IMO.
You do not use the random numbers to figure out which Action/Description
applies. You just use the tags for that. You select the random numbers
like you do it for the v-tags. So no comparisons for the random numbers
are necessary.
>
> -vlad
>






From tsvwg-bounces@ietf.org Wed Jul 11 20:50:36 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8msx-0003KG-Pa; Wed, 11 Jul 2007 20:50:23 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I8msw-0003J9-IB
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 11 Jul 2007 20:50:22 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8msv-0003I9-L9
	for tsvwg@ietf.org; Wed, 11 Jul 2007 20:50:21 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8msv-000696-Eq
	for tsvwg@ietf.org; Wed, 11 Jul 2007 20:50:21 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 11 Jul 2007 20:50:21 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAFoXlUZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,529,1175486400"; 
	d="scan'208"; a="125832378:sNHT21613292"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6C0oKNH011247
	for <tsvwg@ietf.org>; Wed, 11 Jul 2007 20:50:20 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l6C0oGs2027074
	for <tsvwg@ietf.org>; Thu, 12 Jul 2007 00:50:20 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 11 Jul 2007 20:50:17 -0400
Received: from jmpolk-wxp.cisco.com ([10.89.20.175]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 11 Jul 2007 20:50:16 -0400
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 11 Jul 2007 19:50:16 -0500
To: tsvwg <tsvwg@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-ID: <XFE-RTP-201wTlOKSa9000000db@xfe-rtp-201.amer.cisco.com>
X-OriginalArrivalTime: 12 Jul 2007 00:50:17.0093 (UTC)
	FILETIME=[9D53DB50:01C7C41E]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=194; t=1184201421;
	x=1185065421; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jmpolk@cisco.com;
	z=From:=20=22James=20M.=20Polk=22=20<jmpolk@cisco.com>
	|Subject:=20DRAFT=20Agenda=20for=20TSVWG=20in=20Chicago
	|Sender:=20 |To:=20tsvwg=20<tsvwg@ietf.org>;
	bh=MUidXW4mZIoxly/L21leamPze1nk/cPSOGgTZPbmAG8=;
	b=FqAa4ZQ71KHQDi3vC5zJQit2mP4ag1M5qZ9UWNISv0B7UPBcqXakIGYj4fRnYTyqET671fIr
	Nt020LE0uRyEVk9k2mWCP9vv1b/JcWgE9OGW1MIhh+6jqEHHe0S5NKK3;
Authentication-Results: rtp-dkim-2; header.From=jmpolk@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Subject: [Tsvwg] DRAFT Agenda for TSVWG in Chicago
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

TSVWG

http://www3.ietf.org/proceedings/07jul/agenda/tsvwg.txt

Please review this *DRAFT* agenda

Let the bashing start

cheers,

James
Lars
Magnus
         IETF TSVWG co-chairs 





From tsvwg-bounces@ietf.org Thu Jul 12 09:37:30 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8yrD-0002ON-1n; Thu, 12 Jul 2007 09:37:23 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I8yrB-0002O7-Bz
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 12 Jul 2007 09:37:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8yrA-0002Mr-Lf
	for tsvwg@ietf.org; Thu, 12 Jul 2007 09:37:20 -0400
Received: from atlrel8.hp.com ([156.153.255.206])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8yr6-0002MT-4S
	for tsvwg@ietf.org; Thu, 12 Jul 2007 09:37:20 -0400
Received: from smtp2.fc.hp.com (smtp2.fc.hp.com [15.11.136.114])
	by atlrel8.hp.com (Postfix) with ESMTP id 1419036C53;
	Thu, 12 Jul 2007 09:36:51 -0400 (EDT)
Received: from [16.116.113.226] (galen.zko.hp.com [16.116.113.226])
	by smtp2.fc.hp.com (Postfix) with ESMTP id 2AB99190DA8;
	Thu, 12 Jul 2007 13:36:48 +0000 (UTC)
Message-ID: <46962E6F.5000203@hp.com>
Date: Thu, 12 Jul 2007 09:36:47 -0400
From: Vlad Yasevich <vladislav.yasevich@hp.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070604)
MIME-Version: 1.0
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Tsvwg] Re: sctp-auth questions
References: <4695027E.3040109@hp.com>	<A4E4BE23-2187-484D-B6BA-4B6B1DE756DB@lurchi.franken.de>	<46950BFB.9070006@hp.com>	<82DC7FDA-F1EA-45F4-9066-A8486203387E@lurchi.franken.de>	<46951FA3.8010005@ieee.org>
	<4695246D.8020304@hp.com> <4695281D.2000404@ieee.org>
	<46953681.1020703@hp.com>
	<57CC3A66-0D0F-443C-A70D-9FA126A17A1D@lurchi.franken.de>
	<4695420B.3060208@hp.com>
	<AC694FBD-78AE-423C-9E3B-546D716ED424@lurchi.franken.de>
In-Reply-To: <AC694FBD-78AE-423C-9E3B-546D716ED424@lurchi.franken.de>
X-Enigmail-Version: 0.95.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: Peter Lei <peter.lei@ieee.org>, Randall Stewart <rrs@cisco.com>,
	tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi Michael

Michael Tuexen wrote:
>>>> Just checking since it's not clear.
>>> What exactly is not clear?
>>
>> Well, for one,  the section that's describing INIT collisions is 5.2.1.
>> If that's the section that should be referenced, then things clear up.
>>
>> If 5.2.4 is the right section (Handle a COOKIE ECHO when a TCB exists),
>> then specifying specifics for random number comparison is necessary, IMO.
> You do not use the random numbers to figure out which Action/Description
> applies. You just use the tags for that. You select the random numbers
> like you do it for the v-tags. So no comparisons for the random numbers
> are necessary.

I am probably being really dense here, but it still not clear what particular
item from 2960 Section 5.2.4 applies.

The statement from draft-sctp-auth is:
   In case of INIT collision, the rules governing the handling of this
   random number follow the same pattern as those for the Verification
   Tag, as explained in section 5.2.4 of RFC2960 [5].  Therefore each
   endpoint knows its own random number and the peer's random number
   after the association has been established.


Now, section 5.2.4 is fairly long and has multiple rules that describe
handling of verification tags.

Rule 3 from that section mentions comparison of the tag carried by the
cookie to the association v-tag.

Rule 5 (table) specifies tag and tie-tag comparisons (my guess is this doesn't apply).

Action B specifies the handling of V-TAG during simultaneous start (this is probably
what's referred to in the auth spec)

So, is Action B what's being referred to by the paragraph in sctp-auth?
If yes, that could be made clearer.

Thanks
-vlad





From tsvwg-bounces@ietf.org Thu Jul 12 10:56:20 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I905P-0003Nc-2V; Thu, 12 Jul 2007 10:56:07 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I905O-0003NR-19
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 12 Jul 2007 10:56:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I905N-0003NG-AS
	for tsvwg@ietf.org; Thu, 12 Jul 2007 10:56:05 -0400
Received: from drew.ipv6.franken.de ([2001:638:a02:a001:20e:cff:fe4a:feaa]
	helo=mail-n.franken.de) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I905I-0004sa-Pl
	for tsvwg@ietf.org; Thu, 12 Jul 2007 10:56:05 -0400
Received: from [192.168.1.17] (p508FF965.dip.t-dialin.net [80.143.249.101])
	by mail-n.franken.de (Postfix) with ESMTP id 19DD18000094;
	Thu, 12 Jul 2007 16:55:59 +0200 (CEST)
	(KNF-authenticated sender: macmic)
In-Reply-To: <46962E6F.5000203@hp.com>
References: <4695027E.3040109@hp.com>	<A4E4BE23-2187-484D-B6BA-4B6B1DE756DB@lurchi.franken.de>	<46950BFB.9070006@hp.com>	<82DC7FDA-F1EA-45F4-9066-A8486203387E@lurchi.franken.de>	<46951FA3.8010005@ieee.org>
	<4695246D.8020304@hp.com> <4695281D.2000404@ieee.org>
	<46953681.1020703@hp.com>
	<57CC3A66-0D0F-443C-A70D-9FA126A17A1D@lurchi.franken.de>
	<4695420B.3060208@hp.com>
	<AC694FBD-78AE-423C-9E3B-546D716ED424@lurchi.franken.de>
	<46962E6F.5000203@hp.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <A507B646-F854-4F69-B383-90D297A1C271@lurchi.franken.de>
Content-Transfer-Encoding: 7bit
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Tsvwg] Re: sctp-auth questions
Date: Thu, 12 Jul 2007 16:55:57 +0200
To: Vlad Yasevich <vladislav.yasevich@hp.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: Peter Lei <peter.lei@ieee.org>, Randall Stewart <rrs@cisco.com>,
	tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi Vlad,

let me describe this in a different way:

Both INIT and the INIT-ACK chunks contain Initiate Tags, just like
the RANDOM parameters. RFC 2960 describes how you handle the case
where you receive these chunk in an "unexpected" state. The result
is that both sides use on Initiate Tag. For SCTP-AUTH you should
use the same mechanism for the the RANDOM parameter as for the
initiate tag. Once you decide which Initiate Tag you use, you
know that you use the RANDOM parameter of the chunk containing
that Initiate Tag.

Best regards
Michael

On Jul 12, 2007, at 3:36 PM, Vlad Yasevich wrote:

> Hi Michael
>
> Michael Tuexen wrote:
>>>>> Just checking since it's not clear.
>>>> What exactly is not clear?
>>>
>>> Well, for one,  the section that's describing INIT collisions is  
>>> 5.2.1.
>>> If that's the section that should be referenced, then things  
>>> clear up.
>>>
>>> If 5.2.4 is the right section (Handle a COOKIE ECHO when a TCB  
>>> exists),
>>> then specifying specifics for random number comparison is  
>>> necessary, IMO.
>> You do not use the random numbers to figure out which Action/ 
>> Description
>> applies. You just use the tags for that. You select the random  
>> numbers
>> like you do it for the v-tags. So no comparisons for the random  
>> numbers
>> are necessary.
>
> I am probably being really dense here, but it still not clear what  
> particular
> item from 2960 Section 5.2.4 applies.
>
> The statement from draft-sctp-auth is:
>    In case of INIT collision, the rules governing the handling of this
>    random number follow the same pattern as those for the Verification
>    Tag, as explained in section 5.2.4 of RFC2960 [5].  Therefore each
>    endpoint knows its own random number and the peer's random number
>    after the association has been established.
>
>
> Now, section 5.2.4 is fairly long and has multiple rules that describe
> handling of verification tags.
>
> Rule 3 from that section mentions comparison of the tag carried by the
> cookie to the association v-tag.
>
> Rule 5 (table) specifies tag and tie-tag comparisons (my guess is  
> this doesn't apply).
>
> Action B specifies the handling of V-TAG during simultaneous start  
> (this is probably
> what's referred to in the auth spec)
>
> So, is Action B what's being referred to by the paragraph in sctp- 
> auth?
> If yes, that could be made clearer.
>
> Thanks
> -vlad
>






From tsvwg-bounces@ietf.org Thu Jul 12 11:09:39 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I90IS-0002h3-ME; Thu, 12 Jul 2007 11:09:36 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I90IP-0002gv-AJ
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 12 Jul 2007 11:09:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I90IP-0002gn-0U
	for tsvwg@ietf.org; Thu, 12 Jul 2007 11:09:33 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I90IK-0005Aq-Hi
	for tsvwg@ietf.org; Thu, 12 Jul 2007 11:09:32 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 12 Jul 2007 08:09:28 -0700
X-IronPort-AV: i="unknown";  a="180973365:sNHT0"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6CF9SiP011339; 
	Thu, 12 Jul 2007 08:09:28 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l6CF8unQ019414;
	Thu, 12 Jul 2007 15:09:27 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Jul 2007 08:09:24 -0700
Received: from [127.0.0.1] ([171.68.225.134]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Jul 2007 08:09:23 -0700
Message-ID: <4696445A.30502@cisco.com>
Date: Thu, 12 Jul 2007 11:10:18 -0400
From: Randall Stewart <rrs@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.13) Gecko/20070601
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Tsvwg] Re: sctp-auth questions
References: <4695027E.3040109@hp.com>	<A4E4BE23-2187-484D-B6BA-4B6B1DE756DB@lurchi.franken.de>	<46950BFB.9070006@hp.com>	<82DC7FDA-F1EA-45F4-9066-A8486203387E@lurchi.franken.de>	<46951FA3.8010005@ieee.org>
	<4695246D.8020304@hp.com> <4695281D.2000404@ieee.org>
	<46953681.1020703@hp.com>
	<57CC3A66-0D0F-443C-A70D-9FA126A17A1D@lurchi.franken.de>
	<4695420B.3060208@hp.com>
	<AC694FBD-78AE-423C-9E3B-546D716ED424@lurchi.franken.de>
	<46962E6F.5000203@hp.com>
	<A507B646-F854-4F69-B383-90D297A1C271@lurchi.franken.de>
In-Reply-To: <A507B646-F854-4F69-B383-90D297A1C271@lurchi.franken.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Jul 2007 15:09:23.0602 (UTC)
	FILETIME=[A170EF20:01C7C496]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3008; t=1184252968;
	x=1185116968; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=rrs@cisco.com;
	z=From:=20Randall=20Stewart=20<rrs@cisco.com>
	|Subject:=20Re=3A=20[Tsvwg]=20Re=3A=20sctp-auth=20questions
	|Sender:=20; bh=aovvBmr1cBRBP3dFWsPZczfrwxL2YAGybBmyvlv4tQc=;
	b=Dn11O5d5j3Lt3xjsohBXyhno8Zf70p2LnqZmFP+O0S1UfbMPF3dCrD45x6cUuqXJcjz57Wbc
	qtdSfFCdNQ8U6fnNSYRE+MhC7nSbnzrBZ3/qnWmJg+LaojxS76JA0PxA;
Authentication-Results: sj-dkim-2; header.From=rrs@cisco.com; dkim=pass (sig
	from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>, Peter Lei <peter.lei@ieee.org>,
	tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Michael Tuexen wrote:
> Hi Vlad,
> 
> let me describe this in a different way:
> 
> Both INIT and the INIT-ACK chunks contain Initiate Tags, just like
> the RANDOM parameters. RFC 2960 describes how you handle the case
> where you receive these chunk in an "unexpected" state. The result
> is that both sides use on Initiate Tag. For SCTP-AUTH you should
> use the same mechanism for the the RANDOM parameter as for the
> initiate tag. Once you decide which Initiate Tag you use, you
> know that you use the RANDOM parameter of the chunk containing
> that Initiate Tag.

Let me just add one thing.. that might help too.

Basically Vlad when the tie-tags match and you would
accept the association.. (replacing what was in
your INIT since we are talking about the collision
case here) and use the tags in the cookie.. then
you would use the random parameters from that cookie.

R


> 
> Best regards
> Michael
> 
> On Jul 12, 2007, at 3:36 PM, Vlad Yasevich wrote:
> 
>> Hi Michael
>>
>> Michael Tuexen wrote:
>>
>>>>>> Just checking since it's not clear.
>>>>>
>>>>> What exactly is not clear?
>>>>
>>>>
>>>> Well, for one,  the section that's describing INIT collisions is  
>>>> 5.2.1.
>>>> If that's the section that should be referenced, then things  clear up.
>>>>
>>>> If 5.2.4 is the right section (Handle a COOKIE ECHO when a TCB  
>>>> exists),
>>>> then specifying specifics for random number comparison is  
>>>> necessary, IMO.
>>>
>>> You do not use the random numbers to figure out which Action/ 
>>> Description
>>> applies. You just use the tags for that. You select the random  numbers
>>> like you do it for the v-tags. So no comparisons for the random  numbers
>>> are necessary.
>>
>>
>> I am probably being really dense here, but it still not clear what  
>> particular
>> item from 2960 Section 5.2.4 applies.
>>
>> The statement from draft-sctp-auth is:
>>    In case of INIT collision, the rules governing the handling of this
>>    random number follow the same pattern as those for the Verification
>>    Tag, as explained in section 5.2.4 of RFC2960 [5].  Therefore each
>>    endpoint knows its own random number and the peer's random number
>>    after the association has been established.
>>
>>
>> Now, section 5.2.4 is fairly long and has multiple rules that describe
>> handling of verification tags.
>>
>> Rule 3 from that section mentions comparison of the tag carried by the
>> cookie to the association v-tag.
>>
>> Rule 5 (table) specifies tag and tie-tag comparisons (my guess is  
>> this doesn't apply).
>>
>> Action B specifies the handling of V-TAG during simultaneous start  
>> (this is probably
>> what's referred to in the auth spec)
>>
>> So, is Action B what's being referred to by the paragraph in sctp- auth?
>> If yes, that could be made clearer.
>>
>> Thanks
>> -vlad
>>
> 


-- 
Randall Stewart
NSSTG - Cisco Systems Inc.
803-345-0369 <or> 803-317-4952 (cell)





From tsvwg-bounces@ietf.org Thu Jul 12 11:20:20 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I90So-0002ic-25; Thu, 12 Jul 2007 11:20:18 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I90Sm-0002f2-Vt
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 12 Jul 2007 11:20:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I90Sm-0002d6-Jg
	for tsvwg@ietf.org; Thu, 12 Jul 2007 11:20:16 -0400
Received: from atlrel7.hp.com ([156.153.255.213])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I90SY-0005dj-8z
	for tsvwg@ietf.org; Thu, 12 Jul 2007 11:20:16 -0400
Received: from smtp2.fc.hp.com (smtp.fc.hp.com [15.11.136.114])
	by atlrel7.hp.com (Postfix) with ESMTP id 8BCAF35D37;
	Thu, 12 Jul 2007 11:19:36 -0400 (EDT)
Received: from [16.116.113.226] (galen.zko.hp.com [16.116.113.226])
	by smtp2.fc.hp.com (Postfix) with ESMTP id 038BB190BD4;
	Thu, 12 Jul 2007 15:18:49 +0000 (UTC)
Message-ID: <46964659.9090402@hp.com>
Date: Thu, 12 Jul 2007 11:18:49 -0400
From: Vlad Yasevich <vladislav.yasevich@hp.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070604)
MIME-Version: 1.0
To: Randall Stewart <rrs@cisco.com>
Subject: Re: [Tsvwg] Re: sctp-auth questions
References: <4695027E.3040109@hp.com>	<A4E4BE23-2187-484D-B6BA-4B6B1DE756DB@lurchi.franken.de>	<46950BFB.9070006@hp.com>	<82DC7FDA-F1EA-45F4-9066-A8486203387E@lurchi.franken.de>	<46951FA3.8010005@ieee.org>
	<4695246D.8020304@hp.com> <4695281D.2000404@ieee.org>
	<46953681.1020703@hp.com>
	<57CC3A66-0D0F-443C-A70D-9FA126A17A1D@lurchi.franken.de>
	<4695420B.3060208@hp.com>
	<AC694FBD-78AE-423C-9E3B-546D716ED424@lurchi.franken.de>
	<46962E6F.5000203@hp.com>
	<A507B646-F854-4F69-B383-90D297A1C271@lurchi.franken.de>
	<4696445A.30502@cisco.com>
In-Reply-To: <4696445A.30502@cisco.com>
X-Enigmail-Version: 0.95.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
Cc: Peter Lei <peter.lei@ieee.org>,
	Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Randall Stewart wrote:
> Michael Tuexen wrote:
>> Hi Vlad,
>>
>> let me describe this in a different way:
>>
>> Both INIT and the INIT-ACK chunks contain Initiate Tags, just like
>> the RANDOM parameters. RFC 2960 describes how you handle the case
>> where you receive these chunk in an "unexpected" state. The result
>> is that both sides use on Initiate Tag. For SCTP-AUTH you should
>> use the same mechanism for the the RANDOM parameter as for the
>> initiate tag. Once you decide which Initiate Tag you use, you
>> know that you use the RANDOM parameter of the chunk containing
>> that Initiate Tag.
> 
> Let me just add one thing.. that might help too.
> 
> Basically Vlad when the tie-tags match and you would
> accept the association.. (replacing what was in
> your INIT since we are talking about the collision
> case here) and use the tags in the cookie.. then
> you would use the random parameters from that cookie.
> 
> R

OK.  So basically the handling of the Random parameter is the
same as behavior for Verification TAg as describe in Action B of
section 5.2.4.

That make it absolutely clear, thanks.  The wording in the spec
was not that clear.

-vlad

> 
> 
>>
>> Best regards
>> Michael
>>
>> On Jul 12, 2007, at 3:36 PM, Vlad Yasevich wrote:
>>
>>> Hi Michael
>>>
>>> Michael Tuexen wrote:
>>>
>>>>>>> Just checking since it's not clear.
>>>>>>
>>>>>> What exactly is not clear?
>>>>>
>>>>>
>>>>> Well, for one,  the section that's describing INIT collisions is 
>>>>> 5.2.1.
>>>>> If that's the section that should be referenced, then things  clear
>>>>> up.
>>>>>
>>>>> If 5.2.4 is the right section (Handle a COOKIE ECHO when a TCB 
>>>>> exists),
>>>>> then specifying specifics for random number comparison is 
>>>>> necessary, IMO.
>>>>
>>>> You do not use the random numbers to figure out which Action/
>>>> Description
>>>> applies. You just use the tags for that. You select the random  numbers
>>>> like you do it for the v-tags. So no comparisons for the random 
>>>> numbers
>>>> are necessary.
>>>
>>>
>>> I am probably being really dense here, but it still not clear what 
>>> particular
>>> item from 2960 Section 5.2.4 applies.
>>>
>>> The statement from draft-sctp-auth is:
>>>    In case of INIT collision, the rules governing the handling of this
>>>    random number follow the same pattern as those for the Verification
>>>    Tag, as explained in section 5.2.4 of RFC2960 [5].  Therefore each
>>>    endpoint knows its own random number and the peer's random number
>>>    after the association has been established.
>>>
>>>
>>> Now, section 5.2.4 is fairly long and has multiple rules that describe
>>> handling of verification tags.
>>>
>>> Rule 3 from that section mentions comparison of the tag carried by the
>>> cookie to the association v-tag.
>>>
>>> Rule 5 (table) specifies tag and tie-tag comparisons (my guess is 
>>> this doesn't apply).
>>>
>>> Action B specifies the handling of V-TAG during simultaneous start 
>>> (this is probably
>>> what's referred to in the auth spec)
>>>
>>> So, is Action B what's being referred to by the paragraph in sctp- auth?
>>> If yes, that could be made clearer.
>>>
>>> Thanks
>>> -vlad
>>>
>>
> 
> 






From tsvwg-bounces@ietf.org Thu Jul 12 11:23:37 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I90W0-0005zb-Rb; Thu, 12 Jul 2007 11:23:36 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I90Vz-0005zK-BM
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 12 Jul 2007 11:23:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I90Vz-0005z9-1k
	for tsvwg@ietf.org; Thu, 12 Jul 2007 11:23:35 -0400
Received: from drew.ipv6.franken.de ([2001:638:a02:a001:20e:cff:fe4a:feaa]
	helo=mail-n.franken.de) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I90Vu-0005sj-Mu
	for tsvwg@ietf.org; Thu, 12 Jul 2007 11:23:35 -0400
Received: from [192.168.1.17] (p508FF965.dip.t-dialin.net [80.143.249.101])
	by mail-n.franken.de (Postfix) with ESMTP id 00B9B801AC05
	for <tsvwg@ietf.org>; Thu, 12 Jul 2007 17:23:29 +0200 (CEST)
	(KNF-authenticated sender: macmic)
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Transfer-Encoding: 7bit
Message-Id: <15D5F2FA-1E74-4F97-B14A-1E0D443C035B@lurchi.franken.de>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: TSWG <tsvwg@ietf.org>
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Date: Thu, 12 Jul 2007 17:23:29 +0200
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Subject: [Tsvwg] SCTP Interop registration deadline is approaching
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Dear all,

I just want to let you know that the registration deadline for
the 9th SCTP Interop, this time held in Kyoto, is approaching.
It is July 15th. You can find more information at
http://www.interop.sctp.jp

If you have further question, just send me or Randall Stewart
an e-mail.

Happy SCTPing
Michael






From tsvwg-bounces@ietf.org Thu Jul 12 13:15:15 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I92Fz-0000ai-Nz; Thu, 12 Jul 2007 13:15:11 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I92Fy-0000aP-FN
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 12 Jul 2007 13:15:10 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I92Fy-0000aG-4L; Thu, 12 Jul 2007 13:15:10 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I92Fx-00043f-SR; Thu, 12 Jul 2007 13:15:10 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id C632B2AC9D;
	Thu, 12 Jul 2007 17:15:09 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I92Fv-0005LW-C5; Thu, 12 Jul 2007 13:15:07 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I92Fv-0005LW-C5@stiedprstage1.ietf.org>
Date: Thu, 12 Jul 2007 13:15:07 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: tsvwg@ietf.org
Subject: [Tsvwg] I-D ACTION:draft-ietf-tsvwg-emergency-rsvp-03.txt 
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Transport Area Working Group Working Group of the IETF.

	Title		: Resource ReSerVation Protovol (RSVP) Extensions for Emergency Services
	Author(s)	: F. Le Faucheur, et al.
	Filename	: draft-ietf-tsvwg-emergency-rsvp-03.txt
	Pages		: 28
	Date		: 2007-7-12
	
An Emergency Telecommunications Service (ETS) requires the ability to 
   provide an elevated probability of session establishment to an 
   authorized user in times of network congestion (typically, during a 
   crisis). When supported over the Internet Protocol suite, this may be 
   facilitated through a network layer admission control solution, which 
   supports prioritized access to resources (e.g., bandwidth). These 
   resources may be explicitly set aside for emergency services, or they 
   may be shared with other sessions.    This document specifies RSVP extensions that can be used to support 
   such an admission priority capability at the network layer. Note that 
   these extensions represent one possible solution component in 
   satisfying ETS requirements. Other solution components, or other 
   solutions, are outside the scope of this document.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-emergency-rsvp-03.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-tsvwg-emergency-rsvp-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-tsvwg-emergency-rsvp-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-7-12120222.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-tsvwg-emergency-rsvp-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-tsvwg-emergency-rsvp-03.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-7-12120222.I-D@ietf.org>


--OtherAccess--

--NextPart--





From tsvwg-bounces@ietf.org Thu Jul 12 14:15:48 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I93CZ-0002j9-0N; Thu, 12 Jul 2007 14:15:43 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1I93CO-0002PI-R8
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 12 Jul 2007 14:15:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I93CO-0002P7-F5; Thu, 12 Jul 2007 14:15:32 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I93CO-0007X5-6s; Thu, 12 Jul 2007 14:15:32 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 2FCF632A4B;
	Thu, 12 Jul 2007 18:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I93Bu-0002NP-1r; Thu, 12 Jul 2007 14:15:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I93Bu-0002NP-1r@stiedprstage1.ietf.org>
Date: Thu, 12 Jul 2007 14:15:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: tsvwg@ietf.org
Subject: [Tsvwg] I-D ACTION:draft-ietf-tsvwg-diffserv-class-aggr-03.txt 
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Transport Area Working Group Working Group of the IETF.

	Title		: Aggregation of DiffServ Service Classes
	Author(s)	: K. Chan, et al.
	Filename	: draft-ietf-tsvwg-diffserv-class-aggr-03.txt
	Pages		: 19
	Date		: 2007-7-12
	
In the core of a high capacity network, service differentiation is
   still needed to support applications' utilization of the network.
   Applications with similar traffic characteristics and performance
   requirements are mapped into diffserv service classes based on end-
   to-end behavior requirements of the applications as indicated by
   Diffserv Service Classes [5].  However, some network segments may be
   configured in such a way that a single forwarding treatment may
   satisfy the traffic characteristics and performance requirements of
   two or more service classes.  In these cases, it may be desirable to
   aggregate two or more Diffserv Service Classes [5] into a single
   forwarding treatment.  This document provides guidelines for the
   aggregation of Diffserv Service Classes [5] into forwarding
   treatments.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-diffserv-class-aggr-03.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-tsvwg-diffserv-class-aggr-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-tsvwg-diffserv-class-aggr-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-7-12132635.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-tsvwg-diffserv-class-aggr-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-tsvwg-diffserv-class-aggr-03.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-7-12132635.I-D@ietf.org>


--OtherAccess--

--NextPart--





From tsvwg-bounces@ietf.org Mon Jul 16 11:48:33 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IASoH-0008WM-P5; Mon, 16 Jul 2007 11:48:29 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IASoG-0008TN-Lp
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 16 Jul 2007 11:48:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IASoG-0008TC-CF
	for tsvwg@ietf.org; Mon, 16 Jul 2007 11:48:28 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IASoB-0000Jh-Kf
	for tsvwg@ietf.org; Mon, 16 Jul 2007 11:48:28 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 16 Jul 2007 17:48:23 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAJYvm0aQ/uCLh2dsb2JhbACPPQEBCQon
X-IronPort-AV: i="4.16,542,1175464800"; 
	d="scan'208"; a="148172919:sNHT63689628"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6GFmMlb000872; 
	Mon, 16 Jul 2007 17:48:22 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6GFmJkv022500; 
	Mon, 16 Jul 2007 15:48:19 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 16 Jul 2007 17:48:19 +0200
Received: from [144.254.53.89] ([144.254.53.89]) by xfe-ams-331.emea.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 16 Jul 2007 17:48:19 +0200
In-Reply-To: <6D1FB7A5-37E0-4708-A0F7-61B05251BFE4@g11.org.uk>
References: <E1I400A-0005PX-DQ@stiedprstage1.ietf.org>
	<CB3E86CE-5A05-43B4-81AC-443B727F14D4@cisco.com>
	<6D1FB7A5-37E0-4708-A0F7-61B05251BFE4@g11.org.uk>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <0879C74D-31CA-4F54-BC6D-1B8BC0F44B50@cisco.com>
Content-Transfer-Encoding: 7bit
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
Subject: Re: [Tsvwg] I-D ACTION:draft-ietf-tsvwg-rsvp-proxy-proto-01.txt 
Date: Mon, 16 Jul 2007 17:45:21 +0200
To: ken carlberg <carlberg@g11.org.uk>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 16 Jul 2007 15:48:19.0335 (UTC)
	FILETIME=[BB4C8170:01C7C7C0]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=6653; t=1184600902;
	x=1185464902; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.com>
	|Subject:=20Re=3A=20[Tsvwg]=20I-D=20ACTION=3Adraft-ietf-tsvwg-rsvp-proxy-
	proto-01.txt=20 |Sender:=20;
	bh=V0Wd+AuKk4ahZ664vXS3gKj3vFIJ64JW8u7izx6MjkY=;
	b=bUF/nnHeIODezpEF6/o2cVKnbJBHRiSUpMIKWOEC/g6nT9Gfj4qJrXaS7cZLr1W1SpxTEm4V
	sbtUw2rF16N5yYoOoz4DA0I7gNBXUHIU1KWH+IHbHFHzp4ZZy1Djx7+f;
Authentication-Results: ams-dkim-2; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 225414c974e0d6437992164e91287a51
Cc: Allan GUILLOU <allan.guillou@neufcegetel.fr>, tsvwg tsvwg <tsvwg@ietf.org>,
	hemant.malik@airtel.in, Ashok Narayanan <ashokn@cisco.com>,
	Jukka Manner MJ <jmanner@cs.Helsinki.FI>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hello Ken,

Thanks for your thorough review of the rsvp-proxy-proto. Please see  
below:


On 9 Jul 2007, at 16:26, ken carlberg wrote:

> Francois,
>
> the draft is quite nice.

great.

> Most of the comments below are suggestions for added clarity.  A  
> number of these are nits, so feel free to discard or modify those  
> as you see fit.
>
> 1) It may be helpful to move the Terminology section up so that it  
> is directly under the first paragraph of section 1.  In section 2,  
> you start off with terminology specific to this draft (eg, "RSVP  
> receiver Proxy"), and then later describe what it is in the  
> Terminology section below.

The Introduction section defines the terms that it uses already  
("Sender Proxy" and "Receiver Proxy"). The idea of the terminology  
section was to have a handy place to go back for the reader to check  
all the terms. So a standalone section seems reasonable to me.
We should probably state that this terminology is borrowed from proxy- 
approaches.


> You should also add a description of what is a "regular receiver"  
> in the Terminology section, and to state that it refers to an RSVP  
> capable end-host in the classic end-to-end model.

Agreed.

>
> It may also be helpful to state as early as possible, either in the  
> Introduction or in the Terminology section, that for this document  
> the Sender always refers to the RSVP capable node that originates  
> Path messages.  And that the receiver always refers to the RSVP  
> capable node that originates RESV messages and is a proxy.  My  
> confusion on this matter came up in the first sentence of page 5,  
> when you state "...some notifications about reservation state (...)  
> are only sent to the receiver".  I presume you mean the RSVP proxy  
> receiver, as opposed to the destination end host that may also be  
> an RSVP capable receiver.

The idea is that:
	* the sender = the sender of data flow
	* the receiver = the receiver of data flow.
If you see places where sender/receiver is not used with this  
meaning, let us know and we want to address this.

In the case of interest for this draft, the assumed model was that  
the sender was RSVP-capable (so it can do the synchronisation betwen  
RSVP and application). So the draft was written with this model in  
mind. However, it is applicable to scenarios where the sender is not  
RSVP capable and instead there is a RSVP Sender Proxy (that is  
synchrnised with application). So I think we should go through the  
doc and make sure the text covers both cases.

For example, we may want to replace:
" Since the synchronisation between RSVP reservation and application  
requirement is now effectively performed by the sender, it is  
important that the sender is aware of the reservation state.
"
by
"
Since the synchronisation between RSVP reservation and application  
requirement is now effectively performed by the sender (or through an  
RSVP Sender Proxy), it is important that the sender (or RSVP Sender  
Proxy) is aware of the reservation state.
"

To avoid the confusion you mention above, we could also replace "are  
only sent to the receiver" by "are only sent towards the receiver".

How does that sound?

>
> 2) just a nit, but I would feel more comfortable using the term  
> "intermediary" instead of "slave" in the third paragraph of page 4.

fine.

>
> 3) nit.  Section 3, first paragraph, change "of the sender" to "to  
> the sender"

or perhaps "notification of the sender (or RSVP Sender Proxy) about  
reservation failure".

>
> 4) Page 9, 1'st paragraph.  Could you add a sentence or two stating  
> what are the benefits of ensuring that the sender gets a prompt  
> failure notification?

yes. This includes ability to provide faster corresponding enduser  
notification at application layer (eg busy signal, application-level- 
rerouting) as well as faster release of application-level resources.

>
> I may also be reading the following two paragraphs of that page  
> incorrectly, but if an implementation MUST support the method of  
> 3.1, why would I add support for 3.2?  Is it rather a case of MUST  
> support 3.1  *or*  3.2, with the latter being more efficient but  
> requiring support of rfc-3473?  Or am I using poor terminology and  
> should the text say something like, "must support the method of  
> 3.1, and optionally 3.2, but may deploy/use either method"?

What is intended is a "router" must implement 3.1 and may also  
optionally implement 3.2. This is because we propose to have at least  
a common denominator on all routers claiming support of this document  
(ie 3.1). This is needed to guarantee interoperability.
Within a given deployment environment, the operator can choose what  
he/she wants (ie use 3.1 or 3.2 or both if they so desire).

So how about we :
	* replace "an implementation MUST" by "a router implementation MUST"
	* adding a sentence to the effect that the network operator is free  
to deploy 3.1 or 3.2 or both in a given environment.


>
> 5) Finally, this may be a nit, but it might be helpful to add a  
> Considerations section at the end of the document that mentions the  
> possible scenario of proxy reservations being established and yet  
> the end-host destination being unreachable/non-existent?  Proxy  
> RSVP routers will know if the downstream leaf router is reachable,  
> but they won't necessarily know if the last hop to the end host is  
> reachable.  And since the proxy segment may be part of an  
> asymmetric path, one can't rely on upstream data to give a hint to  
> the proxy receiver that the destination is up.
>
> I don't think this is major liability, but just something that  
> needs to be mentioned to those that choose to deploy this work.

I would say this consideration is not specific to the particular type  
of RSVP Proxy discussed in this document, but actually applicable to  
most RSVP Proxy scenario/approaches. So I would suggest we bring this  
point in the rsvp-proxy-approaches document.

As you say, generally in practice I don't expect this is to be a  
major concern since application level-signaling would take place with  
the sender/receiver before RSVP reservations are established, so that  
if either is unreachable, application signaling will be affected  
first. But it is conceivable that receiver is reachable from  
application server and not reachable from sender. So we may as well  
bring up that point (in proxy-approaches).

Thanks

FRancois

>
> -ken
>
>





From tsvwg-bounces@ietf.org Mon Jul 16 14:37:07 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IAVRP-0001Yw-8k; Mon, 16 Jul 2007 14:37:03 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IAVRN-0001XP-KR
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 16 Jul 2007 14:37:01 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IAVRN-0001Vj-8Z
	for tsvwg@ietf.org; Mon, 16 Jul 2007 14:37:01 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IAVRM-0008By-Ug
	for tsvwg@ietf.org; Mon, 16 Jul 2007 14:37:01 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-3.cisco.com with ESMTP; 16 Jul 2007 11:18:11 -0700
X-IronPort-AV: i="unknown";  a="503682180:sNHT0"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6GIIBAk003599
	for <tsvwg@ietf.org>; Mon, 16 Jul 2007 11:18:11 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l6GII66E016685
	for <tsvwg@ietf.org>; Mon, 16 Jul 2007 18:18:10 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 16 Jul 2007 11:18:08 -0700
Received: from jmpolk-wxp.cisco.com ([10.89.16.77]) by
	xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 16 Jul 2007 11:18:08 -0700
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 16 Jul 2007 13:18:06 -0500
To: tsvwg <tsvwg@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-ID: <XFE-SJC-2111o8yfogk000000fa@xfe-sjc-211.amer.cisco.com>
X-OriginalArrivalTime: 16 Jul 2007 18:18:08.0273 (UTC)
	FILETIME=[A91F9810:01C7C7D5]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1141; t=1184609891;
	x=1185473891; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jmpolk@cisco.com;
	z=From:=20=22James=20M.=20Polk=22=20<jmpolk@cisco.com>
	|Subject:=20FINAL=20Agenda=20for=20Chicago |Sender:=20;
	bh=mL0QrjnpWFGW2Sm0cAzHNpHsN1rUWfZM2QL/VkoYubQ=;
	b=aPabvUx7rHcahl8uy1pksclPgW1x+kASDT6oiLol3YAFjD1AontpJTpsA926CkDwRVJe3wpr
	zf80Xkwh0n+ISDX0Tw0BoA+P1i9niG/WB3LuaNdBXlDwbRkwsjdpzLNh;
Authentication-Results: sj-dkim-2; header.From=jmpolk@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Subject: [Tsvwg] FINAL Agenda for Chicago
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

TSVWG

Here is the final agenda for the Chicago meeting

         http://www3.ietf.org/proceedings/07jul/agenda/tsvwg.txt

Notice we've changed rooms!  We're now in the Grand Ballroom (moving 
up in the world, I guess  ;-)

I will continue looking for agenda bashing, if you have any items to bring up

We need volunteers for meeting notes, and jabber scribe -- who's up for either?

SPEAKERS!!!  Presentations will be due on Wednesday July 25th at noon 
local time, in order to make it on the server.  Changes after that 
time may not be received.  Speakers without presentations... well, 
they don't speak.

We (chairs) will likely be requesting WGLC opinions on several 
documents within this meeting.  The top 4 IDs on the agenda are a 
starting point.

We also have a number of -00 IDs this meeting, and their presenter's 
always ask if their doc can become a WG item.  Having read these docs 
gives YOU the opportunity to give an informed opinion about any of 
these fine efforts.

Several of these docs are not long, so read them please!


cheers,

James
Lars
Magnus
         IETF TSVWG co-chairs 





From tsvwg-bounces@ietf.org Tue Jul 17 08:38:15 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IAmJc-0003OJ-7u; Tue, 17 Jul 2007 08:38:08 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IAmJa-0003Nx-67
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 17 Jul 2007 08:38:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IAmJZ-0003No-SP; Tue, 17 Jul 2007 08:38:05 -0400
Received: from smtp1.smtp.bt.com ([217.32.164.137])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IAmJY-0005dP-6P; Tue, 17 Jul 2007 08:38:05 -0400
Received: from E03MVZ4-UKDY.domain1.systemhost.net ([193.113.30.64]) by
	smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 17 Jul 2007 13:38:03 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7C86F.50BE3E6A"
Date: Tue, 17 Jul 2007 13:38:13 +0100
Message-ID: <BAB4DC0CD5148948A86BD047A85CE2A70350388B@E03MVZ4-UKDY.domain1.systemhost.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Re-ECN meeting in Chicago
Thread-Index: AcfIb1dcZj34MKodRHiY9C/kzgz8ww==
From: <toby.moncaster@bt.com>
To: <re-ecn@ietf.org>
X-OriginalArrivalTime: 17 Jul 2007 12:38:03.0374 (UTC)
	FILETIME=[5144D8E0:01C7C86F]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 33cc095b503da4365ce57c727e553cf1
Cc: tsv-area@ietf.org, tsvwg@ietf.org
Subject: [Tsvwg] Re-ECN meeting in Chicago
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: re-ecn@ietf.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7C86F.50BE3E6A
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


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.=20

5 mins		Administrivia
25 mins		presentation and discussion on encoding in IP v4 and v6
(rationale behind current choices,=20
		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)=20
		   - mechanics of the protocol in TCP/IP=20
	 	   - implementation of the dropper and the policer=20
		   - extension for use by TCP proxies or other
congestion control proxies  =20
		   - extension for use by other transports=20
		   - 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 re-ecn@ietf.org.

Toby Moncaster=20
________________________________________________________________________
____
Toby Moncaster, <toby.moncaster@bt.com> Networks Research Centre, BT
Research
B54/70 Adastral Park, Martlesham Heath, Ipswich, IP53RE, UK.  +44 1473
648734=20


------_=_NextPart_001_01C7C86F.50BE3E6A
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>Re-ECN meeting in Chicago</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">All,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">There will be another re-ECN unofficial =
&quot;Bar BoF&quot; 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 &lt;</FONT><A =
HREF=3D"http://www.cs.ucl.ac.uk/staff/B.Briscoe/projects/refb/#Presentati=
ons"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">http://www.cs.ucl.ac.uk/staff/B.Briscoe/projects/refb/#Pre=
sentations</FONT></U></A><FONT SIZE=3D2 FACE=3D"Arial">&gt;)</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">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. </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">5 mins&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Administrivia</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">25 mins =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; presentation and discussion =
on encoding in IP v4 and v6 (rationale behind current choices, </FONT>

<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">alternatives, etc)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">10 mins =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; How to deploy experimentally =
(open mic)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">10 mins =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Deployment Scenarios</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">10 mins =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Next Steps:</FONT>

<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp; - format of the encoding (in v4, in v6) =
</FONT>

<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp; - mechanics of the protocol in TCP/IP =
</FONT>

<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<FONT SIZE=3D2 =
FACE=3D"Arial"> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; - =
implementation of the dropper and the policer </FONT>

<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp; - extension for use by TCP proxies or other =
congestion control proxies&nbsp;&nbsp; </FONT>

<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp; - extension for use by other transports =
</FONT>

<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp; - etc</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">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.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">All Internet drafts and other =
documentation relevant to re-ECN can be found at: &lt;</FONT><A =
HREF=3D"http://www.cs.ucl.ac.uk/staff/B.Briscoe/projects/refb/"><U><FONT =
COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">http://www.cs.ucl.ac.uk/staff/B.Briscoe/projects/refb/</FO=
NT></U></A><FONT SIZE=3D2 FACE=3D"Arial">&gt; including =
draft-briscoe-tsvwg-re-ecn-tcp which describes the protocol and the =
rationale behind it.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Please could you address any replies to =
this message to the unofficial IETF mailing list re-ecn@ietf.org.</FONT>
</P>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">Toby Moncaster</FONT></B><FONT =
FACE=3D"Times New Roman"> </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Courier =
New">____________________________________________________________________=
________</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Courier New">Toby Moncaster, =
&lt;toby.moncaster@bt.com&gt; Networks Research Centre, BT =
Research</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Courier New">B54/70 Adastral Park, Martlesham =
Heath, Ipswich, IP53RE, UK.&nbsp; +44 1473 648734</FONT>=20
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7C86F.50BE3E6A--





From tsvwg-bounces@ietf.org Tue Jul 17 14:42:15 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IArzc-0003d4-K9; Tue, 17 Jul 2007 14:41:52 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IArzZ-0003cl-R9
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 17 Jul 2007 14:41:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IArzZ-0003bt-GT
	for tsvwg@ietf.org; Tue, 17 Jul 2007 14:41:49 -0400
Received: from sccrmhc15.comcast.net ([63.240.77.85])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IArzZ-00033Y-83
	for tsvwg@ietf.org; Tue, 17 Jul 2007 14:41:49 -0400
Received: from [192.168.1.2]
	(c-69-250-218-72.hsd1.md.comcast.net[69.250.218.72])
	by comcast.net (sccrmhc15) with SMTP
	id <20070717184148015005eqjre>; Tue, 17 Jul 2007 18:41:48 +0000
In-Reply-To: <0879C74D-31CA-4F54-BC6D-1B8BC0F44B50@cisco.com>
References: <E1I400A-0005PX-DQ@stiedprstage1.ietf.org>
	<CB3E86CE-5A05-43B4-81AC-443B727F14D4@cisco.com>
	<6D1FB7A5-37E0-4708-A0F7-61B05251BFE4@g11.org.uk>
	<0879C74D-31CA-4F54-BC6D-1B8BC0F44B50@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <77A7AC0D-D52D-4B09-B250-8AC063454794@g11.org.uk>
Content-Transfer-Encoding: 7bit
From: ken carlberg <carlberg@g11.org.uk>
Subject: Re: [Tsvwg] I-D ACTION:draft-ietf-tsvwg-rsvp-proxy-proto-01.txt 
Date: Tue, 17 Jul 2007 14:41:45 -0400
To: Francois Le Faucheur IMAP <flefauch@cisco.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Cc: Ashok Narayanan <ashokn@cisco.com>, hemant.malik@airtel.in,
	Allan GUILLOU <allan.guillou@neufcegetel.fr>, tsvwg tsvwg <tsvwg@ietf.org>,
	Jukka Manner MJ <jmanner@cs.Helsinki.FI>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Francois,

>> It may also be helpful to state as early as possible, either in  
>> the Introduction or in the Terminology section, that for this  
>> document the Sender always refers to the RSVP capable node that  
>> originates Path messages.  And that the receiver always refers to  
>> the RSVP capable node that originates RESV messages and is a  
>> proxy.  My confusion on this matter came up in the first sentence  
>> of page 5, when you state "...some notifications about reservation  
>> state (...) are only sent to the receiver".  I presume you mean  
>> the RSVP proxy receiver, as opposed to the destination end host  
>> that may also be an RSVP capable receiver.
>
> The idea is that:
> 	* the sender = the sender of data flow
> 	* the receiver = the receiver of data flow.
> If you see places where sender/receiver is not used with this  
> meaning, let us know and we want to address this.
>
> In the case of interest for this draft, the assumed model was that  
> the sender was RSVP-capable (so it can do the synchronisation  
> betwen RSVP and application). So the draft was written with this  
> model in mind. However, it is applicable to scenarios where the  
> sender is not RSVP capable and instead there is a RSVP Sender Proxy  
> (that is synchrnised with application). So I think we should go  
> through the doc and make sure the text covers both cases.

That would be helpful.  And just to close the point I made above, you  
could clear up any ambiguity by saying something like: "...some  
notifications about reservation state (...) are only sent towards the  
receiver and terminated by the on-path proxy receiver".  Its that  
last part that I felt needed clarity.

> For example, we may want to replace:
> " Since the synchronisation between RSVP reservation and  
> application requirement is now effectively performed by the sender,  
> it is important that the sender is aware of the reservation state.
> "
> by
> "
> Since the synchronisation between RSVP reservation and application  
> requirement is now effectively performed by the sender (or through  
> an RSVP Sender Proxy), it is important that the sender (or RSVP  
> Sender Proxy) is aware of the reservation state.
> "
>
> To avoid the confusion you mention above, we could also replace  
> "are only sent to the receiver" by "are only sent towards the  
> receiver".
>
> How does that sound?

fine

>>
>> 2) just a nit, but I would feel more comfortable using the term  
>> "intermediary" instead of "slave" in the third paragraph of page 4.
>
> fine.
>
>>
>> 3) nit.  Section 3, first paragraph, change "of the sender" to "to  
>> the sender"
>
> or perhaps "notification of the sender (or RSVP Sender Proxy) about  
> reservation failure".

fine.

>> I may also be reading the following two paragraphs of that page  
>> incorrectly, but if an implementation MUST support the method of  
>> 3.1, why would I add support for 3.2?  Is it rather a case of MUST  
>> support 3.1  *or*  3.2, with the latter being more efficient but  
>> requiring support of rfc-3473?  Or am I using poor terminology and  
>> should the text say something like, "must support the method of  
>> 3.1, and optionally 3.2, but may deploy/use either method"?
>
> What is intended is a "router" must implement 3.1 and may also  
> optionally implement 3.2. This is because we propose to have at  
> least a common denominator on all routers claiming support of this  
> document (ie 3.1). This is needed to guarantee interoperability.
> Within a given deployment environment, the operator can choose what  
> he/she wants (ie use 3.1 or 3.2 or both if they so desire).
>
> So how about we :
> 	* replace "an implementation MUST" by "a router implementation MUST"
> 	* adding a sentence to the effect that the network operator is  
> free to deploy 3.1 or 3.2 or both in a given environment.

fine.  I probably should have been more clear in my original comment  
and advocated the use and distinction of implementation and deployment.

cheers,

-ken








From tsvwg-bounces@ietf.org Wed Jul 18 08:11:53 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IB8Ni-0003H7-KU; Wed, 18 Jul 2007 08:11:50 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IApVu-00055J-M6
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 17 Jul 2007 12:03:02 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IApVu-00055A-BI
	for tsvwg@ietf.org; Tue, 17 Jul 2007 12:03:02 -0400
Received: from web36701.mail.mud.yahoo.com ([209.191.85.35])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IApVs-0005bj-MI
	for tsvwg@ietf.org; Tue, 17 Jul 2007 12:03:02 -0400
Received: (qmail 46619 invoked by uid 60001); 17 Jul 2007 16:03:00 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
	b=eXAgeiUBq7rUQYZ5vyI3mGRvCgMa9YcZngxzA83J3pHUIETZQLLEhWYWN5HB+ct8Va+TxXDwaDa618a/F0Tifzo6NxbPWnZFNT7BqXZ+BlrfTsDTEXPxmq3HMcv/wzgjlQxAOmicl7bG/GeTeRvFRXPYQVQbFcDp30M7zTid3e4=;
X-YMail-OSG: J_v9QBsVM1kqQxThVECFQWZVPmj1LM7BMHoWtPHSlF0jQayw5k7nWFQyFdgU7ePJ3_LoXx0xs_Yce0HMz_rBxr_8V7DMuYqnCvibFjyEi2slKuP8KzYvLwC_2c_FfQ--
Received: from [138.239.78.107] by web36701.mail.mud.yahoo.com via HTTP;
	Tue, 17 Jul 2007 09:03:00 PDT
Date: Tue, 17 Jul 2007 09:03:00 -0700 (PDT)
From: Zack Best <zbest28@yahoo.com>
Subject: Re: [Tsvwg] Does anyone have a defence in favour of flow ratefairness?
To: tsvwg@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Message-ID: <107232.44814.qm@web36701.mail.mud.yahoo.com>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
X-Mailman-Approved-At: Wed, 18 Jul 2007 08:11:49 -0400
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

>From draft-floyd-tsvwg-besteffort-00b.txt

> One of the obvious dangers of simple
> implementations of QoS mechanisms or
> of cost-based fairness, in the absence of the
> protection of simple best-effort traffic,
> would be that the users with more money
> *could* end up completely shutting out users with
> less money in times of congestion.  There
> seems to be fairly widespread agreement that
> this would not be a desirable goal.

I am curious why this is not a desirable goal let
alone why there is widespread agreement of this.

If people are paying a monthly fee to their ISP
and if uninterrupted connectivity at relatively
low bandwidth is important to them (which in most
cases it is) wouldn't market forces work to make
this happen?  I.e. ISPs would spend their money
to insure to insure customers got what they wanted,
lest they lose business.

On the other hand, may people (perhaps most of the 
world) are excluded from the internet because
they can't afford the basic monthly fee to connect.
A cost based system would theoretically lower the
cost of entry for those who did not want to compete
for bandwidth at contested times, and actually make
limited connectivity available to a group previous
excluded.

There is certainly a recurring argument in the
political arena between the free market advocates,
and those who claim the free market would result
in unfairness that is best addressed by enforced
equality at the expense of choice and flexibility.

I won't attempt to resolve that argument here, but
my sympathies are certainly the the free market 
folks.  Experience has shown over and over that
market forces do a better job at scarce resource
allocation than detractors predict and a better
job than the proposed alternatives.

This is not meant as a comment on the practicality
of implementing cost based fairness, just as a
defense of the goal.



       
____________________________________________________________________________________
Pinpoint customers who are looking for what you sell. 
http://searchmarketing.yahoo.com/





From tsvwg-bounces@ietf.org Wed Jul 18 11:10:30 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBBAW-0007Zt-D3; Wed, 18 Jul 2007 11:10:24 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IBBAP-0007Z5-SO
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 18 Jul 2007 11:10:17 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBBAP-0007Yr-Ew
	for tsvwg@ietf.org; Wed, 18 Jul 2007 11:10:17 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IBBAO-0004pC-4N
	for tsvwg@ietf.org; Wed, 18 Jul 2007 11:10:17 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 18 Jul 2007 17:10:15 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAJ7KnUaQ/uCLh2dsb2JhbACCYoxhAQEJCic
X-IronPort-AV: i="4.16,550,1175464800"; 
	d="scan'208,217"; a="148389642:sNHT241817532"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6IFAECN024753
	for <tsvwg@ietf.org>; Wed, 18 Jul 2007 17:10:14 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6IF9jlV000892
	for <tsvwg@ietf.org>; Wed, 18 Jul 2007 15:10:14 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 18 Jul 2007 17:10:12 +0200
Received: from [10.0.0.15] ([10.61.65.174]) by xfe-ams-331.emea.cisco.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 18 Jul 2007 17:10:11 +0200
Mime-Version: 1.0 (Apple Message framework v752.3)
References: <E1I8giM-0003D3-47@stiedprstage1.ietf.org>
Content-Type: multipart/alternative; boundary=Apple-Mail-58-305604087
Message-Id: <DE890DAA-9B90-4659-8CC0-AD779C6E0217@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
Subject: Fwd: [Tsvwg] I-D ACTION:draft-ietf-tsvwg-rsvp-proxy-approaches-01.txt
Date: Wed, 18 Jul 2007 17:07:14 +0200
To: tsvwg tsvwg <tsvwg@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 18 Jul 2007 15:10:11.0750 (UTC)
	FILETIME=[BC9E3C60:01C7C94D]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=23275; t=1184771414;
	x=1185635414; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.com>
	|Subject:=20Fwd=3A=20[Tsvwg]=20I-D=20ACTION=3Adraft-ietf-tsvwg-rsvp-proxy
	-approaches-01.txt=20 |Sender:=20;
	bh=Mou6g0wKeej6HDTlrBnvxv2wNFpGNpgRb0A9eO54p5k=;
	b=f2OPFGDxBQrjmx+LiCIYkuqmV6vzPydVtuVaOrm6F7nUE6NLbTCnkkudF1TWyaYmyP45G7pt
	MyP12Undqs/aOsHjaRwVPtVc/AY113ZZS8szLH+C/WPVl5S2iCEg4acF;
Authentication-Results: ams-dkim-2; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: 0.2 (/)
X-Scan-Signature: b5216aa5b0df24d46eaed76d4f65aa31
Cc: 
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org


--Apple-Mail-58-305604087
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

Hello,

This updated version of rsvp-proxy-approaches addresses the comments  
received to date including:
	* outcome of the discussion with Lou Berger on Application_Entity- 
Controlled Proxy (this resulted in restructuring of several  
sections , + additional text on candidate protocols for Proxy Control)
	* discussion with Ken Carlberg re soft-state/hard-sate across Proxy  
Control interface
	* input from Chris Christou for IPsec scenario (this resulted in new  
section A.5)

It also includes the following additional changes:
	* various clean-up of pictures and text
	* new section on Policy_Server-Controlled Proxy (based on text  
provided by Tullio Loffredo and Massimo Sassi)
	* renaming of "Other Proxy Approaches" section into "Endsystem- 
Controlled Proxy" (since it only discusses that one appproach)
	* rewritten Security Considerations section

Francois

Begin forwarded message:

> From: Internet-Drafts@ietf.org
> Date: 11 July 2007 20:15:02 GMT+02:00
> To: i-d-announce@ietf.org
> Cc: tsvwg@ietf.org
> Subject: [Tsvwg] I-D ACTION:draft-ietf-tsvwg-rsvp-proxy- 
> approaches-01.txt
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Transport Area Working Group  
> Working Group of the IETF.
>
> 	Title		: RSVP Proxy Approaches
> 	Author(s)	: F. Le Faucheur, et al.
> 	Filename	: draft-ietf-tsvwg-rsvp-proxy-approaches-01.txt
> 	Pages		: 43
> 	Date		: 2007-7-11
> 	
> RSVP signaling can be used to make end-to-end resource reservations
>    in an IP network in order to guarantee the Quality of Service
>    required by certain flows.  With conventional RSVP, both the data
>    sender and receiver of a given flow take part in RSVP signaling.
>    Yet, there are many use cases where resource reservation is  
> required,
>    but the receiver, the sender, or both, is not RSVP-capable.  This
>    document presents RSVP Proxy behaviors allowing RSVP routers to
>    perform RSVP signaling on behalf of a receiver or a sender that is
>    not RSVP-capable.  This allows resource reservations to be
>    established on critical parts of the end-to-end path.  This  
> document
>    reviews conceptual approaches for deploying RSVP Proxies and
>    discusses how RSVP reservations can be synchronized with  
> application
>    requirements, despite the sender, receiver, or both not  
> participating
>    in RSVP.  This document also points out where extensions to RSVP  
> (or
>    to other protocols) may be needed for deployment of a given RSVP
>    Proxy approach.  However, such extensions are outside the scope of
>    this document.  Finally, practical use cases for RSVP Proxy are
>    described.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rsvp-proxy- 
> approaches-01.txt
>
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body of
> the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>
> Internet-Drafts are also available by anonymous FTP. Login with the
> username "anonymous" and a password of your e-mail address. After
> logging in, type "cd internet-drafts" and then
> "get draft-ietf-tsvwg-rsvp-proxy-approaches-01.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-tsvwg-rsvp-proxy- 
> approaches-01.txt".
> 	
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> Content-Type: text/plain
> Content-ID: <2007-7-11133252.I-D@ietf.org>
>


--Apple-Mail-58-305604087
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; ">Hello,<DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>This updated version of =
rsvp-proxy-approaches addresses the comments received to date =
including:</DIV><DIV><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>* outcome of the discussion with =
Lou Berger on Application_Entity-Controlled Proxy (this resulted in =
restructuring of several sections , + additional text on candidate =
protocols for Proxy Control)</DIV><DIV><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>* discussion with Ken Carlberg re =
soft-state/hard-sate across Proxy Control interface</DIV><DIV><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>* input =
from Chris Christou for IPsec scenario (this resulted in new section =
A.5)=A0</DIV><DIV><BR><DIV>It also includes the following additional =
changes:</DIV><DIV><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>* various clean-up of pictures =
and text</DIV><DIV><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>* new section on =
Policy_Server-Controlled Proxy (based on text provided =
by=A0Tullio=A0Loffredo and Massimo Sassi)</DIV><DIV><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>* =
renaming of "Other Proxy Approaches" section into "Endsystem-Controlled =
Proxy" (since it only discusses that one appproach)</DIV><DIV><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>* =
rewritten Security Considerations section</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Francois</DIV><DIV><BR><DIV>B=
egin forwarded message:</DIV><BR =
class=3D"Apple-interchange-newline"><BLOCKQUOTE type=3D"cite"><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 18.0px Helvetica; color: #000000"><B>From: =
</B></FONT><FONT face=3D"Helvetica" size=3D"5" style=3D"font: 18.0px =
Helvetica"><A =
href=3D"mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</A></FON=
T></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" =
color=3D"#000000" style=3D"font: 18.0px Helvetica; color: =
#000000"><B>Date: </B></FONT><FONT face=3D"Helvetica" size=3D"5" =
style=3D"font: 18.0px Helvetica">11 July 2007 20:15:02 =
GMT+02:00</FONT></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><FONT face=3D"Helvetica" =
size=3D"5" color=3D"#000000" style=3D"font: 18.0px Helvetica; color: =
#000000"><B>To: </B></FONT><FONT face=3D"Helvetica" size=3D"5" =
style=3D"font: 18.0px Helvetica"><A =
href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</A></FONT></DI=
V><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 18.0px Helvetica; color: #000000"><B>Cc: </B></FONT><FONT =
face=3D"Helvetica" size=3D"5" style=3D"font: 18.0px Helvetica"><A =
href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</A></FONT></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 18.0px Helvetica; color: #000000"><B>Subject: =
</B></FONT><FONT face=3D"Helvetica" size=3D"5" style=3D"font: 18.0px =
Helvetica"><B>[Tsvwg] I-D =
ACTION:draft-ietf-tsvwg-rsvp-proxy-approaches-01.txt<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></B></FONT></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV> <DIV style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">A New =
Internet-Draft is available from the on-line Internet-Drafts<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">directories.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">This draft is a work item of the =
Transport Area Working Group Working Group of the IETF.</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>Title<SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN><SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>: RSVP Proxy Approaches</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>Author(s)<SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>: F. Le Faucheur, et al.</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>Filename<SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>: draft-ietf-tsvwg-rsvp-proxy-approaches-01.txt</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>Pages<SPAN class=3D"Apple-tab-span"=
 style=3D"white-space:pre">	</SPAN><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>: 43</DIV><DIV style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>Date<SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>: =
2007-7-11</DIV><P style=3D"margin: 0.0px 0.0px 0.0px 0.0px; min-height: =
14.0px"><SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN><BR class=3D"khtml-block-placeholder"></P><DIV style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">RSVP =
signaling can be used to make end-to-end resource reservations</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0=A0 =
</SPAN>in an IP network in order to guarantee the Quality of =
Service</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>required by certain =
flows.<SPAN class=3D"Apple-converted-space">=A0 </SPAN>With conventional =
RSVP, both the data</DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>sender and receiver of a =
given flow take part in RSVP signaling.</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>Yet, there are many use =
cases where resource reservation is required,</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0=A0 =
</SPAN>but the receiver, the sender, or both, is not RSVP-capable.<SPAN =
class=3D"Apple-converted-space">=A0 </SPAN>This</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0=A0 =
</SPAN>document presents RSVP Proxy behaviors allowing RSVP routers =
to</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0=A0 =
</SPAN>perform RSVP signaling on behalf of a receiver or a sender that =
is</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0=A0 =
</SPAN>not RSVP-capable.<SPAN class=3D"Apple-converted-space">=A0 =
</SPAN>This allows resource reservations to be</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0=A0 =
</SPAN>established on critical parts of the end-to-end path.<SPAN =
class=3D"Apple-converted-space">=A0 </SPAN>This document</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0=A0 =
</SPAN>reviews conceptual approaches for deploying RSVP Proxies =
and</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>discusses how RSVP =
reservations can be synchronized with application</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0=A0 =
</SPAN>requirements, despite the sender, receiver, or both not =
participating</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>in RSVP.<SPAN =
class=3D"Apple-converted-space">=A0 </SPAN>This document also points out =
where extensions to RSVP (or</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>to other protocols) may be =
needed for deployment of a given RSVP</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>Proxy approach.<SPAN =
class=3D"Apple-converted-space">=A0 </SPAN>However, such extensions are =
outside the scope of</DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>this document.<SPAN =
class=3D"Apple-converted-space">=A0 </SPAN>Finally, practical use cases =
for RSVP Proxy are</DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>described.</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">A URL =
for this Internet-Draft is:</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A =
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rsvp-proxy-ap=
proaches-01.txt">http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rsvp=
-proxy-approaches-01.txt</A></DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">To remove yourself from the I-D =
Announcement list, send a message to<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A =
href=3D"mailto:i-d-announce-request@ietf.org">i-d-announce-request@ietf.or=
g</A> with the word unsubscribe in the body of<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">the =
message.<SPAN class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">You can also visit <A =
href=3D"https://www1.ietf.org/mailman/listinfo/I-D-announce">https://www1.=
ietf.org/mailman/listinfo/I-D-announce</A><SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">to =
change your subscription settings.</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Internet-Drafts are also =
available by anonymous FTP. Login with the<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">username =
"anonymous" and a password of your e-mail address. After<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">logging =
in, type "cd internet-drafts" and then<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">"get =
draft-ietf-tsvwg-rsvp-proxy-approaches-01.txt".</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">A list =
of Internet-Drafts directories can be found in</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</=
A><SPAN class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">or <A =
href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/ietf=
/1shadow-sites.txt</A></DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Internet-Drafts can also be =
obtained by e-mail.</DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Send a message to:</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN><A =
href=3D"mailto:mailserv@ietf.org">mailserv@ietf.org</A>.</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">In the body type:</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>"FILE =
/internet-drafts/draft-ietf-tsvwg-rsvp-proxy-approaches-01.txt".</DIV><P =
style=3D"margin: 0.0px 0.0px 0.0px 0.0px; min-height: 14.0px"><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN><BR =
class=3D"khtml-block-placeholder"></P><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">NOTE:<SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>The mail =
server at ietf.org can return the document in</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>MIME-encoded form by using the =
"mpack" utility.<SPAN class=3D"Apple-converted-space">=A0 </SPAN>To use =
this</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>feature, insert the command =
"ENCODING mime" before the "FILE"</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>command.<SPAN class=3D"Apple-converted-space">=A0 </SPAN>To =
decode the response(s), you will need "munpack" or</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>a MIME-compliant mail =
reader.<SPAN class=3D"Apple-converted-space">=A0 </SPAN>Different =
MIME-compliant mail readers</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>exhibit =
different behavior, especially when dealing with</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>"multipart" MIME messages (i.e. =
documents which have been split</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>up into =
multiple messages), so check your local documentation on</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>how to manipulate these =
messages.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Below is the data which will enable a MIME compliant =
mail reader</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">implementation to automatically =
retrieve the ASCII version of the</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">Internet-Draft.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Content-Type: =
text/plain</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Content-ID: &lt;<A =
href=3D"mailto:2007-7-11133252.I-D@ietf.org">2007-7-11133252.I-D@ietf.org<=
/A>&gt;</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV> =
</BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>=

--Apple-Mail-58-305604087--





From tsvwg-bounces@ietf.org Wed Jul 18 16:06:07 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBFmb-0003qm-UM; Wed, 18 Jul 2007 16:06:01 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IBFma-0003n8-B1
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 18 Jul 2007 16:06:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBFmZ-0003ki-T0
	for tsvwg@ietf.org; Wed, 18 Jul 2007 16:05:59 -0400
Received: from atlrel9.hp.com ([156.153.255.214])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBFmX-00040f-EW
	for tsvwg@ietf.org; Wed, 18 Jul 2007 16:05:59 -0400
Received: from smtp1.fc.hp.com (smtp.cnd.hp.com [15.15.136.127])
	by atlrel9.hp.com (Postfix) with ESMTP id BF30F370DF;
	Wed, 18 Jul 2007 15:49:09 -0400 (EDT)
Received: from [16.116.113.226] (galen.zko.hp.com [16.116.113.226])
	by smtp1.fc.hp.com (Postfix) with ESMTP id 77FAB149B7F;
	Wed, 18 Jul 2007 19:48:57 +0000 (UTC)
Message-ID: <469E6EA8.70500@hp.com>
Date: Wed, 18 Jul 2007 15:48:56 -0400
From: Vlad Yasevich <vladislav.yasevich@hp.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070604)
MIME-Version: 1.0
To: tsvwg <tsvwg@ietf.org>
References: <4695027E.3040109@hp.com>
In-Reply-To: <4695027E.3040109@hp.com>
X-Enigmail-Version: 0.95.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -4.0 (----)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
	Randall Stewart <rrs@cisco.com>
Subject: [Tsvwg] Re: sctp-auth questions
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi All

One more item from Draft 8:

Section 3.1

   The RANDOM parameter MUST be included once in the INIT or INIT-ACK
   chunk if the sender wants to send or receive authenticated chunks to
   provide a 32 byte Random Number.

The sentence reads almost like a run-on and I can't quite figure out
what "to provide a 32 byte Random Number" is trying to explain.
The first time I read it, I though it was part of the requirement, but
I don't think it was meant to be.

I this this sentence needs to clarified.

Thanks
-vlad





From tsvwg-bounces@ietf.org Wed Jul 18 16:06:45 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBFnG-0004pD-OZ; Wed, 18 Jul 2007 16:06:42 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IBFnD-0004oc-Eh
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 18 Jul 2007 16:06:39 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBFnC-0004md-09
	for tsvwg@ietf.org; Wed, 18 Jul 2007 16:06:38 -0400
Received: from atlrel9.hp.com ([156.153.255.214])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IBFnB-0005HJ-NJ
	for tsvwg@ietf.org; Wed, 18 Jul 2007 16:06:37 -0400
Received: from smtp1.fc.hp.com (smtp1.fc.hp.com [15.15.136.127])
	by atlrel9.hp.com (Postfix) with ESMTP id 07D7437677;
	Wed, 18 Jul 2007 15:59:46 -0400 (EDT)
Received: from [16.116.113.226] (galen.zko.hp.com [16.116.113.226])
	by smtp1.fc.hp.com (Postfix) with ESMTP id 6A7B6148FA9;
	Wed, 18 Jul 2007 19:55:54 +0000 (UTC)
Message-ID: <469E704A.6070206@hp.com>
Date: Wed, 18 Jul 2007 15:55:54 -0400
From: Vlad Yasevich <vladislav.yasevich@hp.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070604)
MIME-Version: 1.0
To: tsvwg <tsvwg@ietf.org>
References: <4695027E.3040109@hp.com> <469E6EA8.70500@hp.com>
In-Reply-To: <469E6EA8.70500@hp.com>
X-Enigmail-Version: 0.95.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
	Randall Stewart <rrs@cisco.com>
Subject: [Tsvwg] Re: sctp-auth questions
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Vlad Yasevich wrote:
> Hi All
> 
> One more item from Draft 8:
> 
> Section 3.1
> 
>    The RANDOM parameter MUST be included once in the INIT or INIT-ACK
>    chunk if the sender wants to send or receive authenticated chunks to
>    provide a 32 byte Random Number.
> 
> The sentence reads almost like a run-on and I can't quite figure out
> what "to provide a 32 byte Random Number" is trying to explain.
> The first time I read it, I though it was part of the requirement, but
> I don't think it was meant to be.

Ok, so it is meant to be a requirement (based on section 6.1), but it
is worded badly.

Still needs to be reworded.

> 
> I this this sentence needs to clarified.
> 
> Thanks
> -vlad
> 






From tsvwg-bounces@ietf.org Wed Jul 18 16:19:16 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBFzO-0001HZ-0v; Wed, 18 Jul 2007 16:19:14 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IBFz3-0000D7-FT
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 18 Jul 2007 16:18:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBFz1-000088-I0
	for tsvwg@ietf.org; Wed, 18 Jul 2007 16:18:52 -0400
Received: from gw.openss7.com ([142.179.199.224])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBFz0-0004Wv-3R
	for tsvwg@ietf.org; Wed, 18 Jul 2007 16:18:51 -0400
Received: from ns.pigworks.openss7.net
	(IDENT:4+8G0PJ0FYfRXZ9QRVUcCl6vVVkj7g8M@ns1.evil.openss7.net
	[192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id l6IKIUM29295;
	Wed, 18 Jul 2007 14:18:30 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id l6IKIUn08946;
	Wed, 18 Jul 2007 14:18:30 -0600
Date: Wed, 18 Jul 2007 14:18:30 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Vlad Yasevich <vladislav.yasevich@hp.com>
Subject: Re: [Tsvwg] Re: sctp-auth questions
Message-ID: <20070718141830.A7782@openss7.org>
Mail-Followup-To: Vlad Yasevich <vladislav.yasevich@hp.com>,
	tsvwg <tsvwg@ietf.org>,
	Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
	Randall Stewart <rrs@cisco.com>
References: <4695027E.3040109@hp.com> <469E6EA8.70500@hp.com>
	<469E704A.6070206@hp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <469E704A.6070206@hp.com>;
	from vladislav.yasevich@hp.com on Wed, Jul 18, 2007 at 03:55:54PM
	-0400
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
	Randall Stewart <rrs@cisco.com>, tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bidulock@openss7.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Vlad,

It should obviously be interpreted so:

Section 3.1

   The RANDOM parameter MUST be included once in the INIT or INIT-ACK
   chunk (if the sender wants to send or receive authenticated chunks) to
   provide a 32 byte Random Number.

That is,

   "to provide a 32 byte Random Number"

is the purpose of including the RANDOM parameter.  And,

   "if the sender wants to send or receive authenticated chunks"

modifies the MUST in that the RANDOM parameter does not need to be included
in all INIT or INIT-ACK messages, only when the sender wants to send or
receive authenticated chunks.

--brian


Vlad Yasevich wrote:                             (Wed, 18 Jul 2007 15:55:54)
> Vlad Yasevich wrote:
> > Hi All
> > 
> > One more item from Draft 8:
> > 
> > Section 3.1
> > 
> >    The RANDOM parameter MUST be included once in the INIT or INIT-ACK
> >    chunk if the sender wants to send or receive authenticated chunks to
> >    provide a 32 byte Random Number.
> > 
> > The sentence reads almost like a run-on and I can't quite figure out
> > what "to provide a 32 byte Random Number" is trying to explain.
> > The first time I read it, I though it was part of the requirement, but
> > I don't think it was meant to be.
> 
> Ok, so it is meant to be a requirement (based on section 6.1), but it
> is worded badly.
> 
> Still needs to be reworded.
> 
> > 
> > I this this sentence needs to clarified.
> > 
> > Thanks
> > -vlad
> > 
> 
> 

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/





From tsvwg-bounces@ietf.org Wed Jul 18 16:37:54 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBGHQ-000243-Id; Wed, 18 Jul 2007 16:37:52 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IBGHK-00023Y-Vt
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 18 Jul 2007 16:37:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBGHK-00023P-MI
	for tsvwg@ietf.org; Wed, 18 Jul 2007 16:37:46 -0400
Received: from atlrel7.hp.com ([156.153.255.213])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBGHJ-0005SP-Cx
	for tsvwg@ietf.org; Wed, 18 Jul 2007 16:37:46 -0400
Received: from smtp2.fc.hp.com (smtp2.fc.hp.com [15.11.136.114])
	by atlrel7.hp.com (Postfix) with ESMTP id 8226934867;
	Wed, 18 Jul 2007 16:37:24 -0400 (EDT)
Received: from [16.116.113.226] (galen.zko.hp.com [16.116.113.226])
	by smtp2.fc.hp.com (Postfix) with ESMTP id 49006192BE5;
	Wed, 18 Jul 2007 20:37:18 +0000 (UTC)
Message-ID: <469E79FD.1030903@hp.com>
Date: Wed, 18 Jul 2007 16:37:17 -0400
From: Vlad Yasevich <vladislav.yasevich@hp.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070604)
MIME-Version: 1.0
To: Vlad Yasevich <vladislav.yasevich@hp.com>, tsvwg <tsvwg@ietf.org>,
	Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
	Randall Stewart <rrs@cisco.com>
Subject: Re: [Tsvwg] Re: sctp-auth questions
References: <4695027E.3040109@hp.com> <469E6EA8.70500@hp.com>
	<469E704A.6070206@hp.com> <20070718141830.A7782@openss7.org>
In-Reply-To: <20070718141830.A7782@openss7.org>
X-Enigmail-Version: 0.95.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: 
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Brian F. G. Bidulock wrote:
> Vlad,
> 
> It should obviously be interpreted so:
> 
> Section 3.1
> 
>    The RANDOM parameter MUST be included once in the INIT or INIT-ACK
>    chunk (if the sender wants to send or receive authenticated chunks) to
>    provide a 32 byte Random Number.

Sorry, but I don't see the parenthesis in the on-line copy.

Either parenthesis or commas would clear it up.

-vlad

> 
> That is,
> 
>    "to provide a 32 byte Random Number"
> 
> is the purpose of including the RANDOM parameter.  And,
> 
>    "if the sender wants to send or receive authenticated chunks"
> 
> modifies the MUST in that the RANDOM parameter does not need to be included
> in all INIT or INIT-ACK messages, only when the sender wants to send or
> receive authenticated chunks.
> 
> --brian
> 
> 
> Vlad Yasevich wrote:                             (Wed, 18 Jul 2007 15:55:54)
>> Vlad Yasevich wrote:
>>> Hi All
>>>
>>> One more item from Draft 8:
>>>
>>> Section 3.1
>>>
>>>    The RANDOM parameter MUST be included once in the INIT or INIT-ACK
>>>    chunk if the sender wants to send or receive authenticated chunks to
>>>    provide a 32 byte Random Number.
>>>
>>> The sentence reads almost like a run-on and I can't quite figure out
>>> what "to provide a 32 byte Random Number" is trying to explain.
>>> The first time I read it, I though it was part of the requirement, but
>>> I don't think it was meant to be.
>> Ok, so it is meant to be a requirement (based on section 6.1), but it
>> is worded badly.
>>
>> Still needs to be reworded.
>>
>>> I this this sentence needs to clarified.
>>>
>>> Thanks
>>> -vlad
>>>
>>
> 






From tsvwg-bounces@ietf.org Wed Jul 18 16:38:24 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBGHw-0002Sj-LR; Wed, 18 Jul 2007 16:38:24 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IBGHa-0002Pj-RO
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 18 Jul 2007 16:38:02 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBGHa-0002P8-Gh
	for tsvwg@ietf.org; Wed, 18 Jul 2007 16:38:02 -0400
Received: from mail1.adax.com ([208.201.231.104])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IBGHZ-0006xD-Vd
	for tsvwg@ietf.org; Wed, 18 Jul 2007 16:38:02 -0400
Received: from adax (adax [12.0.0.88]) by mail1.adax.com (Postfix) with ESMTP
	id 6A0233DDB; Wed, 18 Jul 2007 13:49:19 -0700 (PDT)
Received: by adax (Postfix, from userid 243)
	id 7C2C838052; Wed, 18 Jul 2007 13:37:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by adax (Postfix) with ESMTP id 71EFFC072;
	Wed, 18 Jul 2007 13:37:25 -0700 (PDT)
Date: Wed, 18 Jul 2007 13:37:25 -0700 (PDT)
From: Christopher Benson <cbenson@adax.com>
X-X-Sender: cbenson@adax
To: Vlad Yasevich <vladislav.yasevich@hp.com>
Subject: Re: [Tsvwg] Re: sctp-auth questions
In-Reply-To: <469E704A.6070206@hp.com>
Message-ID: <Pine.LNX.4.44.0707181319020.11042-100000@adax>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
	Randall Stewart <rrs@cisco.com>, tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Vlad and authors,

How about rephrasing as:
    If the sender of an INIT or INIT-ACK wants to send or 
    receive authenticated chunks, then the RANDOM parameter 
    MUST be included [once] to provide a 32 byte Random 
    Number [as the RANDOM parameter's value].

I think that is the intention and it is clearer to me.
The [once] may be dropped in my opinion, and I added a 
perhaps superfluous phrase connecting the value and the 
parameter.

 With thanks, from Chris Benson.

On Wed, 18 Jul 2007, Vlad Yasevich wrote:

>>  Date: Wed, 18 Jul 2007 15:55:54 -0400
>>  From: Vlad Yasevich <vladislav.yasevich@hp.com>
>>  To: tsvwg <tsvwg@ietf.org>
>>  Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
>>       Randall Stewart <rrs@cisco.com>
>>  Subject: [Tsvwg] Re: sctp-auth questions
>>  
>>  Vlad Yasevich wrote:
>>  > Hi All
>>  > 
>>  > One more item from Draft 8:
>>  > 
>>  > Section 3.1
>>  > 
>>  >    The RANDOM parameter MUST be included once in the INIT or INIT-ACK
>>  >    chunk if the sender wants to send or receive authenticated chunks to
>>  >    provide a 32 byte Random Number.
>>  > 
>>  > The sentence reads almost like a run-on and I can't quite figure out
>>  > what "to provide a 32 byte Random Number" is trying to explain.
>>  > The first time I read it, I though it was part of the requirement, but
>>  > I don't think it was meant to be.
>>  
>>  Ok, so it is meant to be a requirement (based on section 6.1), but it
>>  is worded badly.
>>  
>>  Still needs to be reworded.
>>  
>>  > 
>>  > I this this sentence needs to clarified.
>>  > 
>>  > Thanks
>>  > -vlad
>>  > 
>>  
>>  
>>  






From tsvwg-bounces@ietf.org Wed Jul 18 16:50:20 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBGTS-0005uD-Jx; Wed, 18 Jul 2007 16:50:18 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IBGTR-0005tr-9J
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 18 Jul 2007 16:50:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBGTO-0005tZ-Td
	for tsvwg@ietf.org; Wed, 18 Jul 2007 16:50:15 -0400
Received: from atlrel9.hp.com ([156.153.255.214])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBGTN-0005ky-Im
	for tsvwg@ietf.org; Wed, 18 Jul 2007 16:50:14 -0400
Received: from smtp1.fc.hp.com (smtp.fc.hp.com [15.15.136.127])
	by atlrel9.hp.com (Postfix) with ESMTP id B2E55345A6;
	Wed, 18 Jul 2007 16:49:47 -0400 (EDT)
Received: from [16.116.113.226] (galen.zko.hp.com [16.116.113.226])
	by smtp1.fc.hp.com (Postfix) with ESMTP id BF9A9149B72;
	Wed, 18 Jul 2007 20:49:46 +0000 (UTC)
Message-ID: <469E7CEA.2050106@hp.com>
Date: Wed, 18 Jul 2007 16:49:46 -0400
From: Vlad Yasevich <vladislav.yasevich@hp.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070604)
MIME-Version: 1.0
To: Christopher Benson <cbenson@adax.com>
Subject: Re: [Tsvwg] Re: sctp-auth questions
References: <Pine.LNX.4.44.0707181319020.11042-100000@adax>
In-Reply-To: <Pine.LNX.4.44.0707181319020.11042-100000@adax>
X-Enigmail-Version: 0.95.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
	Randall Stewart <rrs@cisco.com>, tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi Chris

Christopher Benson wrote:
> Vlad and authors,
> 
> How about rephrasing as:
>     If the sender of an INIT or INIT-ACK wants to send or 
>     receive authenticated chunks, then the RANDOM parameter 
>     MUST be included [once] to provide a 32 byte Random 
>     Number [as the RANDOM parameter's value].
> 

I would go even as far as to completely kill this reference to
32 bytes.  Section 6.1 already has a hard requirement on
the RANDOM number being 32 bytes long and having it in multple
places just confuses things.

Just my $.02.

-vlad

> I think that is the intention and it is clearer to me.
> The [once] may be dropped in my opinion, and I added a 
> perhaps superfluous phrase connecting the value and the 
> parameter.
> 
>  With thanks, from Chris Benson.
> 
> On Wed, 18 Jul 2007, Vlad Yasevich wrote:
> 
>>>  Date: Wed, 18 Jul 2007 15:55:54 -0400
>>>  From: Vlad Yasevich <vladislav.yasevich@hp.com>
>>>  To: tsvwg <tsvwg@ietf.org>
>>>  Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
>>>       Randall Stewart <rrs@cisco.com>
>>>  Subject: [Tsvwg] Re: sctp-auth questions
>>>  
>>>  Vlad Yasevich wrote:
>>>  > Hi All
>>>  > 
>>>  > One more item from Draft 8:
>>>  > 
>>>  > Section 3.1
>>>  > 
>>>  >    The RANDOM parameter MUST be included once in the INIT or INIT-ACK
>>>  >    chunk if the sender wants to send or receive authenticated chunks to
>>>  >    provide a 32 byte Random Number.
>>>  > 
>>>  > The sentence reads almost like a run-on and I can't quite figure out
>>>  > what "to provide a 32 byte Random Number" is trying to explain.
>>>  > The first time I read it, I though it was part of the requirement, but
>>>  > I don't think it was meant to be.
>>>  
>>>  Ok, so it is meant to be a requirement (based on section 6.1), but it
>>>  is worded badly.
>>>  
>>>  Still needs to be reworded.
>>>  
>>>  > 
>>>  > I this this sentence needs to clarified.
>>>  > 
>>>  > Thanks
>>>  > -vlad
>>>  > 
>>>  
>>>  
>>>  
> 






From tsvwg-bounces@ietf.org Wed Jul 18 17:28:52 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBH4W-000125-6k; Wed, 18 Jul 2007 17:28:36 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IBH4E-0000xo-T0
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 18 Jul 2007 17:28:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBH4E-0000x5-3I
	for tsvwg@ietf.org; Wed, 18 Jul 2007 17:28:18 -0400
Received: from drew.ipv6.franken.de ([2001:638:a02:a001:20e:cff:fe4a:feaa]
	helo=mail-n.franken.de) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IBH4C-0006dF-Ok
	for tsvwg@ietf.org; Wed, 18 Jul 2007 17:28:18 -0400
Received: from [192.168.1.198] (p508FE5A2.dip.t-dialin.net [80.143.229.162])
	by mail-n.franken.de (Postfix) with ESMTP id 799E1801AC13;
	Wed, 18 Jul 2007 23:28:14 +0200 (CEST)
	(KNF-authenticated sender: macmic)
In-Reply-To: <469E7CEA.2050106@hp.com>
References: <Pine.LNX.4.44.0707181319020.11042-100000@adax>
	<469E7CEA.2050106@hp.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <C2580597-E7F6-4F20-884F-42E216C86A09@lurchi.franken.de>
Content-Transfer-Encoding: 7bit
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Tsvwg] Re: sctp-auth questions
Date: Wed, 18 Jul 2007 23:28:16 +0200
To: Vlad Yasevich <vladislav.yasevich@hp.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 1.4 (+)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: Randall Stewart <rrs@cisco.com>, tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Dear all,

the ID is currently in AUTH48, which means that it is
unfortunately too late to include these changes.

Best regards
Michael


On Jul 18, 2007, at 10:49 PM, Vlad Yasevich wrote:

> Hi Chris
>
> Christopher Benson wrote:
>> Vlad and authors,
>>
>> How about rephrasing as:
>>     If the sender of an INIT or INIT-ACK wants to send or
>>     receive authenticated chunks, then the RANDOM parameter
>>     MUST be included [once] to provide a 32 byte Random
>>     Number [as the RANDOM parameter's value].
>>
>
> I would go even as far as to completely kill this reference to
> 32 bytes.  Section 6.1 already has a hard requirement on
> the RANDOM number being 32 bytes long and having it in multple
> places just confuses things.
>
> Just my $.02.
>
> -vlad
>
>> I think that is the intention and it is clearer to me.
>> The [once] may be dropped in my opinion, and I added a
>> perhaps superfluous phrase connecting the value and the
>> parameter.
>>
>>  With thanks, from Chris Benson.
>>
>> On Wed, 18 Jul 2007, Vlad Yasevich wrote:
>>
>>>>  Date: Wed, 18 Jul 2007 15:55:54 -0400
>>>>  From: Vlad Yasevich <vladislav.yasevich@hp.com>
>>>>  To: tsvwg <tsvwg@ietf.org>
>>>>  Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
>>>>       Randall Stewart <rrs@cisco.com>
>>>>  Subject: [Tsvwg] Re: sctp-auth questions
>>>>
>>>>  Vlad Yasevich wrote:
>>>>> Hi All
>>>>>
>>>>> One more item from Draft 8:
>>>>>
>>>>> Section 3.1
>>>>>
>>>>>    The RANDOM parameter MUST be included once in the INIT or  
>>>>> INIT-ACK
>>>>>    chunk if the sender wants to send or receive authenticated  
>>>>> chunks to
>>>>>    provide a 32 byte Random Number.
>>>>>
>>>>> The sentence reads almost like a run-on and I can't quite  
>>>>> figure out
>>>>> what "to provide a 32 byte Random Number" is trying to explain.
>>>>> The first time I read it, I though it was part of the  
>>>>> requirement, but
>>>>> I don't think it was meant to be.
>>>>
>>>>  Ok, so it is meant to be a requirement (based on section 6.1),  
>>>> but it
>>>>  is worded badly.
>>>>
>>>>  Still needs to be reworded.
>>>>
>>>>>
>>>>> I this this sentence needs to clarified.
>>>>>
>>>>> Thanks
>>>>> -vlad
>>>>>
>>>>
>>>>
>>>>
>>
>
>






From tsvwg-bounces@ietf.org Wed Jul 18 19:56:15 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBJNM-0006q9-Bz; Wed, 18 Jul 2007 19:56:12 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IBJNL-0006q3-It
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 18 Jul 2007 19:56:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBJNK-0006pu-QF
	for tsvwg@ietf.org; Wed, 18 Jul 2007 19:56:10 -0400
Received: from vapor.isi.edu ([128.9.64.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBJNK-0002GI-96
	for tsvwg@ietf.org; Wed, 18 Jul 2007 19:56:10 -0400
Received: from [192.168.1.42] (pool-71-105-86-112.lsanca.dsl-w.verizon.net
	[71.105.86.112])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id l6INtlpp008072;
	Wed, 18 Jul 2007 16:55:47 -0700 (PDT)
Message-ID: <469EA87D.9020500@isi.edu>
Date: Wed, 18 Jul 2007 16:55:41 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Tsvwg] Re: sctp-auth questions
References: <Pine.LNX.4.44.0707181319020.11042-100000@adax>	<469E7CEA.2050106@hp.com>
	<C2580597-E7F6-4F20-884F-42E216C86A09@lurchi.franken.de>
In-Reply-To: <C2580597-E7F6-4F20-884F-42E216C86A09@lurchi.franken.de>
X-Enigmail-Version: 0.95.2
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig1D8C68CE5C61734E3CE6BC2D"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>, Randall Stewart <rrs@cisco.com>,
	tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig1D8C68CE5C61734E3CE6BC2D
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable



Michael Tuexen wrote:
> Dear all,
>=20
> the ID is currently in AUTH48, which means that it is
> unfortunately too late to include these changes.
>=20
> Best regards
> Michael
>=20
>=20
> On Jul 18, 2007, at 10:49 PM, Vlad Yasevich wrote:
>=20
>> Hi Chris
>>
>> Christopher Benson wrote:
>>> Vlad and authors,
>>>
>>> How about rephrasing as:
>>>     If the sender of an INIT or INIT-ACK wants to send or
>>>     receive authenticated chunks, then the RANDOM parameter
>>>     MUST be included [once] to provide a 32 byte Random
>>>     Number [as the RANDOM parameter's value].
>>>
>>
>> I would go even as far as to completely kill this reference to
>> 32 bytes.  Section 6.1 already has a hard requirement on
>> the RANDOM number being 32 bytes long and having it in multple
>> places just confuses things.
>>
>> Just my $.02.
>>
>> -vlad
>>
>>> I think that is the intention and it is clearer to me.
>>> The [once] may be dropped in my opinion, and I added a
>>> perhaps superfluous phrase connecting the value and the
>>> parameter.
>>>
>>>  With thanks, from Chris Benson.
>>>
>>> On Wed, 18 Jul 2007, Vlad Yasevich wrote:
>>>
>>>>>  Date: Wed, 18 Jul 2007 15:55:54 -0400
>>>>>  From: Vlad Yasevich <vladislav.yasevich@hp.com>
>>>>>  To: tsvwg <tsvwg@ietf.org>
>>>>>  Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
>>>>>       Randall Stewart <rrs@cisco.com>
>>>>>  Subject: [Tsvwg] Re: sctp-auth questions
>>>>>
>>>>>  Vlad Yasevich wrote:
>>>>>> Hi All
>>>>>>
>>>>>> One more item from Draft 8:
>>>>>>
>>>>>> Section 3.1
>>>>>>
>>>>>>    The RANDOM parameter MUST be included once in the INIT or INIT-=
ACK
>>>>>>    chunk if the sender wants to send or receive authenticated
>>>>>> chunks to
>>>>>>    provide a 32 byte Random Number.
>>>>>>
>>>>>> The sentence reads almost like a run-on and I can't quite figure o=
ut
>>>>>> what "to provide a 32 byte Random Number" is trying to explain.
>>>>>> The first time I read it, I though it was part of the requirement,=

>>>>>> but
>>>>>> I don't think it was meant to be.
>>>>>
>>>>>  Ok, so it is meant to be a requirement (based on section 6.1), but=
 it
>>>>>  is worded badly.
>>>>>
>>>>>  Still needs to be reworded.
>>>>>
>>>>>>
>>>>>> I this this sentence needs to clarified.
>>>>>>
>>>>>> Thanks
>>>>>> -vlad
>>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>
>>
>=20
>=20

--=20
----------------------------------------------------------------------
Joe Touch                Sr. Network Engineer, USAF TSAT Space Segment
               Postel Center Director & Research Assoc. Prof., USC/ISI


--------------enig1D8C68CE5C61734E3CE6BC2D
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGnqh9E5f5cImnZrsRAntjAJ4/YbNjWn+iDqQy+6u1AgqkDNmCKwCgkbWc
SDMEZi8XBGaEfI5C1kx5uk0=
=IFKO
-----END PGP SIGNATURE-----

--------------enig1D8C68CE5C61734E3CE6BC2D--





From tsvwg-bounces@ietf.org Wed Jul 18 19:57:22 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBJOR-0008W1-4Z; Wed, 18 Jul 2007 19:57:19 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IBJOP-0008Vv-2I
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 18 Jul 2007 19:57:17 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBJOO-0008Vn-Ni
	for tsvwg@ietf.org; Wed, 18 Jul 2007 19:57:16 -0400
Received: from vapor.isi.edu ([128.9.64.64])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IBJOO-00044X-5e
	for tsvwg@ietf.org; Wed, 18 Jul 2007 19:57:16 -0400
Received: from [192.168.1.42] (pool-71-105-86-112.lsanca.dsl-w.verizon.net
	[71.105.86.112])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id l6INv1in008220;
	Wed, 18 Jul 2007 16:57:01 -0700 (PDT)
Message-ID: <469EA8C7.6020706@isi.edu>
Date: Wed, 18 Jul 2007 16:56:55 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Tsvwg] Re: sctp-auth questions
References: <Pine.LNX.4.44.0707181319020.11042-100000@adax>	<469E7CEA.2050106@hp.com>
	<C2580597-E7F6-4F20-884F-42E216C86A09@lurchi.franken.de>
In-Reply-To: <C2580597-E7F6-4F20-884F-42E216C86A09@lurchi.franken.de>
X-Enigmail-Version: 0.95.2
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig2E476E1386F584B6307D98B7"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>, Randall Stewart <rrs@cisco.com>,
	tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig2E476E1386F584B6307D98B7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Sorry - meant to say that you might ask the RFC-Editor whether such a
change would be OK.

Joe


Michael Tuexen wrote:
> Dear all,
>=20
> the ID is currently in AUTH48, which means that it is
> unfortunately too late to include these changes.
>=20
> Best regards
> Michael
>=20
>=20
> On Jul 18, 2007, at 10:49 PM, Vlad Yasevich wrote:
>=20
>> Hi Chris
>>
>> Christopher Benson wrote:
>>> Vlad and authors,
>>>
>>> How about rephrasing as:
>>>     If the sender of an INIT or INIT-ACK wants to send or
>>>     receive authenticated chunks, then the RANDOM parameter
>>>     MUST be included [once] to provide a 32 byte Random
>>>     Number [as the RANDOM parameter's value].
>>>
>>
>> I would go even as far as to completely kill this reference to
>> 32 bytes.  Section 6.1 already has a hard requirement on
>> the RANDOM number being 32 bytes long and having it in multple
>> places just confuses things.
>>
>> Just my $.02.
>>
>> -vlad
>>
>>> I think that is the intention and it is clearer to me.
>>> The [once] may be dropped in my opinion, and I added a
>>> perhaps superfluous phrase connecting the value and the
>>> parameter.
>>>
>>>  With thanks, from Chris Benson.
>>>
>>> On Wed, 18 Jul 2007, Vlad Yasevich wrote:
>>>
>>>>>  Date: Wed, 18 Jul 2007 15:55:54 -0400
>>>>>  From: Vlad Yasevich <vladislav.yasevich@hp.com>
>>>>>  To: tsvwg <tsvwg@ietf.org>
>>>>>  Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
>>>>>       Randall Stewart <rrs@cisco.com>
>>>>>  Subject: [Tsvwg] Re: sctp-auth questions
>>>>>
>>>>>  Vlad Yasevich wrote:
>>>>>> Hi All
>>>>>>
>>>>>> One more item from Draft 8:
>>>>>>
>>>>>> Section 3.1
>>>>>>
>>>>>>    The RANDOM parameter MUST be included once in the INIT or INIT-=
ACK
>>>>>>    chunk if the sender wants to send or receive authenticated
>>>>>> chunks to
>>>>>>    provide a 32 byte Random Number.
>>>>>>
>>>>>> The sentence reads almost like a run-on and I can't quite figure o=
ut
>>>>>> what "to provide a 32 byte Random Number" is trying to explain.
>>>>>> The first time I read it, I though it was part of the requirement,=

>>>>>> but
>>>>>> I don't think it was meant to be.
>>>>>
>>>>>  Ok, so it is meant to be a requirement (based on section 6.1), but=
 it
>>>>>  is worded badly.
>>>>>
>>>>>  Still needs to be reworded.
>>>>>
>>>>>>
>>>>>> I this this sentence needs to clarified.
>>>>>>
>>>>>> Thanks
>>>>>> -vlad
>>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>
>>
>=20
>=20

--=20
----------------------------------------------------------------------
Joe Touch                Sr. Network Engineer, USAF TSAT Space Segment
               Postel Center Director & Research Assoc. Prof., USC/ISI


--------------enig2E476E1386F584B6307D98B7
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGnqjHE5f5cImnZrsRAmxgAKDS+iOfookRcezIVLXsCQAY3fUv+wCgzeJx
bOpTdW9B45DPJ/3vVU3HSqM=
=+OZM
-----END PGP SIGNATURE-----

--------------enig2E476E1386F584B6307D98B7--





From tsvwg-bounces@ietf.org Wed Jul 18 20:46:38 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBKA6-00012o-Aq; Wed, 18 Jul 2007 20:46:34 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IBKA4-00011L-FY
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 18 Jul 2007 20:46:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBKA4-00011D-5y
	for tsvwg@ietf.org; Wed, 18 Jul 2007 20:46:32 -0400
Received: from drew.ipv6.franken.de ([2001:638:a02:a001:20e:cff:fe4a:feaa]
	helo=mail-n.franken.de) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IBKA2-0004SV-RA
	for tsvwg@ietf.org; Wed, 18 Jul 2007 20:46:32 -0400
Received: from [192.168.1.198] (p508FE5A2.dip.t-dialin.net [80.143.229.162])
	by mail-n.franken.de (Postfix) with ESMTP id C344A80000BC;
	Thu, 19 Jul 2007 02:46:28 +0200 (CEST)
	(KNF-authenticated sender: macmic)
In-Reply-To: <469EA8C7.6020706@isi.edu>
References: <Pine.LNX.4.44.0707181319020.11042-100000@adax>	<469E7CEA.2050106@hp.com>
	<C2580597-E7F6-4F20-884F-42E216C86A09@lurchi.franken.de>
	<469EA8C7.6020706@isi.edu>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <64436CEF-8A78-4751-BB75-945BFF4A5AC7@lurchi.franken.de>
Content-Transfer-Encoding: 7bit
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Tsvwg] Re: sctp-auth questions
Date: Thu, 19 Jul 2007 02:46:30 +0200
To: Lars Eggert <lars.eggert@nokia.com>,
	Magnus Westerlund <magnus.westerlund@ericsson.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 1.4 (+)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>, Randall Stewart <rrs@cisco.com>,
	tsvwg <tsvwg@ietf.org>, Joe Touch <touch@ISI.EDU>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

ADs?

On Jul 19, 2007, at 1:56 AM, Joe Touch wrote:

> Sorry - meant to say that you might ask the RFC-Editor whether such a
> change would be OK.
>
> Joe
>
>
> Michael Tuexen wrote:
>> Dear all,
>>
>> the ID is currently in AUTH48, which means that it is
>> unfortunately too late to include these changes.
>>
>> Best regards
>> Michael
>>
>>
>> On Jul 18, 2007, at 10:49 PM, Vlad Yasevich wrote:
>>
>>> Hi Chris
>>>
>>> Christopher Benson wrote:
>>>> Vlad and authors,
>>>>
>>>> How about rephrasing as:
>>>>     If the sender of an INIT or INIT-ACK wants to send or
>>>>     receive authenticated chunks, then the RANDOM parameter
>>>>     MUST be included [once] to provide a 32 byte Random
>>>>     Number [as the RANDOM parameter's value].
>>>>
>>>
>>> I would go even as far as to completely kill this reference to
>>> 32 bytes.  Section 6.1 already has a hard requirement on
>>> the RANDOM number being 32 bytes long and having it in multple
>>> places just confuses things.
>>>
>>> Just my $.02.
>>>
>>> -vlad
>>>
>>>> I think that is the intention and it is clearer to me.
>>>> The [once] may be dropped in my opinion, and I added a
>>>> perhaps superfluous phrase connecting the value and the
>>>> parameter.
>>>>
>>>>  With thanks, from Chris Benson.
>>>>
>>>> On Wed, 18 Jul 2007, Vlad Yasevich wrote:
>>>>
>>>>>>  Date: Wed, 18 Jul 2007 15:55:54 -0400
>>>>>>  From: Vlad Yasevich <vladislav.yasevich@hp.com>
>>>>>>  To: tsvwg <tsvwg@ietf.org>
>>>>>>  Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
>>>>>>       Randall Stewart <rrs@cisco.com>
>>>>>>  Subject: [Tsvwg] Re: sctp-auth questions
>>>>>>
>>>>>>  Vlad Yasevich wrote:
>>>>>>> Hi All
>>>>>>>
>>>>>>> One more item from Draft 8:
>>>>>>>
>>>>>>> Section 3.1
>>>>>>>
>>>>>>>    The RANDOM parameter MUST be included once in the INIT or  
>>>>>>> INIT-ACK
>>>>>>>    chunk if the sender wants to send or receive authenticated
>>>>>>> chunks to
>>>>>>>    provide a 32 byte Random Number.
>>>>>>>
>>>>>>> The sentence reads almost like a run-on and I can't quite  
>>>>>>> figure out
>>>>>>> what "to provide a 32 byte Random Number" is trying to explain.
>>>>>>> The first time I read it, I though it was part of the  
>>>>>>> requirement,
>>>>>>> but
>>>>>>> I don't think it was meant to be.
>>>>>>
>>>>>>  Ok, so it is meant to be a requirement (based on section  
>>>>>> 6.1), but it
>>>>>>  is worded badly.
>>>>>>
>>>>>>  Still needs to be reworded.
>>>>>>
>>>>>>>
>>>>>>> I this this sentence needs to clarified.
>>>>>>>
>>>>>>> Thanks
>>>>>>> -vlad
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>
>>>
>>
>>
>
> -- 
> ----------------------------------------------------------------------
> Joe Touch                Sr. Network Engineer, USAF TSAT Space Segment
>                Postel Center Director & Research Assoc. Prof., USC/ISI
>






From tsvwg-bounces@ietf.org Thu Jul 19 00:16:47 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBNRP-00010N-AP; Thu, 19 Jul 2007 00:16:39 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IBNRN-00010H-Er
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 19 Jul 2007 00:16:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBNRN-000109-32
	for tsvwg@ietf.org; Thu, 19 Jul 2007 00:16:37 -0400
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBNRL-00019m-Kz
	for tsvwg@ietf.org; Thu, 19 Jul 2007 00:16:37 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l6J4GSep022110; Thu, 19 Jul 2007 07:16:31 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 19 Jul 2007 07:16:27 +0300
Received: from mgw-int01.ntc.nokia.com ([172.21.143.96]) by
	esebh104.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 19 Jul 2007 07:16:26 +0300
Received: from [10.130.5.118] (essapo-nirac252186.europe.nokia.com
	[10.162.252.186])
	by mgw-int01.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l6J4GO8e013430; Thu, 19 Jul 2007 07:16:24 +0300
In-Reply-To: <64436CEF-8A78-4751-BB75-945BFF4A5AC7@lurchi.franken.de>
References: <Pine.LNX.4.44.0707181319020.11042-100000@adax>	<469E7CEA.2050106@hp.com>
	<C2580597-E7F6-4F20-884F-42E216C86A09@lurchi.franken.de>
	<469EA8C7.6020706@isi.edu>
	<64436CEF-8A78-4751-BB75-945BFF4A5AC7@lurchi.franken.de>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-34-352948111;
	protocol="application/pkcs7-signature"
Message-Id: <CCB4087C-D140-4F59-9A74-EAF6196C105F@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
Subject: Re: [Tsvwg] Re: sctp-auth questions
Date: Thu, 19 Jul 2007 07:16:18 +0300
To: "ext Michael Tuexen" <Michael.Tuexen@lurchi.franken.de>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 19 Jul 2007 04:16:27.0562 (UTC)
	FILETIME=[9397E0A0:01C7C9BB]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>,
	Magnus Westerlund <magnus.westerlund@ericsson.com>,
	Randall Stewart <rrs@cisco.com>, tsvwg <tsvwg@ietf.org>,
	Joe Touch <touch@ISI.EDU>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org


--Apple-Mail-34-352948111
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

If the authors feel that this is a clarification, it is appropriate  
to make this change during AUTH48.

(I wish the document had received this level of review during the WGLC.)

On 2007-7-19, at 3:46, ext Michael Tuexen wrote:
> ADs?
>
> On Jul 19, 2007, at 1:56 AM, Joe Touch wrote:
>> Sorry - meant to say that you might ask the RFC-Editor whether such a
>> change would be OK.

Lars
--Apple-Mail-34-352948111
Content-Transfer-Encoding: base64
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGQDCCAvkw
ggJioAMCAQICEGtxkLFHQu1g67hlmYfwPuIwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ
ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA3MDEwNDE2MTE1NFoXDTA4MDEwNDE2MTE1
NFowXDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVnZ2Vy
dDEkMCIGCSqGSIb3DQEJARYVbGFycy5lZ2dlcnRAbm9raWEuY29tMIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEA26hjntVPZMiwh4d8tyuk9KiucvG92BVUGArk5zO1jhmq7tLFgU1mqcIg
VGumfQqjkAzIuh83kxIiqBrB05Wvxp85apwt4sUCvzMe8mQWzZZZYp0rBzwpOj+VC5pxsMRYtYW+
BaTFBEmvFr7D7C7roZUk0lDppS5SZFs4SQbEe9ykB9aeUf1iTiw2+ikyP2+JEYto14WYCoxFWbms
FbQ1uaaK+yn1WH2YHhyMfi0IOxuT0jtbsngjHJMpWIqq334zBhj+rPSUug47YBHr41FCDMHbbbjv
WbyTyDYneOW3WY8LY8bGWVlAknQGB7lgduShe6e0RI/7SL/VE6X27lM9LwIDAQABozIwMDAgBgNV
HREEGTAXgRVsYXJzLmVnZ2VydEBub2tpYS5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUF
AAOBgQCx3nxxTg/WowobVTRXBiXUEEZj4LBiunWbuAnR0UbJIgijvq3JbiJvZo2gUGiW9LPaHSBz
4oxT1VR/S/6O0a4e87oV5cOQm6ReB68o9rDfUzxHTwoCfv2wwMwBrXyzQMjyQK4Lt8siV41gmZpm
rSXMhjTJdd9uYYNoZKQLq+VM+TCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJ
BgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgG
A1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMg
RGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3
DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3
MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5
KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTCBnzAN
BgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9
fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+
uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMB
Af8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3
dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgG
A1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcP
f6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH
2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8x
ggMQMIIDDAIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAo
UHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ
a3GQsUdC7WDruGWZh/A+4jAJBgUrDgMCGgUAoIIBbzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcB
MBwGCSqGSIb3DQEJBTEPFw0wNzA3MTkwNDE2MThaMCMGCSqGSIb3DQEJBDEWBBR3k/pidXrfTt3S
jNEyFvHbgr2M4zCBhQYJKwYBBAGCNxAEMXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0ECEGtxkLFHQu1g67hlmYfwPuIwgYcGCyqGSIb3DQEJEAILMXigdjBiMQsw
CQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UE
AxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEGtxkLFHQu1g67hlmYfwPuIw
DQYJKoZIhvcNAQEBBQAEggEAFcvt06YvWGIa7bkXXncj7IJra/57+hpd6dfj49AWpktwDyBKW6X8
D+hm2EF9RVYi5zBeuXgNdygknwr2Tuq2EUZ4TAyEk1lFJNGT/R4TBlRBsJC7DHC+JMIQ6PJzH9Nj
feUXlOUHJwC3BSSrRpvkYDM6emEUGjpK0KPMvDds0JJrEXXgaRUbwL1o1X58cRZMffsP51TIjCe1
9yMi9gD3ydRdne2qRWVs+IudS/7BRcoin1b1hnp5eLNkg4J9hMnZSSHIN/JoJ3G9ihzmd1NmFz76
Ht13faEi4Dyukj/R43qLDt102GrqlqSaXPeYhGb7Bj/AHgnzWPp5fvQVhmrEuAAAAAAAAA==

--Apple-Mail-34-352948111--





From tsvwg-bounces@ietf.org Thu Jul 19 06:44:49 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBTUu-00013V-Oe; Thu, 19 Jul 2007 06:44:40 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IBTUs-000137-PO
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 19 Jul 2007 06:44:38 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBTUs-00012w-4T
	for tsvwg@ietf.org; Thu, 19 Jul 2007 06:44:38 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IBTUr-0003Ih-JA
	for tsvwg@ietf.org; Thu, 19 Jul 2007 06:44:38 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-5.cisco.com with ESMTP; 19 Jul 2007 03:44:37 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CANTdnkarR7MV/2dsb2JhbAA
X-IronPort-AV: i="4.16,555,1175497200"; 
	d="scan'208"; a="167296416:sNHT27927810"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l6JAiakW003681; 
	Thu, 19 Jul 2007 03:44:36 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l6JAia6C006637;
	Thu, 19 Jul 2007 10:44:36 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 19 Jul 2007 03:44:36 -0700
Received: from [127.0.0.1] ([171.68.225.134]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 19 Jul 2007 03:44:35 -0700
Message-ID: <469F40BF.10305@cisco.com>
Date: Thu, 19 Jul 2007 06:45:19 -0400
From: Randall Stewart <rrs@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.13) Gecko/20070601
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Joe Touch <touch@ISI.EDU>
Subject: Re: [Tsvwg] Re: sctp-auth questions
References: <Pine.LNX.4.44.0707181319020.11042-100000@adax>	<469E7CEA.2050106@hp.com>
	<C2580597-E7F6-4F20-884F-42E216C86A09@lurchi.franken.de>
	<469EA8C7.6020706@isi.edu>
In-Reply-To: <469EA8C7.6020706@isi.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Jul 2007 10:44:35.0839 (UTC)
	FILETIME=[CC7CF0F0:01C7C9F1]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2830; t=1184841876;
	x=1185705876; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=rrs@cisco.com;
	z=From:=20Randall=20Stewart=20<rrs@cisco.com>
	|Subject:=20Re=3A=20[Tsvwg]=20Re=3A=20sctp-auth=20questions
	|Sender:=20; bh=QdqbYbhAz0fF4ukga/OIqzE/ImGiEPh+KlabZ+isbWY=;
	b=lUYBzyj4GAQT525Qsu93MqtiBGSWHSHD5ED7WYMGndQe9oB9aMeM5CCoP87tF8VSuK+qTTgZ
	f+GY+NCEYEsi0TBb5AtBTAa6RdGp0MBKhodD9e4asXT5aWZpTannM2psi+24GTOqpnGNJCFwS3
	Im5JKxbCX58QMOMiiI/xpNWB0=;
Authentication-Results: sj-dkim-1; header.From=rrs@cisco.com; dkim=pass (sig
	from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>,
	Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Joe Touch wrote:
> Sorry - meant to say that you might ask the RFC-Editor whether such a
> change would be OK.

It is just a textual clearfication... " a edit " :-)

Michael, why don't you send a request to the RFC editor
about this.. most they can do is say no :-D

R
> 
> Joe
> 
> 
> Michael Tuexen wrote:
> 
>>Dear all,
>>
>>the ID is currently in AUTH48, which means that it is
>>unfortunately too late to include these changes.
>>
>>Best regards
>>Michael
>>
>>
>>On Jul 18, 2007, at 10:49 PM, Vlad Yasevich wrote:
>>
>>
>>>Hi Chris
>>>
>>>Christopher Benson wrote:
>>>
>>>>Vlad and authors,
>>>>
>>>>How about rephrasing as:
>>>>    If the sender of an INIT or INIT-ACK wants to send or
>>>>    receive authenticated chunks, then the RANDOM parameter
>>>>    MUST be included [once] to provide a 32 byte Random
>>>>    Number [as the RANDOM parameter's value].
>>>>
>>>
>>>I would go even as far as to completely kill this reference to
>>>32 bytes.  Section 6.1 already has a hard requirement on
>>>the RANDOM number being 32 bytes long and having it in multple
>>>places just confuses things.
>>>
>>>Just my $.02.
>>>
>>>-vlad
>>>
>>>
>>>>I think that is the intention and it is clearer to me.
>>>>The [once] may be dropped in my opinion, and I added a
>>>>perhaps superfluous phrase connecting the value and the
>>>>parameter.
>>>>
>>>> With thanks, from Chris Benson.
>>>>
>>>>On Wed, 18 Jul 2007, Vlad Yasevich wrote:
>>>>
>>>>
>>>>>> Date: Wed, 18 Jul 2007 15:55:54 -0400
>>>>>> From: Vlad Yasevich <vladislav.yasevich@hp.com>
>>>>>> To: tsvwg <tsvwg@ietf.org>
>>>>>> Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
>>>>>>      Randall Stewart <rrs@cisco.com>
>>>>>> Subject: [Tsvwg] Re: sctp-auth questions
>>>>>>
>>>>>> Vlad Yasevich wrote:
>>>>>>
>>>>>>>Hi All
>>>>>>>
>>>>>>>One more item from Draft 8:
>>>>>>>
>>>>>>>Section 3.1
>>>>>>>
>>>>>>>   The RANDOM parameter MUST be included once in the INIT or INIT-ACK
>>>>>>>   chunk if the sender wants to send or receive authenticated
>>>>>>>chunks to
>>>>>>>   provide a 32 byte Random Number.
>>>>>>>
>>>>>>>The sentence reads almost like a run-on and I can't quite figure out
>>>>>>>what "to provide a 32 byte Random Number" is trying to explain.
>>>>>>>The first time I read it, I though it was part of the requirement,
>>>>>>>but
>>>>>>>I don't think it was meant to be.
>>>>>>
>>>>>> Ok, so it is meant to be a requirement (based on section 6.1), but it
>>>>>> is worded badly.
>>>>>>
>>>>>> Still needs to be reworded.
>>>>>>
>>>>>>
>>>>>>>I this this sentence needs to clarified.
>>>>>>>
>>>>>>>Thanks
>>>>>>>-vlad
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>
>>
> 


-- 
Randall Stewart
NSSTG - Cisco Systems Inc.
803-345-0369 <or> 803-317-4952 (cell)





From tsvwg-bounces@ietf.org Thu Jul 19 06:47:12 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBTXL-0002HD-A0; Thu, 19 Jul 2007 06:47:11 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IBTXJ-0002Gy-8W
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 19 Jul 2007 06:47:09 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBTXI-0002Go-TQ
	for tsvwg@ietf.org; Thu, 19 Jul 2007 06:47:08 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IBTXI-0003NO-Hd
	for tsvwg@ietf.org; Thu, 19 Jul 2007 06:47:08 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-3.cisco.com with ESMTP; 19 Jul 2007 03:47:08 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CANTdnkarR7O6/2dsb2JhbAA
X-IronPort-AV: i="4.16,556,1175497200"; 
	d="scan'208"; a="504860429:sNHT26812148"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6JAl7NK013161; 
	Thu, 19 Jul 2007 03:47:07 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l6JAl7Sb012494;
	Thu, 19 Jul 2007 10:47:07 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 19 Jul 2007 03:47:06 -0700
Received: from [127.0.0.1] ([171.68.225.134]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 19 Jul 2007 03:47:06 -0700
Message-ID: <469F4155.7030904@cisco.com>
Date: Thu, 19 Jul 2007 06:47:49 -0400
From: Randall Stewart <rrs@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.13) Gecko/20070601
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Lars Eggert <lars.eggert@nokia.com>
Subject: Re: [Tsvwg] Re: sctp-auth questions
References: <Pine.LNX.4.44.0707181319020.11042-100000@adax>	<469E7CEA.2050106@hp.com>
	<C2580597-E7F6-4F20-884F-42E216C86A09@lurchi.franken.de>
	<469EA8C7.6020706@isi.edu>
	<64436CEF-8A78-4751-BB75-945BFF4A5AC7@lurchi.franken.de>
	<CCB4087C-D140-4F59-9A74-EAF6196C105F@nokia.com>
In-Reply-To: <CCB4087C-D140-4F59-9A74-EAF6196C105F@nokia.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Jul 2007 10:47:06.0574 (UTC)
	FILETIME=[265546E0:01C7C9F2]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=713; t=1184842027;
	x=1185706027; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=rrs@cisco.com;
	z=From:=20Randall=20Stewart=20<rrs@cisco.com>
	|Subject:=20Re=3A=20[Tsvwg]=20Re=3A=20sctp-auth=20questions
	|Sender:=20; bh=sWIJlkDrBmkXlQJAwPoQcRT8pTdmMHyv5K5KAOyAQb4=;
	b=mMkz7xjWPT5T0ttw3iqPh9TOnPa7qHuq0u2Jxh7ij3kBbygRnoj11t+05LWbGKDS11E2U2at
	SZuJWgRoAxI9T0Xa+d+NqfYkwPqh2wr/iu+s3cvkzE2FcUEdufgL8TTg;
Authentication-Results: sj-dkim-2; header.From=rrs@cisco.com; dkim=pass (sig
	from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>,
	ext Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
	Joe Touch <touch@ISI.EDU>, tsvwg <tsvwg@ietf.org>,
	Magnus Westerlund <magnus.westerlund@ericsson.com>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Lars Eggert wrote:
> If the authors feel that this is a clarification, it is appropriate  to 
> make this change during AUTH48.
> 
> (I wish the document had received this level of review during the WGLC.)


I think it is worth the change.. but I definetly agree with you.. it
would have been nice to get these comments BEFORE we were in
auth-48.. like WGLC :-0

R
> 
> On 2007-7-19, at 3:46, ext Michael Tuexen wrote:
> 
>> ADs?
>>
>> On Jul 19, 2007, at 1:56 AM, Joe Touch wrote:
>>
>>> Sorry - meant to say that you might ask the RFC-Editor whether such a
>>> change would be OK.
> 
> 
> Lars


-- 
Randall Stewart
NSSTG - Cisco Systems Inc.
803-345-0369 <or> 803-317-4952 (cell)





From tsvwg-bounces@ietf.org Thu Jul 19 07:51:21 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBUXF-0001nI-19; Thu, 19 Jul 2007 07:51:09 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IBUXD-0001mn-NI
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 19 Jul 2007 07:51:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBUXD-0001mf-Cv
	for tsvwg@ietf.org; Thu, 19 Jul 2007 07:51:07 -0400
Received: from drew.ipv6.franken.de ([2001:638:a02:a001:20e:cff:fe4a:feaa]
	helo=mail-n.franken.de) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IBUXC-0003Nm-O1
	for tsvwg@ietf.org; Thu, 19 Jul 2007 07:51:07 -0400
Received: from [192.168.1.198] (p508FEE50.dip.t-dialin.net [80.143.238.80])
	by mail-n.franken.de (Postfix) with ESMTP id 0BECD801AC09;
	Thu, 19 Jul 2007 13:51:04 +0200 (CEST)
	(KNF-authenticated sender: macmic)
In-Reply-To: <469F40BF.10305@cisco.com>
References: <Pine.LNX.4.44.0707181319020.11042-100000@adax>	<469E7CEA.2050106@hp.com>
	<C2580597-E7F6-4F20-884F-42E216C86A09@lurchi.franken.de>
	<469EA8C7.6020706@isi.edu> <469F40BF.10305@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <9F4C58FD-3F85-40A8-BBD9-8D761CDE2A83@lurchi.franken.de>
Content-Transfer-Encoding: 7bit
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Tsvwg] Re: sctp-auth questions
Date: Thu, 19 Jul 2007 13:51:06 +0200
To: Randall Stewart <rrs@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>, tsvwg <tsvwg@ietf.org>,
	Joe Touch <touch@ISI.EDU>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi Randy,

I'll send a note. I'll also look what Vlad had posted before.

Best regards
Michael

On Jul 19, 2007, at 12:45 PM, Randall Stewart wrote:

> Joe Touch wrote:
>> Sorry - meant to say that you might ask the RFC-Editor whether such a
>> change would be OK.
>
> It is just a textual clearfication... " a edit " :-)
>
> Michael, why don't you send a request to the RFC editor
> about this.. most they can do is say no :-D
>
> R
>> Joe
>> Michael Tuexen wrote:
>>> Dear all,
>>>
>>> the ID is currently in AUTH48, which means that it is
>>> unfortunately too late to include these changes.
>>>
>>> Best regards
>>> Michael
>>>
>>>
>>> On Jul 18, 2007, at 10:49 PM, Vlad Yasevich wrote:
>>>
>>>
>>>> Hi Chris
>>>>
>>>> Christopher Benson wrote:
>>>>
>>>>> Vlad and authors,
>>>>>
>>>>> How about rephrasing as:
>>>>>    If the sender of an INIT or INIT-ACK wants to send or
>>>>>    receive authenticated chunks, then the RANDOM parameter
>>>>>    MUST be included [once] to provide a 32 byte Random
>>>>>    Number [as the RANDOM parameter's value].
>>>>>
>>>>
>>>> I would go even as far as to completely kill this reference to
>>>> 32 bytes.  Section 6.1 already has a hard requirement on
>>>> the RANDOM number being 32 bytes long and having it in multple
>>>> places just confuses things.
>>>>
>>>> Just my $.02.
>>>>
>>>> -vlad
>>>>
>>>>
>>>>> I think that is the intention and it is clearer to me.
>>>>> The [once] may be dropped in my opinion, and I added a
>>>>> perhaps superfluous phrase connecting the value and the
>>>>> parameter.
>>>>>
>>>>> With thanks, from Chris Benson.
>>>>>
>>>>> On Wed, 18 Jul 2007, Vlad Yasevich wrote:
>>>>>
>>>>>
>>>>>>> Date: Wed, 18 Jul 2007 15:55:54 -0400
>>>>>>> From: Vlad Yasevich <vladislav.yasevich@hp.com>
>>>>>>> To: tsvwg <tsvwg@ietf.org>
>>>>>>> Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
>>>>>>>      Randall Stewart <rrs@cisco.com>
>>>>>>> Subject: [Tsvwg] Re: sctp-auth questions
>>>>>>>
>>>>>>> Vlad Yasevich wrote:
>>>>>>>
>>>>>>>> Hi All
>>>>>>>>
>>>>>>>> One more item from Draft 8:
>>>>>>>>
>>>>>>>> Section 3.1
>>>>>>>>
>>>>>>>>   The RANDOM parameter MUST be included once in the INIT or  
>>>>>>>> INIT-ACK
>>>>>>>>   chunk if the sender wants to send or receive authenticated
>>>>>>>> chunks to
>>>>>>>>   provide a 32 byte Random Number.
>>>>>>>>
>>>>>>>> The sentence reads almost like a run-on and I can't quite  
>>>>>>>> figure out
>>>>>>>> what "to provide a 32 byte Random Number" is trying to explain.
>>>>>>>> The first time I read it, I though it was part of the  
>>>>>>>> requirement,
>>>>>>>> but
>>>>>>>> I don't think it was meant to be.
>>>>>>>
>>>>>>> Ok, so it is meant to be a requirement (based on section  
>>>>>>> 6.1), but it
>>>>>>> is worded badly.
>>>>>>>
>>>>>>> Still needs to be reworded.
>>>>>>>
>>>>>>>
>>>>>>>> I this this sentence needs to clarified.
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>> -vlad
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>
>>>
>
>
> -- 
> Randall Stewart
> NSSTG - Cisco Systems Inc.
> 803-345-0369 <or> 803-317-4952 (cell)
>






From tsvwg-bounces@ietf.org Thu Jul 19 17:31:55 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBdb9-0005xO-T5; Thu, 19 Jul 2007 17:31:47 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IBdb8-0005vz-1H
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 19 Jul 2007 17:31:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBdb7-0005vr-MJ
	for tsvwg@ietf.org; Thu, 19 Jul 2007 17:31:45 -0400
Received: from smtpout.mac.com ([17.250.248.172])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBdb6-0002yU-7T
	for tsvwg@ietf.org; Thu, 19 Jul 2007 17:31:45 -0400
Received: from mac.com (smtpin02-en2 [10.13.10.147])
	by smtpout.mac.com (Xserve/smtpout02/MantshX 4.0) with ESMTP id
	l6JLVhkM007849; Thu, 19 Jul 2007 14:31:43 -0700 (PDT)
Received: from [192.168.1.64] (adsl-70-132-5-50.dsl.snfc21.sbcglobal.net
	[70.132.5.50]) (authenticated bits=0)
	by mac.com (Xserve/smtpin02/MantshX 4.0) with ESMTP id l6JLUwJC020141; 
	Thu, 19 Jul 2007 14:31:15 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v624)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <a77a82372c75e173c8679a03c3181cea@mac.com>
Content-Transfer-Encoding: 7bit
From: Sally Floyd <sallyfloyd@mac.com>
Date: Thu, 19 Jul 2007 14:30:56 -0700
To: tsvwg WG <tsvwg@ietf.org>
X-Mailer: Apple Mail (2.624)
X-Brightmail-Tracker: AAAAAA==
X-Brightmail-scanned: yes
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
Cc: 
Subject: [Tsvwg] feedback on draft-briscoe-tsvwg-ecn-tunnel-00
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Bob -

Here is some feedback on Layered Encapsulation of Congestion 
Notification,
draft-briscoe-tsvwg-ecn-tunnel-00.

As I have said earlier, it is fine by me to update RFC 3168 to say
that a tunnel ingress should copy the ECN field from the inner
header to the outer header.  So this feedback is about smaller bits
and pieces.  (SHOULD vs. MUST, for example...)

- Sally


Feedback on draft-briscoe-tsvwg-ecn-tunnel-00:

Section 3.1:
"ECN at the IP layer is designed to carry information about congestion
from a congested resource to some downstream node that will feed the
information back somehow to the point upstream of the congestion that
can regulate the load on the congested resource."

Actually, that is not true.  RFC 3168 has two parts, specifying
ECN in both IP and in TCP, but ECN in the IP layer wasn't designed
only for unicast transport protocols.  E.g., at the time multicast
was a big deal in some of the research community, with receivers
joining and leaving layered multicast groups.  From the first
paragraph of the Introduction of RFC 3168:

"We ... describe modifications needed to TCP to make it ECN-capable.
Modifications to other transport protocols (e.g., unreliable unicast
or multicast, reliable multicast, other reliable unicast transport
protocols) could be considered as those protocols are developed and
advance through the standards process."

And later, in Section 6 on "Support from the Transport Protocol":

"Second, the transport protocol must be capable of reacting
appropriately to the receipt of CE packets.  This reaction could be
in the form of the data receiver informing the data sender of the
received CE packet (e.g., TCP), of the data receiver unsubscribing to
a layered multicast group (e.g., RLM [MJV96]), or of some other
action that ultimately reduces the arrival rate of that flow on that
congested link."

So ECN was designed with transport protocols in mind, but it was not
designed only for unicast, TCP-like transport protocols.  In particular,
there could be protocols where the transport receiver is the actor,
not the transport sender.


Section 3.2:
"It might be useful for the tunnel egress to be able to tell whether
congestion occurred across a tunnel or upstream of it."

The rest of the paragraph is specific to multi-level congestion
marking such as PCN (and even in this case, I assume that the tunnel
egress can only tell whether congestion occurred across the tunnel
or upstream of it if the ECN field was not already at the highest
of the multi levels at tunnel ingress).

It seems *conceivable* to me that someone might want to design a
tunnel where the egress would want to know whether congestion
occurred across the tunnel or upstream of it, but where the ingress
was not a Load Regulator.  (I don't know why, offhand, though
multicast comes to mind.)  *If* one wanted to allow this in some
future tunnel, then one should change the MUST about copying the
ECN field from the inner to the outer header at ingress to a SHOULD.
And if one didn't want to allow this, then this should be made as
explicit as possible, I would say.  Making it completely clear that
when the ECN field is copied from the inner to the outer header at
ingress, then the tunnel egress won't necessarily be able to tell
whether congestion occurred across a tunnel or upstream of it.
(I guess that a simple way out would be just to stretch the
definition of "Load Regulator", to say that any time the tunnel
egress wants to be able to tell whether congestion occurred
across the tunnel or upstream of it, the ingress is called a
Load Regulator.)


Section 5:
In Table 1, are you ruling out the possibility of a future
tunnel design, with a Load Regulator at the ingress, where
packets are ECN-Capable within the tunnel, but not ECN-Capable
outside the tunnel?  (This could result in an inner header
that was not-ECT, but an outer header that was ECT or CE.)
Is this table specific to PCN?  It would seem OK to me to
think about an ECN-Capable tunnel with a Load Regulator in
the middle of a non-ECN-Capable end-to-end connection.


When the ingress is a Load Regulator, why "MUST" it reset
the outer heater to ECT(0)?  Isn't this PCN-specific?  Might
an ingress that is a Load Regulator in some cases want to
use both ECN(0) and ECN(1) *within the tunnel*, with some
tunnel-specific mechanism for using ECN(0) ad ECN(1) to
check for misbehaving nodes along the path?  (I am not
recommending it, just arguing against precluding
it unnecessarily...)


Section 9:
"With the rules as they stand in RFC3168 and RFC4301, within a
tunnel a CE marking could be added and subsequently removed by a
non-compliant node without detection, because the evidence of such
misbehaviour is removed by the decapsulator." Yep, as with this
document, RFC 3168 didn't copy ECT(0) or ECT(1) from the outer to
the inner header upon decapsulation.  But the tunnel egress, if it
wanted, could look to see if the ECT fields in the inner and outer
headers didn't match, and infer cheating within the tunnel, if it
wanted (in the RFC 3168 case, that is, where the ECT field from the
inner header is copied to the outer header).  But if you say that
an encapsulator that is a Load Regulator MUST set the outer header
to ECT(0), you lose that possibility of protection at the egress
of non-compliant nodes within the tunnel, it would seem to me.
Worth mentioning somewhere.



Nits:
 From the abstract:
This document "gives general principles to guide the design of
alternate congestion marking behaviours for specific PHBs and for
lower layer congestion notification schemes."

Where did this document do that?  That seems misleading to me.


Section 6:
When you first use "full-functionality" and "limited-functionality"
modes, you might want to refer the reader to RFC 3168.


Section 7:
"neither identified the need to raise an alarm if the inner header
was CE but the outer header was ECT."

RFC 3168 didn't identify the need to raise an alarm in this case
because there *is* no need to raise an alarm when the inner header
is not copied to the outer header, as is the case in RFC 3168.






From tsvwg-bounces@ietf.org Thu Jul 19 19:31:07 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBfSb-0006Ux-0s; Thu, 19 Jul 2007 19:31:05 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IBfSa-0006Uf-4t
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 19 Jul 2007 19:31:04 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBfSZ-0006UW-QF; Thu, 19 Jul 2007 19:31:03 -0400
Received: from smtpout.mac.com ([17.250.248.174])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IBfSZ-0008Og-7m; Thu, 19 Jul 2007 19:31:03 -0400
Received: from mac.com (smtpin08-en2 [10.13.10.153])
	by smtpout.mac.com (Xserve/smtpout04/MantshX 4.0) with ESMTP id
	l6JNV2Bf027891; Thu, 19 Jul 2007 16:31:02 -0700 (PDT)
Received: from [192.150.186.170] (laptop170.icsi.berkeley.edu
	[192.150.186.170]) (authenticated bits=0)
	by mac.com (Xserve/smtpin08/MantshX 4.0) with ESMTP id l6JNUWF6009841; 
	Thu, 19 Jul 2007 16:30:37 -0700 (PDT)
In-Reply-To: <5.2.1.1.2.20070617041232.04188110@pop3.jungle.bt.co.uk>
References: <5.2.1.1.2.20070617041232.04188110@pop3.jungle.bt.co.uk>
Mime-Version: 1.0 (Apple Message framework v624)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <3144d54f51c807e534a10759210d5729@mac.com>
Content-Transfer-Encoding: 7bit
From: Sally Floyd <sallyfloyd@mac.com>
Date: Thu, 19 Jul 2007 16:30:31 -0700
To: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
X-Mailer: Apple Mail (2.624)
X-Brightmail-Tracker: AAAAAA==
X-Brightmail-scanned: yes
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: PCN IETF list <pcn@ietf.org>, DCCP IETF list <dccp@ietf.org>,
	tsvwg IETF list <tsvwg@ietf.org>
Subject: [Tsvwg] Re: [dccp] Initial I-D: draft-briscoe-tsvwg-byte-pkt-mark-00
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Bob -

Some feedback on "Byte and Packet Congestion Notification",
draft-briscoe-tsvwg-byte-pkt-mark-00:

It seems odd to me to talk about RED in byte vs. packet mode, and
not to talk about the similar performance difference between
Drop-Tail queues in bytes vs. packets.  (Well, someone could
care about RED and not Drop-Tail because one cared only
about packet marks in an ECN environment, but for this document
it strikes me as quite odd to talk about RED in byte vs. packet mode,
and not to talk also about Drop-Tail queues in bytes vs. packets.)

I am enclosing some text from some 2/26/2007 email that I sent you
about this, in response to "draft-briscoe-tsvwg-byte-pkt-mark-00c".
(I didn't reread the new draft, but I did look at the diffs between
draft-briscoe-tsvwg-byte-pkt-mark-00 and
draft-briscoe-tsvwg-byte-pkt-mark-00c, and I didn't notice anything
added about Drop-Tail queues in bytes vs. packets.)

 From my 2/26/2007 email:
----------------------------------------------------------------
"As is discussed at length and illustrated with simulations in [RFC
4828], drop-tail queues also have a wide range of possible behaviors,
in terms of dropping packets from a flow proportionally to the
sending rate in bits per second, or to the sending rate in packets
per second, or something else entirely.  For example, the abstract
of [RFC 4828] includes the following:"

     "Flows using TFRC-SP compete reasonably fairly with large-packet TCP
     and TFRC flows in environments where large-packet flows and small-
     packet flows experience similar packet drop rates.  However, in
     environments where small-packet flows experience lower packet drop
     rates than large-packet flows (e.g., with Drop-Tail queues in units
     of bytes), TFRC-SP can receive considerably more than its share of
     the bandwidth."

"This is discussed more in Section 4.5.1, and in Appendix B.3 of that 
draft."

"My understanding is that buffer architectures in routers can be
complex, but one buffer architecture is to have a fixed number of
slots for packet headers in the output queue, with the actual data
packet stored elsewhere in the router.  So in this design, the queue
would essentially have a fixed number of slots for packet headers,
with each packet taking exactly one packet-header slot, regardless
of the packet size in bytes.   Functionally, this would be equivalent
to a Drop-Tail queue in packets in NS.  But there could also be
routers whose Drop-Tail queues are more like the Drop-Tail queue
in bytes in NS, where small packets are more likely than large
packets to find a slot in the queue.  So the complications are not
only about AQM..."
----------------------------------------------------------------


As an aside, in the future should I forward feedback about this draft to
only one of the three mailing lists above?

- Sally
http://www.icir.org/floyd/






From tsvwg-bounces@ietf.org Fri Jul 20 05:02:12 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBoNE-0008GW-Kh; Fri, 20 Jul 2007 05:02:08 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IBoND-0008GR-50
	for tsvwg-confirm+ok@megatron.ietf.org; Fri, 20 Jul 2007 05:02:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBoNC-0008GJ-OK
	for tsvwg@ietf.org; Fri, 20 Jul 2007 05:02:06 -0400
Received: from smtp4.smtp.bt.com ([217.32.164.151])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBoNB-0001Sj-8F
	for tsvwg@ietf.org; Fri, 20 Jul 2007 05:02:06 -0400
Received: from E03MVB2-UKBR.domain1.systemhost.net ([193.113.197.111]) by
	smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 20 Jul 2007 10:02:04 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Tsvwg] Does anyone have a defence in favour of flow ratefairness?
Date: Fri, 20 Jul 2007 10:02:05 +0100
Message-ID: <DB3E5D6F36600847BC70D451534EBCD5C32475@E03MVB2-UKBR.domain1.systemhost.net>
In-Reply-To: <107232.44814.qm@web36701.mail.mud.yahoo.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Tsvwg] Does anyone have a defence in favour of flow
	ratefairness?
Thread-Index: AcfKBITRE31cidSqSKq2IPFhVt0j7QApaWAg
From: <louise.burness@bt.com>
To: <zbest28@yahoo.com>,
	<tsvwg@ietf.org>
X-OriginalArrivalTime: 20 Jul 2007 09:02:04.0014 (UTC)
	FILETIME=[A420B0E0:01C7CAAC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: 
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org



I think that we should focus on technical wherever possible and leave =
the system open to be used in different ways in different parts of the =
world - I don't think technology should force any particular social or =
political opinion. I think cost fairness does allow different approaches =
to co-exist within a single network - so the goal of avoiding the rich =
shutting out the poor can be achieved in one network or country, and a =
goal of pure free market could also be achieved elsewhere.

At the moment I think we do have a technical problem that we should =
address - in times of congestion users with more technical knowledge can =
completely shut out na=EFve users.=20

-----Original Message-----
From: Zack Best [mailto:zbest28@yahoo.com]=20
Sent: 17 July 2007 17:03
To: tsvwg@ietf.org
Subject: Re: [Tsvwg] Does anyone have a defence in favour of flow =
ratefairness?

>From draft-floyd-tsvwg-besteffort-00b.txt

> One of the obvious dangers of simple
> implementations of QoS mechanisms or
> of cost-based fairness, in the absence of the protection of simple=20
> best-effort traffic, would be that the users with more money
> *could* end up completely shutting out users with less money in times=20
> of congestion.  There seems to be fairly widespread agreement that=20
> this would not be a desirable goal.

I am curious why this is not a desirable goal let alone why there is =
widespread agreement of this.

If people are paying a monthly fee to their ISP and if uninterrupted =
connectivity at relatively low bandwidth is important to them (which in =
most cases it is) wouldn't market forces work to make this happen?  I.e. =
ISPs would spend their money to insure to insure customers got what they =
wanted, lest they lose business.

On the other hand, may people (perhaps most of the
world) are excluded from the internet because they can't afford the =
basic monthly fee to connect.
A cost based system would theoretically lower the cost of entry for =
those who did not want to compete for bandwidth at contested times, and =
actually make limited connectivity available to a group previous =
excluded.

There is certainly a recurring argument in the political arena between =
the free market advocates, and those who claim the free market would =
result in unfairness that is best addressed by enforced equality at the =
expense of choice and flexibility.

I won't attempt to resolve that argument here, but my sympathies are =
certainly the the free market folks.  Experience has shown over and over =
that market forces do a better job at scarce resource allocation than =
detractors predict and a better job than the proposed alternatives.

This is not meant as a comment on the practicality of implementing cost =
based fairness, just as a defense of the goal.



      =20
_________________________________________________________________________=
___________
Pinpoint customers who are looking for what you sell.=20
http://searchmarketing.yahoo.com/







From tsvwg-bounces@ietf.org Fri Jul 20 05:57:09 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBpEG-0003mS-3W; Fri, 20 Jul 2007 05:56:56 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IBpEE-0003jT-AT
	for tsvwg-confirm+ok@megatron.ietf.org; Fri, 20 Jul 2007 05:56:54 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBpED-0003h7-Ue
	for tsvwg@ietf.org; Fri, 20 Jul 2007 05:56:53 -0400
Received: from exprod7og54.obsmtp.com ([64.18.2.163])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IBpED-0006H0-CN
	for tsvwg@ietf.org; Fri, 20 Jul 2007 05:56:53 -0400
Received: from source ([67.96.16.12]) (using TLSv1) by exprod7ob54.obsmtp.com
	([64.18.6.12]) with SMTP; Fri, 20 Jul 2007 02:56:51 PDT
Received: from ETSMSG-CINAV01.etsmsg.org ([65.90.82.49]) by
	naout-cinexs02.nasmtpout.emrsn.com with Microsoft
	SMTPSVC(6.0.3790.3959); Fri, 20 Jul 2007 06:08:23 -0400
Received: from ETSMSG-CINEXS01.etsmsg.org ([65.90.82.49]) by
	ETSMSG-CINAV01.etsmsg.org with InterScan Message Security Suite;
	Fri, 20 Jul 2007 05:51:51 -0400
Received: from ETSMSG-CINEXS01.etsmsg.org ([65.90.82.81]) by
	ETSMSG-CINEXS01.etsmsg.org with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 20 Jul 2007 05:51:50 -0400
Received: from ant.artesyncp.com ([65.90.82.49]) by ETSMSG-CINEXS01.etsmsg.org
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 20 Jul 2007 05:51:50 -0400
Received: from stephane by ant.artesyncp.com with local (Exim 4.67)
	(envelope-from <stephane@artesyncp.com>) id 1IBp9J-0007hf-PK
	for tsvwg@ietf.org; Fri, 20 Jul 2007 10:51:49 +0100
Date: Fri, 20 Jul 2007 10:51:49 +0100
From: Stephane Chazelas <stephane@artesyncp.com>
To: tsvwg <tsvwg@ietf.org>
Subject: Re: [Tsvwg] comments and questions on draft-ietf-tsvwg-sctpsocket-15
Message-ID: <20070720095149.GM9304@artesyncp.com>
References: <20070711163947.GD6418@artesyncp.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070711163947.GD6418@artesyncp.com>
User-Agent: mutt-ng/devel-r562 (Linux)
X-OriginalArrivalTime: 20 Jul 2007 09:51:50.0560 (UTC)
	FILETIME=[983F7200:01C7CAB3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

On Wed, Jul 11, 2007 at 05:39:47PM +0100, Stephane Chazelas wrote:
> Hi guys,
> 
> while looking at the details of what should be done upon send*()
> with no data, I found some areas of the Socket draft that
> confused me.
> 
> Could you please help me clarify them?

Hi there,

doesn't look like those considerations raise a lot of interest
:). I guess the point I was mostly interested in having your
opinion about is the one below.

I've another concern about this draft on another point of
detail, this time about the SCTP_DEFAULT_SEND_PARAM in 1-to-many
style.

I understand that this options affects subsequent sendto()s to
the association specified in sinfo_assoc_id, or if
sinfo_assoc_id is 0 to any newly created association from now
on. Now, what about the SCTP_SENDALL flag?

When that flag is set in the sndrcv structure in the ancillary
data of a sendmsg(), then the destination address or the
sinfo_assoc_id is ignored, the message is sent to every
association on the socket (and at the same time override the
default send param of each association).

But when it's set in the default send param of a specific
association, does that mean that anytime we do a sendto() to
that association, the message will be automatically forwarded to
every other association in the socket?

After a setsockopt with SCTP_DEFAULT_SEND_PARAM with
sinfo_assoc_id == 0 and sinfo_flags == SCTP_SENDALL, should
every sendto() go to every association, or only those sendto()s
sent to addresses for which there is no association yet?

[...]
> 6.1:
>   > Note, if an application calls a send function with no user data and
>   > no ancillary data the SCTP implementation should reject the request
>   > with an appropriate error message.  An implementation is NOT allowed
>   > to send a Data chunk with no user data RFC2960 [RFC2960].
> 
>   OK, but then what about a sendmsg() with ancillary data and no user
>   data?
> 
>   The draft suggests that we may send a SCTP_SNDRCV structure with
>   SCTP_EOF and no data if we want to close a 1-to-many association.
> 
>   It suggests as well that we may be able to use SCTP_ABORT with no data
>   if we want to abort an association without giving a reason.
> 
>   But what about the other possible usages of SCTP_SNDRCV and SCTP_INIT?
> 
>   If we do a sendmsg() with an SCTP_INIT and no user data,
>   should it automatically start an association without sending
>   data?
> 
>   If yes, then why not allowing a user to do a sendmsg() with neither
>   data nor ancillary data, to allow him to establish an association
>   using the default init parameters?
> 
>   Also, what about a sendmsg() with SCTP_ABORT (or SCTP_EOF and no data)
>   to a destination to which we're not associated yet? Should it
>   establish and then close an association?

TIA and best regards,
Stephane





From tsvwg-bounces@ietf.org Fri Jul 20 06:00:35 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBpHl-0000kA-TB; Fri, 20 Jul 2007 06:00:33 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IBpHk-0000k5-VZ
	for tsvwg-confirm+ok@megatron.ietf.org; Fri, 20 Jul 2007 06:00:32 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBpHk-0000jw-K2
	for tsvwg@ietf.org; Fri, 20 Jul 2007 06:00:32 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IBpHk-0006LT-3M
	for tsvwg@ietf.org; Fri, 20 Jul 2007 06:00:32 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 20 Jul 2007 12:00:10 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAPYkoEaQ/uCLZmdsb2JhbACPTwsKJA
X-IronPort-AV: i="4.16,562,1175464800"; 
	d="scan'208"; a="148561895:sNHT55784635248"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6KA08ol005284; 
	Fri, 20 Jul 2007 12:00:08 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6K9xvlH019680; 
	Fri, 20 Jul 2007 10:00:08 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 20 Jul 2007 12:00:08 +0200
Received: from [10.0.0.16] ([10.61.82.52]) by xfe-ams-331.emea.cisco.com with
	Microsoft SMTPSVC(6.0.3790.1830); Fri, 20 Jul 2007 12:00:07 +0200
In-Reply-To: <462636D9.9090607@ericsson.com>
References: <4607D8E9.6090300@ericsson.com> <462636D9.9090607@ericsson.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <358E40DB-5884-4F4A-9474-CFB93EF0C418@cisco.com>
Content-Transfer-Encoding: 7bit
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
Subject: Re: [Tsvwg] WG last call of draft-ietf-tsvwg-emergency-rsvp-02
Date: Fri, 20 Jul 2007 11:57:09 +0200
To: Magnus Westerlund <magnus.westerlund@ericsson.com>,
	tsvwg chair <tsvwg-chairs@tools.ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 20 Jul 2007 10:00:07.0934 (UTC)
	FILETIME=[C0B4B1E0:01C7CAB4]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1712; t=1184925608;
	x=1185789608; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.com>
	|Subject:=20Re=3A=20[Tsvwg]=20WG=20last=20call=20of=20draft-ietf-tsvwg-em
	ergency-rsvp-02 |Sender:=20;
	bh=kfhvRiNDR/gW6T5A1RZDghSfqqI5Gu71XCj+dK5gVfE=;
	b=CXdDA9DK/tSD6q2IwHHhZLm7J6OOrW1F7hBu974VW9NhPmlRCp5jElnKstMYlmhhiN+EN5B9
	WfZKqH/jsezzh/S+2j/EBgZMKPnBdFApECFizunASqyHrNYfONN/baLq;
Authentication-Results: ams-dkim-2; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hello Magnus, Lars, James,

Just to keep everyone on the same page:

On 18 Apr 2007, at 17:18, Magnus Westerlund wrote:

> Magnus Westerlund skrev:
>> This announces the start of the WG last call of "Resource  
>> ReSerVation Protovol (RSVP) Extensions for Emergency Services"  
>> with the intended status of proposed standard:
>> http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-emergency- 
>> rsvp-02.txt
>> Please provide positive or negative feedback before the 13th of  
>> April.
>
> Hi,
>
> This WG last call has now ended. Authors please produce an updated  
> version to address the comments that come in. If there are still  
> some issues where there isn't consensus please continue the  
> discussion.

The recently posted draft-ietf-tsvwg-emergency-rsvp-03.txt  
incorporated resolution of the WG Last Call comments from Fil  
Dickinson, from Janet Gunn and from Lou Berger.
We also updated the Security Considerations section (consistent with  
the updates also done on rsvp-proxy-approaches and rsvp-proxy-protocol).

So the document should be now ready to progress to the next steps.

Francois

PS: we'll close the loop with Lou and bring it up if any of his  
points needs further work.


>
> Cheers
>
> Magnus Westerlund
>
> IETF Transport Area Director & TSVWG Chair
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM/M
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------





From tsvwg-bounces@ietf.org Fri Jul 20 09:36:41 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBsep-0005zh-4B; Fri, 20 Jul 2007 09:36:35 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IBseo-0005uK-4d
	for tsvwg-confirm+ok@megatron.ietf.org; Fri, 20 Jul 2007 09:36:34 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBsen-0005sZ-OH
	for tsvwg@ietf.org; Fri, 20 Jul 2007 09:36:33 -0400
Received: from atlrel6.hp.com ([156.153.255.205])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IBsen-0002c8-6l
	for tsvwg@ietf.org; Fri, 20 Jul 2007 09:36:33 -0400
Received: from smtp1.fc.hp.com (smtp.fc.hp.com [15.15.136.127])
	by atlrel6.hp.com (Postfix) with ESMTP id 4507437B74;
	Fri, 20 Jul 2007 09:34:21 -0400 (EDT)
Received: from [16.116.113.226] (galen.zko.hp.com [16.116.113.226])
	by smtp1.fc.hp.com (Postfix) with ESMTP id 80124149F48;
	Fri, 20 Jul 2007 13:33:20 +0000 (UTC)
Message-ID: <46A0B9A0.3010400@hp.com>
Date: Fri, 20 Jul 2007 09:33:20 -0400
From: Vlad Yasevich <vladislav.yasevich@hp.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070604)
MIME-Version: 1.0
To: Stephane Chazelas <stephane@artesyncp.com>
Subject: Re: [Tsvwg] comments and questions on draft-ietf-tsvwg-sctpsocket-15
References: <20070711163947.GD6418@artesyncp.com>
In-Reply-To: <20070711163947.GD6418@artesyncp.com>
X-Enigmail-Version: 0.95.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Cc: tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Stephane Chazelas wrote:
> Hi guys,
> 
> while looking at the details of what should be done upon send*()
> with no data, I found some areas of the Socket draft that
> confused me.
> 
> Could you please help me clarify them?
> 
> 3.1.5: (knitpicking)
>   > To gracefully shutdown a specific association represented by the one-
>   > to-many style socket, an application should use the sendmsg() call,
>   > and including the SCTP_EOF flag.  A user may optionally terminate an
>   > association non-gracefully by sending with the SCTP_ABORT flag and
>   > possibly passing a user specified abort code in the data field.  Both
> 
>   What "data field"? 5.2.2 indicates that that's msg_iov, but that field
>   is described as "scatter/gather array", not "data".

Would the following be better?

    A user may optionally terminate an association non-gracefully by sending with
    the SCTP_ABORT flag and possibly providing a user specified abort code as
    data.

> 
> 5.1:
> 
>   > The scatter/gather buffers, or I/O vectors (pointed to by the msg_iov
>   > field) are treated as a single SCTP data chunk, rather than multiple
>   > chunks, for both sendmsg() and recvmsg().
> 
>   possible confusion with protocol DATA chunks. Shouldn't it be "single
>   SCTP message". A stack may still fragment the message into several
>   DATA chunks to fit in the MTU. All those DATA chunks would have the
>   same SSN.

Yes, should be a single message.

> 
> 5.2:
> 
>   > There are two kinds of ancillary data used by SCTP: initialization
>   > data, and, header information (SNDRCV).  Initialization data (one-to-
>   > many style only) sets protocol parameters for new associations.
>   > Section 5.2.1 provides more details.  Header information can set or
>   > report parameters on individual messages in a stream.  See
>   > Section 5.2.2 for how to use SNDRCV ancillary data.
> 
>   Why 1-to-many only? Especially when 4.1.5 mentions explicitely that you
>   can use an SCTP_INIT if you want to send data at the same time as you
>   connect?:
> 
>   > Note that SCTP allows data exchange, similar to T/TCP RFC1644
>   > [RFC1644], during the association set up phase.  If an application
>   > wants to do this, it cannot use connect() call.  Instead, it should
> 			           ^
>                                   the
>   > use sendto() or sendmsg() to initiate an association.  If it uses
>   > sendto() and it wants to change initialization behavior, it needs to
>   > use the SCTP_INITMSG socket option before calling sendto().  Or it
>   > can use SCTP_INIT type sendmsg() to initiate an association without
>   > doing the setsockopt().
> 
>   Inconsistency?

Appears to be a slight one.

> 
> 6.1:
>   > Note, if an application calls a send function with no user data and
>   > no ancillary data the SCTP implementation should reject the request
>   > with an appropriate error message.  An implementation is NOT allowed
>   > to send a Data chunk with no user data RFC2960 [RFC2960].
> 
>   OK, but then what about a sendmsg() with ancillary data and no user
>   data?
> 
>   The draft suggests that we may send a SCTP_SNDRCV structure with
>   SCTP_EOF and no data if we want to close a 1-to-many association.
> 
>   It suggests as well that we may be able to use SCTP_ABORT with no data
>   if we want to abort an association without giving a reason.
> 
>   But what about the other possible usages of SCTP_SNDRCV and SCTP_INIT?

Those would be invalid.

> 
>   If we do a sendmsg() with an SCTP_INIT and no user data,
>   should it automatically start an association without sending
>   data?

Not that I can see...

> 
>   If yes, then why not allowing a user to do a sendmsg() with neither
>   data nor ancillary data, to allow him to establish an association
>   using the default init parameters?
> 
>   Also, what about a sendmsg() with SCTP_ABORT (or SCTP_EOF and no data)
>   to a destination to which we're not associated yet? Should it
>   establish and then close an association?

No.

-vlad





From tsvwg-bounces@ietf.org Fri Jul 20 14:35:58 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBxKO-0005UL-Ub; Fri, 20 Jul 2007 14:35:48 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IBxKN-0005UE-Mf
	for tsvwg-confirm+ok@megatron.ietf.org; Fri, 20 Jul 2007 14:35:47 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBxKN-0005U6-C2
	for tsvwg@ietf.org; Fri, 20 Jul 2007 14:35:47 -0400
Received: from sccrmhc15.comcast.net ([63.240.77.85])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IBxKM-0000iH-U9
	for tsvwg@ietf.org; Fri, 20 Jul 2007 14:35:47 -0400
Received: from [192.168.1.2]
	(c-69-250-218-72.hsd1.md.comcast.net[69.250.218.72])
	by comcast.net (sccrmhc15) with SMTP
	id <20070720183545015001v4qbe>; Fri, 20 Jul 2007 18:35:46 +0000
In-Reply-To: <02d001c7bffc$450d93d0$0200a8c0@your029b8cecfe>
References: <XFE-RTP-202e4fDGCl9000002ec@xfe-rtp-202.amer.cisco.com>
	<02d001c7bffc$450d93d0$0200a8c0@your029b8cecfe>
Mime-Version: 1.0 (Apple Message framework v752.2)
X-Priority: 3
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <AE456C42-761D-43B0-A039-6D4CD1D3421B@g11.org.uk>
Content-Transfer-Encoding: 7bit
From: ken carlberg <carlberg@g11.org.uk>
Subject: Re: [Tsvwg] New ID: draft-polk-tsvwg-signaled-domain-id-00
Date: Fri, 20 Jul 2007 14:35:43 -0400
To: James Polk <jmpolk@cisco.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

James,

here are some comments and questions on the draft...

- to start off with, you definitely need a terminology section that  
clarifies Policy Domain, Domain identifier (which seems to equate to  
an AS), and sub-domain.  I think Janet suggested Service Domain, or  
maybe some other term that doesn't include "domain" so as to minimize  
confusion.

- and if the Domain Identifier == AS, then you'll want to bump up the  
size of the field to 32 bits so that it aligns with rfc-4893.

- section 1, 3'rd paragraph.  I'm paraphrasing what you are saying  
here, but when you speak of the risk of some domains arbitrarily  
using high priority values, hence the need for domain/sub-domain  
identifiers, it seems to me that you are speaking of apples and  
oranges.  The former is really a function of authorization and  
authentication, while the latter seems like an easier approach to  
accomplish access control lists (ie, domains versus source net  
prefixes).

And this brings up another point.  Would you want to accomplish some  
(maybe all?) of this work in the form of an extension to X.509v3 that  
would include the identifiers defined in this draft?

- is it your intention to use this domain ID element only in  
conjunction with rfc-3181?  Or could you envision it being applied to  
draft-ietf-tsvwg-emergency-rsvp-02?  If yes, you'll need to broaden  
some of the text in the draft so that it can be applied to more than  
one policy element.  This *may* also complicate things with respect  
to Error codes.

- Section 4.  You may want to give some thought to adding or changing  
the structures of the existing fields into a series of TLVs so that  
you have some additional flexibility in adding granularity to sub- 
domains and possibly domains.

- page 5 (top).  When you say that a domain and subdomain MAY be  
paired with a SIP RPH header NameSpace, a question arises as to which  
NameSpace?  (given the fact that rfc-4412 says that multiple  
different NameSpaces may exist in the SIP message.

- Section 5, Item 5.  if sub-domains are not to be registered, and  
are administered locally, how do achieve or help ensure  
interoperability if these sub-domains are added by one adminsitrative  
domain and examined by another?

- Section 5, Item 8.  The first sentence says "...entities SHOULD NOT  
change Domain-value field".  I assume you mean the Transit Domain- 
Value, since later on in Item 10 says the "Original-Domain-Value MUST  
NOT be changed..."

- I would disagree that your document introduces no additional  
security considerations above that found in rfc-3181.  to begin with,  
you'll need to update and clarify what is meant by a "trusted zone or  
at least a single zone (no zone boundaries are crossed)" as stated in  
the Security Considerations of rfc-3181.   Perhaps I've missed  
something, but the picture you have painted in this document would  
leave it open to being used across administrative boundaries that may  
not have a continual chain of trust.

-ken








From tsvwg-bounces@ietf.org Fri Jul 20 15:13:37 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBxux-0007jR-6y; Fri, 20 Jul 2007 15:13:35 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IBxuw-0007jC-0Z
	for tsvwg-confirm+ok@megatron.ietf.org; Fri, 20 Jul 2007 15:13:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBxuv-0007j4-NC
	for tsvwg@ietf.org; Fri, 20 Jul 2007 15:13:33 -0400
Received: from mail130.messagelabs.com ([216.82.250.163])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IBxuu-0005vp-PZ
	for tsvwg@ietf.org; Fri, 20 Jul 2007 15:13:33 -0400
X-VirusChecked: Checked
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-10.tower-130.messagelabs.com!1184958806!11988388!1
X-StarScan-Version: 5.5.12.11; banners=-,-,-
X-Originating-IP: [20.137.52.151]
Received: (qmail 8543 invoked from network); 20 Jul 2007 19:13:27 -0000
Received: from amer-mta07.csc.com (HELO amer-mta07.csc.com) (20.137.52.151)
	by server-10.tower-130.messagelabs.com with AES256-SHA encrypted SMTP;
	20 Jul 2007 19:13:27 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245])
	by amer-mta07.csc.com (Switch-3.1.6/Switch-3.1.7) with ESMTP id
	l6KJDYAQ006870; Fri, 20 Jul 2007 15:13:39 -0400 (EDT)
In-Reply-To: <AE456C42-761D-43B0-A039-6D4CD1D3421B@g11.org.uk>
To: ken carlberg <carlberg@g11.org.uk>
Subject: Re: [Tsvwg] New ID: draft-polk-tsvwg-signaled-domain-id-00
MIME-Version: 1.0
X-Mailer: Lotus Notes 652HF83 November 04, 2004
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OF82F29BE5.C0269793-ON8525731E.0068036B-8525731E.00688A05@csc.com>
Date: Fri, 20 Jul 2007 15:01:50 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 7.0.2FP1
	HF180|March 29, 2007) at 07/20/2007 03:12:06 PM,
	Serialize complete at 07/20/2007 03:12:06 PM
Content-Type: multipart/alternative;
	boundary="=_alternative 006889BD8525731E_="
X-Spam-Score: -4.0 (----)
X-Scan-Signature: d9238570526f12788af3d33c67f37625
Cc: James Polk <jmpolk@cisco.com>, tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

This is a multipart message in MIME format.
--=_alternative 006889BD8525731E_=
Content-Type: text/plain; charset="US-ASCII"

I'd be interested in having a better understanding about the relationship 
between 

the DOMAIN_SUBDOMAIN Element in draft-polk-tsvwg-signaled-domain-id-00

and

the Application-Level Resource Priority Policy Element in 
draft-ietf-tsvwg-emergency-rsvp-03, especially the ALRP Namespace.

Janet


ken carlberg <carlberg@g11.org.uk> wrote on 07/20/2007 02:35:43 PM:

> James,
> 
> here are some comments and questions on the draft...
> 
> - to start off with, you definitely need a terminology section that 
> clarifies Policy Domain, Domain identifier (which seems to equate to 
> an AS), and sub-domain.  I think Janet suggested Service Domain, or 
> maybe some other term that doesn't include "domain" so as to minimize 
> confusion.
> 
> - and if the Domain Identifier == AS, then you'll want to bump up the 
> size of the field to 32 bits so that it aligns with rfc-4893.
> 
> - section 1, 3'rd paragraph.  I'm paraphrasing what you are saying 
> here, but when you speak of the risk of some domains arbitrarily 
> using high priority values, hence the need for domain/sub-domain 
> identifiers, it seems to me that you are speaking of apples and 
> oranges.  The former is really a function of authorization and 
> authentication, while the latter seems like an easier approach to 
> accomplish access control lists (ie, domains versus source net 
> prefixes).
> 
> And this brings up another point.  Would you want to accomplish some 
> (maybe all?) of this work in the form of an extension to X.509v3 that 
> would include the identifiers defined in this draft?
> 
> - is it your intention to use this domain ID element only in 
> conjunction with rfc-3181?  Or could you envision it being applied to 
> draft-ietf-tsvwg-emergency-rsvp-02?  If yes, you'll need to broaden 
> some of the text in the draft so that it can be applied to more than 
> one policy element.  This *may* also complicate things with respect 
> to Error codes.
> 
> - Section 4.  You may want to give some thought to adding or changing 
> the structures of the existing fields into a series of TLVs so that 
> you have some additional flexibility in adding granularity to sub- 
> domains and possibly domains.
> 
> - page 5 (top).  When you say that a domain and subdomain MAY be 
> paired with a SIP RPH header NameSpace, a question arises as to which 
> NameSpace?  (given the fact that rfc-4412 says that multiple 
> different NameSpaces may exist in the SIP message.
> 
> - Section 5, Item 5.  if sub-domains are not to be registered, and 
> are administered locally, how do achieve or help ensure 
> interoperability if these sub-domains are added by one adminsitrative 
> domain and examined by another?
> 
> - Section 5, Item 8.  The first sentence says "...entities SHOULD NOT 
> change Domain-value field".  I assume you mean the Transit Domain- 
> Value, since later on in Item 10 says the "Original-Domain-Value MUST 
> NOT be changed..."
> 
> - I would disagree that your document introduces no additional 
> security considerations above that found in rfc-3181.  to begin with, 
> you'll need to update and clarify what is meant by a "trusted zone or 
> at least a single zone (no zone boundaries are crossed)" as stated in 
> the Security Considerations of rfc-3181.   Perhaps I've missed 
> something, but the picture you have painted in this document would 
> leave it open to being used across administrative boundaries that may 
> not have a continual chain of trust.
> 
> -ken
> 
> 
> 
> 
> 

--=_alternative 006889BD8525731E_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif"><br>
<br>
I'd be interested in having a better understanding about the relationship
between </font>
<br>
<br><font size=2 face="sans-serif">the DOMAIN_SUBDOMAIN Element in draft-polk-tsvwg-signaled-domain-id-00</font>
<br>
<br><font size=2 face="sans-serif">and</font>
<br>
<br><font size=2 face="sans-serif">the Application-Level Resource Priority
Policy Element in &nbsp; draft-ietf-tsvwg-emergency-rsvp-03, especially
the ALRP Namespace.</font>
<br>
<br><font size=2 face="sans-serif">Janet<br>
</font>
<br>
<br><font size=2><tt>ken carlberg &lt;carlberg@g11.org.uk&gt; wrote on
07/20/2007 02:35:43 PM:<br>
<br>
&gt; James,<br>
&gt; <br>
&gt; here are some comments and questions on the draft...<br>
&gt; <br>
&gt; - to start off with, you definitely need a terminology section that
&nbsp;<br>
&gt; clarifies Policy Domain, Domain identifier (which seems to equate
to &nbsp;<br>
&gt; an AS), and sub-domain. &nbsp;I think Janet suggested Service Domain,
or &nbsp;<br>
&gt; maybe some other term that doesn't include &quot;domain&quot; so as
to minimize &nbsp;<br>
&gt; confusion.<br>
&gt; <br>
&gt; - and if the Domain Identifier == AS, then you'll want to bump up
the &nbsp;<br>
&gt; size of the field to 32 bits so that it aligns with rfc-4893.<br>
&gt; <br>
&gt; - section 1, 3'rd paragraph. &nbsp;I'm paraphrasing what you are saying
&nbsp;<br>
&gt; here, but when you speak of the risk of some domains arbitrarily &nbsp;<br>
&gt; using high priority values, hence the need for domain/sub-domain &nbsp;<br>
&gt; identifiers, it seems to me that you are speaking of apples and &nbsp;<br>
&gt; oranges. &nbsp;The former is really a function of authorization and
&nbsp;<br>
&gt; authentication, while the latter seems like an easier approach to
&nbsp;<br>
&gt; accomplish access control lists (ie, domains versus source net &nbsp;<br>
&gt; prefixes).<br>
&gt; <br>
&gt; And this brings up another point. &nbsp;Would you want to accomplish
some &nbsp;<br>
&gt; (maybe all?) of this work in the form of an extension to X.509v3 that
&nbsp;<br>
&gt; would include the identifiers defined in this draft?<br>
&gt; <br>
&gt; - is it your intention to use this domain ID element only in &nbsp;<br>
&gt; conjunction with rfc-3181? &nbsp;Or could you envision it being applied
to &nbsp;<br>
&gt; draft-ietf-tsvwg-emergency-rsvp-02? &nbsp;If yes, you'll need to broaden
&nbsp;<br>
&gt; some of the text in the draft so that it can be applied to more than
&nbsp;<br>
&gt; one policy element. &nbsp;This *may* also complicate things with respect
&nbsp;<br>
&gt; to Error codes.<br>
&gt; <br>
&gt; - Section 4. &nbsp;You may want to give some thought to adding or
changing &nbsp;<br>
&gt; the structures of the existing fields into a series of TLVs so that
&nbsp;<br>
&gt; you have some additional flexibility in adding granularity to sub-
<br>
&gt; domains and possibly domains.<br>
&gt; <br>
&gt; - page 5 (top). &nbsp;When you say that a domain and subdomain MAY
be &nbsp;<br>
&gt; paired with a SIP RPH header NameSpace, a question arises as to which
&nbsp;<br>
&gt; NameSpace? &nbsp;(given the fact that rfc-4412 says that multiple
&nbsp;<br>
&gt; different NameSpaces may exist in the SIP message.<br>
&gt; <br>
&gt; - Section 5, Item 5. &nbsp;if sub-domains are not to be registered,
and &nbsp;<br>
&gt; are administered locally, how do achieve or help ensure &nbsp;<br>
&gt; interoperability if these sub-domains are added by one adminsitrative
&nbsp;<br>
&gt; domain and examined by another?<br>
&gt; <br>
&gt; - Section 5, Item 8. &nbsp;The first sentence says &quot;...entities
SHOULD NOT &nbsp;<br>
&gt; change Domain-value field&quot;. &nbsp;I assume you mean the Transit
Domain- <br>
&gt; Value, since later on in Item 10 says the &quot;Original-Domain-Value
MUST &nbsp;<br>
&gt; NOT be changed...&quot;<br>
&gt; <br>
&gt; - I would disagree that your document introduces no additional &nbsp;<br>
&gt; security considerations above that found in rfc-3181. &nbsp;to begin
with, &nbsp;<br>
&gt; you'll need to update and clarify what is meant by a &quot;trusted
zone or &nbsp;<br>
&gt; at least a single zone (no zone boundaries are crossed)&quot; as stated
in &nbsp;<br>
&gt; the Security Considerations of rfc-3181. &nbsp; Perhaps I've missed
&nbsp;<br>
&gt; something, but the picture you have painted in this document would
&nbsp;<br>
&gt; leave it open to being used across administrative boundaries that
may &nbsp;<br>
&gt; not have a continual chain of trust.<br>
&gt; <br>
&gt; -ken<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
</tt></font>
--=_alternative 006889BD8525731E_=--





From tsvwg-bounces@ietf.org Fri Jul 20 15:22:54 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBy3x-0007rX-A5; Fri, 20 Jul 2007 15:22:53 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IBy3v-0007rR-T9
	for tsvwg-confirm+ok@megatron.ietf.org; Fri, 20 Jul 2007 15:22:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBy3v-0007rI-Jc
	for tsvwg@ietf.org; Fri, 20 Jul 2007 15:22:51 -0400
Received: from rwcrmhc15.comcast.net ([204.127.192.85])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBy3u-00068Z-KP
	for tsvwg@ietf.org; Fri, 20 Jul 2007 15:22:51 -0400
Received: from [192.168.1.2]
	(c-69-250-218-72.hsd1.md.comcast.net[69.250.218.72])
	by comcast.net (rwcrmhc15) with SMTP
	id <20070720192249m1500a2rt1e>; Fri, 20 Jul 2007 19:22:49 +0000
In-Reply-To: <OF82F29BE5.C0269793-ON8525731E.0068036B-8525731E.00688A05@csc.com>
References: <OF82F29BE5.C0269793-ON8525731E.0068036B-8525731E.00688A05@csc.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: multipart/alternative; boundary=Apple-Mail-1-493737405
Message-Id: <E3AC55D6-6A48-4AA1-8F1A-FBB0B37EC38F@g11.org.uk>
From: ken carlberg <carlberg@g11.org.uk>
Subject: Re: [Tsvwg] New ID: draft-polk-tsvwg-signaled-domain-id-00
Date: Fri, 20 Jul 2007 15:22:47 -0400
To: Janet P Gunn <jgunn6@csc.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a0494a0224ca59418dd8f92694c1fdb
Cc: James Polk <jmpolk@cisco.com>, tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org


--Apple-Mail-1-493737405
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

At present, there is no relationship :-)

-ken


On Jul 20, 2007, at 3:01 PM, Janet P Gunn wrote:

>
>
>
> I'd be interested in having a better understanding about the  
> relationship between
>
> the DOMAIN_SUBDOMAIN Element in draft-polk-tsvwg-signaled-domain-id-00
>
> and
>
> the Application-Level Resource Priority Policy Element in   draft- 
> ietf-tsvwg-emergency-rsvp-03, especially the ALRP Namespace.
>
> Janet
>
>
> ken carlberg <carlberg@g11.org.uk> wrote on 07/20/2007 02:35:43 PM:
>
> > James,
> >
> > here are some comments and questions on the draft...
> >
> > - to start off with, you definitely need a terminology section that
> > clarifies Policy Domain, Domain identifier (which seems to equate to
> > an AS), and sub-domain.  I think Janet suggested Service Domain, or
> > maybe some other term that doesn't include "domain" so as to  
> minimize
> > confusion.
> >
> > - and if the Domain Identifier == AS, then you'll want to bump up  
> the
> > size of the field to 32 bits so that it aligns with rfc-4893.
> >
> > - section 1, 3'rd paragraph.  I'm paraphrasing what you are saying
> > here, but when you speak of the risk of some domains arbitrarily
> > using high priority values, hence the need for domain/sub-domain
> > identifiers, it seems to me that you are speaking of apples and
> > oranges.  The former is really a function of authorization and
> > authentication, while the latter seems like an easier approach to
> > accomplish access control lists (ie, domains versus source net
> > prefixes).
> >
> > And this brings up another point.  Would you want to accomplish some
> > (maybe all?) of this work in the form of an extension to X.509v3  
> that
> > would include the identifiers defined in this draft?
> >
> > - is it your intention to use this domain ID element only in
> > conjunction with rfc-3181?  Or could you envision it being  
> applied to
> > draft-ietf-tsvwg-emergency-rsvp-02?  If yes, you'll need to broaden
> > some of the text in the draft so that it can be applied to more than
> > one policy element.  This *may* also complicate things with respect
> > to Error codes.
> >
> > - Section 4.  You may want to give some thought to adding or  
> changing
> > the structures of the existing fields into a series of TLVs so that
> > you have some additional flexibility in adding granularity to sub-
> > domains and possibly domains.
> >
> > - page 5 (top).  When you say that a domain and subdomain MAY be
> > paired with a SIP RPH header NameSpace, a question arises as to  
> which
> > NameSpace?  (given the fact that rfc-4412 says that multiple
> > different NameSpaces may exist in the SIP message.
> >
> > - Section 5, Item 5.  if sub-domains are not to be registered, and
> > are administered locally, how do achieve or help ensure
> > interoperability if these sub-domains are added by one  
> adminsitrative
> > domain and examined by another?
> >
> > - Section 5, Item 8.  The first sentence says "...entities SHOULD  
> NOT
> > change Domain-value field".  I assume you mean the Transit Domain-
> > Value, since later on in Item 10 says the "Original-Domain-Value  
> MUST
> > NOT be changed..."
> >
> > - I would disagree that your document introduces no additional
> > security considerations above that found in rfc-3181.  to begin  
> with,
> > you'll need to update and clarify what is meant by a "trusted  
> zone or
> > at least a single zone (no zone boundaries are crossed)" as  
> stated in
> > the Security Considerations of rfc-3181.   Perhaps I've missed
> > something, but the picture you have painted in this document would
> > leave it open to being used across administrative boundaries that  
> may
> > not have a continual chain of trust.
> >
> > -ken
> >
> >
> >
> >
> >


--Apple-Mail-1-493737405
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; ">At present, there is no =
relationship :-)<DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>-ken</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV><BR><DIV><DIV>On Jul 20, =
2007, at 3:01 PM, Janet P Gunn wrote:</DIV><BR =
class=3D"Apple-interchange-newline"><BLOCKQUOTE type=3D"cite"><BR><FONT =
size=3D"2" face=3D"sans-serif"><BR> <BR> I'd be interested in having a =
better understanding about the relationship between </FONT> <BR> =
<BR><FONT size=3D"2" face=3D"sans-serif">the DOMAIN_SUBDOMAIN Element in =
draft-polk-tsvwg-signaled-domain-id-00</FONT> <BR> <BR><FONT size=3D"2" =
face=3D"sans-serif">and</FONT> <BR> <BR><FONT size=3D"2" =
face=3D"sans-serif">the Application-Level Resource Priority Policy =
Element in =A0 draft-ietf-tsvwg-emergency-rsvp-03, especially the ALRP =
Namespace.</FONT> <BR> <BR><FONT size=3D"2" face=3D"sans-serif">Janet<BR> =
</FONT> <BR> <BR><FONT size=3D"2"><TT>ken carlberg &lt;<A =
href=3D"mailto:carlberg@g11.org.uk">carlberg@g11.org.uk</A>&gt; wrote on =
07/20/2007 02:35:43 PM:<BR> <BR> &gt; James,<BR> &gt; <BR> &gt; here are =
some comments and questions on the draft...<BR> &gt; <BR> &gt; - to =
start off with, you definitely need a terminology section that =A0<BR> =
&gt; clarifies Policy Domain, Domain identifier (which seems to equate =
to =A0<BR> &gt; an AS), and sub-domain. =A0I think Janet suggested =
Service Domain, or =A0<BR> &gt; maybe some other term that doesn't =
include "domain" so as to minimize =A0<BR> &gt; confusion.<BR> &gt; <BR> =
&gt; - and if the Domain Identifier =3D=3D AS, then you'll want to bump =
up the =A0<BR> &gt; size of the field to 32 bits so that it aligns with =
rfc-4893.<BR> &gt; <BR> &gt; - section 1, 3'rd paragraph. =A0I'm =
paraphrasing what you are saying =A0<BR> &gt; here, but when you speak =
of the risk of some domains arbitrarily =A0<BR> &gt; using high priority =
values, hence the need for domain/sub-domain =A0<BR> &gt; identifiers, =
it seems to me that you are speaking of apples and =A0<BR> &gt; oranges. =
=A0The former is really a function of authorization and =A0<BR> &gt; =
authentication, while the latter seems like an easier approach to =A0<BR> =
&gt; accomplish access control lists (ie, domains versus source net =
=A0<BR> &gt; prefixes).<BR> &gt; <BR> &gt; And this brings up another =
point. =A0Would you want to accomplish some =A0<BR> &gt; (maybe all?) of =
this work in the form of an extension to X.509v3 that =A0<BR> &gt; would =
include the identifiers defined in this draft?<BR> &gt; <BR> &gt; - is =
it your intention to use this domain ID element only in =A0<BR> &gt; =
conjunction with rfc-3181? =A0Or could you envision it being applied to =
=A0<BR> &gt; draft-ietf-tsvwg-emergency-rsvp-02? =A0If yes, you'll need =
to broaden =A0<BR> &gt; some of the text in the draft so that it can be =
applied to more than =A0<BR> &gt; one policy element. =A0This *may* also =
complicate things with respect =A0<BR> &gt; to Error codes.<BR> &gt; =
<BR> &gt; - Section 4. =A0You may want to give some thought to adding or =
changing =A0<BR> &gt; the structures of the existing fields into a =
series of TLVs so that =A0<BR> &gt; you have some additional flexibility =
in adding granularity to sub- <BR> &gt; domains and possibly =
domains.<BR> &gt; <BR> &gt; - page 5 (top). =A0When you say that a =
domain and subdomain MAY be =A0<BR> &gt; paired with a SIP RPH header =
NameSpace, a question arises as to which =A0<BR> &gt; NameSpace? =A0(given=
 the fact that rfc-4412 says that multiple =A0<BR> &gt; different =
NameSpaces may exist in the SIP message.<BR> &gt; <BR> &gt; - Section 5, =
Item 5. =A0if sub-domains are not to be registered, and =A0<BR> &gt; are =
administered locally, how do achieve or help ensure =A0<BR> &gt; =
interoperability if these sub-domains are added by one adminsitrative =
=A0<BR> &gt; domain and examined by another?<BR> &gt; <BR> &gt; - =
Section 5, Item 8. =A0The first sentence says "...entities SHOULD NOT =
=A0<BR> &gt; change Domain-value field". =A0I assume you mean the =
Transit Domain- <BR> &gt; Value, since later on in Item 10 says the =
"Original-Domain-Value MUST =A0<BR> &gt; NOT be changed..."<BR> &gt; =
<BR> &gt; - I would disagree that your document introduces no additional =
=A0<BR> &gt; security considerations above that found in rfc-3181. =A0to =
begin with, =A0<BR> &gt; you'll need to update and clarify what is meant =
by a "trusted zone or =A0<BR> &gt; at least a single zone (no zone =
boundaries are crossed)" as stated in =A0<BR> &gt; the Security =
Considerations of rfc-3181. =A0 Perhaps I've missed =A0<BR> &gt; =
something, but the picture you have painted in this document would =A0<BR>=
 &gt; leave it open to being used across administrative boundaries that =
may =A0<BR> &gt; not have a continual chain of trust.<BR> &gt; <BR> &gt; =
-ken<BR> &gt; <BR> &gt; <BR> &gt; <BR> &gt; <BR> &gt; <BR> =
</TT></FONT></BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>=

--Apple-Mail-1-493737405--





From tsvwg-bounces@ietf.org Mon Jul 23 07:16:24 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ICvth-0006WY-2I; Mon, 23 Jul 2007 07:16:17 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1ICvtf-0006Ox-S1
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 23 Jul 2007 07:16:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ICvtf-0006Lj-78
	for tsvwg@ietf.org; Mon, 23 Jul 2007 07:16:15 -0400
Received: from smtp5.smtp.bt.com ([217.32.164.139])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ICvtd-0002mp-Ju
	for tsvwg@ietf.org; Mon, 23 Jul 2007 07:16:15 -0400
Received: from i2kc08-ukbr.domain1.systemhost.net ([193.113.197.71]) by
	smtp5.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 23 Jul 2007 12:16:12 +0100
Received: from cbibipnt08.iuser.iroot.adidom.com ([147.149.100.81]) by
	i2kc08-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(6.0.3790.1830); Mon, 23 Jul 2007 12:16:11 +0100
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by
	cbibipnt08.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a
	P0803.399); id 1185189370584; Mon, 23 Jul 2007 12:16:10 +0100
Received: from mut.jungle.bt.co.uk ([10.86.0.203])
	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id
	l6NBFv9g008051; Mon, 23 Jul 2007 12:16:08 +0100
Message-Id: <5.2.1.1.2.20070721102131.051439c0@pop3.jungle.bt.co.uk>
X-Sender: rbriscoe@pop3.jungle.bt.co.uk
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Sun, 22 Jul 2007 20:05:11 +0100
To: mallman@icir.org, "FLOYD, Sally" <floyd@acm.org>
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: -0.4 () ALL_TRUSTED,DATE_IN_PAST_12_24
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 23 Jul 2007 11:16:11.0996 (UTC)
	FILETIME=[E05689C0:01C7CD1A]
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0
Cc: tsvwg IETF list <tsvwg@ietf.org>
Subject: [Tsvwg] terminology issues in draft-floyd-tsvwg-besteffort
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Mark, Sally,

Before I went off-list for a holiday over the last couple of weeks, I said 
I generally agreed with <draft-floyd-tsvwg-besteffort-00.txt>
but I had issues with some choices of terminology. Can I ask you to 
consider the following changes to help the debate be more precise.
But, before I start, I just want to emphasise that I agree that it is 
important for people to understand that:
- ECN is not as simple as drop
- policing bulk congestion is not as simple as no policing at all and
- measuring bulk congestion for border SLAs is not as simple as not having 
border SLAs.
Or more succinctly: enforcing fairness is not as simple as not enforcing 
fairness (which is pretty obvious).

1/ Simple?

The term 'Simple Best Effort' contains a value judgement about simplicity.

Many ISPs already limit their heavy users using various metrics: Volume 
caps, volume pricing, deep packet inspection (=infering an app implies 
heavy usage), or vaguely worded acceptable use policies tied to various 
forms of monitoring that allow them to issue email warnings, reduce 
priority and/or issue disconnection notices.

By saying that 'Simple BE' is the dominant traffic class in the current 
Internet, you are either discounting all this policing as "not really 
policing" or as "not really complex", or you are implying most ISPs don't 
do any of this or most ISPs aren't planning to do more of this.

What we're trying to do is provide the simplest possible principled and 
effective policing metric that is application-neutral and user-neutral; as 
an alternative to all the kludges being introduced that are complex and/or 
too blunt and/or non-neutral. It's most disheartening to be accused of 
making the world more complex, when we believe we're making it simpler than 
it would otherwise be.

The best way to avoid that value judgement altogether is to just say 
"non-policed" or "unlimited", which is what you actually mean. And it would 
be best not to claim (without evidence) that ISPs who don't do any limiting 
are still predominant.

2/ BE?

This resource allocation debate is not about policing solely BE scheduled 
traffic. It could just as easily be about policing AF (say). The core issue 
that concerns you is whether ECN has to be turned on or not, so the most 
precise term is surely "non-ECN".

Points 1/ & 2/ summarised: Something like "Unlimited Non-ECN" would be more 
precise and preferable to 'Simple BE'.

---
I also have three strong disagreements that might be just terminology, or 
might be misunderstandings of what we're proposing. All three are in areas 
where we have deliberately wanted to allow vendors and ISPs to come up with 
a range of solutions, which might explain your confusion. But it would be 
fairer on our proposal if it was judged on the set of these 3 choices that 
is both the simplest and still fully effective. The choices you have chosen 
to hilite are the ones we specifically do not recommend - the most complex 
and/or least acceptable.

It's tough on us to be accused of adding complexity when what we'd 
recommend is actually as pretty d@mn simple as enforcing fairness can get.

3/ User pricing: Flat monthly (in our simplest effective proposal).

Please don't imply we're advocating user congestion pricing, given the 
whole reason we brought re-ECN to the IETF back in 2005 was because we 
found a way to limit congestion without constraining how operators price 
their services to their customers. Specifically, re-ECN is designed to work 
with flat monthly pricing.

4/ User policing: Bulk per-customer (in our simplest effective proposal).

Please don't imply that we're advocating per-flow policing. Admittedly we 
have always shown how you could do either per-flow or per-user. Before 
Oct-06 when I wrote that I-D on dismantling flow rate fairness, the 
community wanted to be able to police flow rates, so we wanted to show we 
could. But we neither require it nor recommend it. Our per-user policing 
makes per-flow policing redundant (but it's still there if an IPS wants it).

For the avoidance of doubt, "Bulk per-customer" policing means policing all 
traffic crossing the customer's sending access interface using a bulk token 
bucket to regulate the bit rate of congestion marked packets to all 
destinations together.

5/ Economic infrastructure: Simple pair-wise relationships (in our simplest 
proposal)

Please don't imply we're making economic infrastructure more complex. All 
network layer relationships would still be between directly connected 
neighbours (pairwise).

Currently many border contracts between privately connected ISPs or between 
ISPs and a peering exchange include an element of usage charging (as well 
as interface capacity pricing). Whether based on volume, on some notion of 
peak demand, or on a hybrid. We propose adding a metric (congestion volume) 
that is only slightly less simple than monthly byte-volume.

However, congestion volume is much more effective, as it can be used to 
make networks precisely accountable for the costs they cause in other 
networks (unlike a volume metric, which depresses usage even when the 
capacity is there for it).

So most of the inter-domain contracts that currently include an element of 
usage might switch to using congestion volume. And those that don't include 
any form of usage measurements in their contracts might stick that way. 
That doesn't make any contracts any more complex.


Bob


____________________________________________________________________________
Bob Briscoe, <bob.briscoe@bt.com>      Networks Research Centre, BT Research
B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 645196  







From tsvwg-bounces@ietf.org Mon Jul 23 09:00:46 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ICxWk-0001pz-M4; Mon, 23 Jul 2007 09:00:42 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1ICxWk-0001ps-6L
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 23 Jul 2007 09:00:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ICxWj-0001pj-SP
	for tsvwg@ietf.org; Mon, 23 Jul 2007 09:00:41 -0400
Received: from smtp5.smtp.bt.com ([217.32.164.139])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ICxWh-0005hD-VA
	for tsvwg@ietf.org; Mon, 23 Jul 2007 09:00:41 -0400
Received: from i2kc08-ukbr.domain1.systemhost.net ([193.113.197.71]) by
	smtp5.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 23 Jul 2007 14:00:15 +0100
Received: from cbibipnt08.iuser.iroot.adidom.com ([147.149.100.81]) by
	i2kc08-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(6.0.3790.1830); Mon, 23 Jul 2007 14:00:14 +0100
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by
	cbibipnt08.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a
	P0803.399); id 1185195612394; Mon, 23 Jul 2007 14:00:12 +0100
Received: from mut.jungle.bt.co.uk ([10.86.0.93])
	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id
	l6ND01ja009067; Mon, 23 Jul 2007 14:00:12 +0100
Message-Id: <5.2.1.1.2.20070723135052.05656e40@pop3.jungle.bt.co.uk>
X-Sender: rbriscoe@pop3.jungle.bt.co.uk
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Mon, 23 Jul 2007 13:58:12 +0100
To: "James M. Polk" <jmpolk@cisco.com>
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
Subject: Re: [Tsvwg] FINAL Agenda for Chicago
In-Reply-To: <XFE-SJC-2111o8yfogk000000fa@xfe-sjc-211.amer.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: -1.36 () ALL_TRUSTED
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 23 Jul 2007 13:00:14.0444 (UTC)
	FILETIME=[692082C0:01C7CD29]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

James,

At 19:18 16/07/2007, James M. Polk wrote:
>SPEAKERS!!!  Presentations will be due on Wednesday July 25th at noon 
>local time, in order to make it on the server.  Changes after that time 
>may not be received.  Speakers without presentations... well, they don't speak.

My 3 presentations are all available in ppt & pdf from:
<http://www.cs.ucl.ac.uk/staff/B.Briscoe/present.html#0707rateFairDis>
(latest in the agenda at the top)

You shouldn't need Bruce's one that is also there, as Bruce already sent 
that to Magnus.


Bob


____________________________________________________________________________
Bob Briscoe, <bob.briscoe@bt.com>      Networks Research Centre, BT Research
B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 645196 







From tsvwg-bounces@ietf.org Mon Jul 23 12:20:13 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID0dk-0004Tp-QX; Mon, 23 Jul 2007 12:20:08 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1ID0dj-0004Tg-37
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 23 Jul 2007 12:20:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID0di-0004TY-Pl; Mon, 23 Jul 2007 12:20:06 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ID0di-0002X1-7n; Mon, 23 Jul 2007 12:20:06 -0400
Received: from dhcp-1398.ietf69.org ([130.129.19.152]:54073)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1ID0dh-0003Mo-E3; Mon, 23 Jul 2007 17:20:05 +0100
In-Reply-To: <E1I7psX-0004oc-Bu@stiedprstage1.ietf.org>
References: <E1I7psX-0004oc-Bu@stiedprstage1.ietf.org>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <96AB315B-327A-49AF-83CA-A4012F6A5153@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [Tsvwg] I-D Action:draft-ietf-tsvwg-udp-guidelines-02.txt 
Date: Mon, 23 Jul 2007 11:20:06 -0500
To: Lars Eggert <lars.eggert@nokia.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: tsvwg WG <tsvwg@ietf.org>, MMUSIC WG <mmusic@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

On 9 Jul 2007, at 04:50, 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 Transport Area Working Group  
> Working Group of the IETF.
>
>
>         Title           : UDP Usage Guidelines for Application  
> Designers
>         Author(s)       : L. Eggert, G. Fairhurst
>         Filename        : draft-ietf-tsvwg-udp-guidelines-02.txt
>         Pages           : 15
>         Date            : 2007-07-09
>
> The User Datagram Protocol (UDP) provides a minimal, message-passing
> transport that has no inherent congestion control mechanisms.
> Because congestion control is critical to the stable operation of the
> Internet, applications and upper-layer protocols that choose to use
> UDP as an Internet transport must employ mechanisms to prevent
> congestion collapse and establish some degree of fairness with
> concurrent traffic.  This document provides guidelines on the use of
> UDP for the designers of such applications and upper-layer protocols
> that cover congestion-control and other topics, including message
> sizes, reliability, checksums and middlebox traversal.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-udp- 
> guidelines-02.txt

Section 3.5 states:

    Applications MAY in addition send periodic keep-alive messages to
    attempt to refresh middlebox state.  Unfortunately, no common  
timeout
    has been specified for per-flow UDP state for arbitrary middleboxes.
    For NATs, [RFC4787] requires a state timeout of 2 minutes or longer,
    and it is likely that other types of middleboxes use timeouts of
    similar timescales.  Consequently, if applications choose to send
    periodic keep-alives, they SHOULD NOT send them more frequently than
    once every two minutes.  (Not that some deployed middleboxes use a
    shorter timeout value than 2 minutes, violating [RFC4787].)

which is fine, except that draft-ietf-mmusic-ice-17 suggests a 15  
second keep alive interval by default. Can we align these?

-- 
Colin Perkins
http://csperkins.org/







From tsvwg-bounces@ietf.org Mon Jul 23 12:55:59 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID1CN-0000xf-P1; Mon, 23 Jul 2007 12:55:55 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1ID1CM-0000sd-EI
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 23 Jul 2007 12:55:54 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ID1CM-0000sU-2g
	for tsvwg@ietf.org; Mon, 23 Jul 2007 12:55:54 -0400
Received: from exprod7og58.obsmtp.com ([64.18.2.171])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ID1CL-0002Oz-76
	for tsvwg@ietf.org; Mon, 23 Jul 2007 12:55:53 -0400
Received: from source ([67.96.16.12]) (using TLSv1) by exprod7ob58.obsmtp.com
	([64.18.6.12]) with SMTP; Mon, 23 Jul 2007 09:55:51 PDT
Received: from ETSMSG-CINAV01.etsmsg.org ([65.90.82.49]) by
	naout-cinexs02.nasmtpout.emrsn.com with Microsoft
	SMTPSVC(6.0.3790.3959); Mon, 23 Jul 2007 13:07:27 -0400
Received: from etsmsg-cinexs04.etsmsg.org ([65.90.82.49]) by
	ETSMSG-CINAV01.etsmsg.org with InterScan Message Security Suite;
	Mon, 23 Jul 2007 12:55:50 -0400
Received: from ETSMSG-CINEXS01.etsmsg.org ([65.90.82.81]) by
	etsmsg-cinexs04.etsmsg.org with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 23 Jul 2007 12:55:50 -0400
Received: from ant.artesyncp.com ([65.90.82.49]) by ETSMSG-CINEXS01.etsmsg.org
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 23 Jul 2007 12:55:49 -0400
Received: from stephane by ant.artesyncp.com with local (Exim 4.67)
	(envelope-from <stephane@artesyncp.com>) id 1ID1CH-0006UU-5F
	for tsvwg@ietf.org; Mon, 23 Jul 2007 17:55:49 +0100
Date: Mon, 23 Jul 2007 17:55:49 +0100
From: Stephane Chazelas <stephane@artesyncp.com>
To: tsvwg <tsvwg@ietf.org>
Subject: Re: [Tsvwg] comments and questions on draft-ietf-tsvwg-sctpsocket-15
Message-ID: <20070723165549.GF27625@artesyncp.com>
References: <20070711163947.GD6418@artesyncp.com>
	<20070720095149.GM9304@artesyncp.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070720095149.GM9304@artesyncp.com>
User-Agent: mutt-ng/devel-r562 (Linux)
X-OriginalArrivalTime: 23 Jul 2007 16:55:50.0105 (UTC)
	FILETIME=[52A33490:01C7CD4A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

On Fri, Jul 20, 2007 at 10:51:49AM +0100, Stephane Chazelas wrote:
[...]
> I've another concern about this draft on another point of
> detail, this time about the SCTP_DEFAULT_SEND_PARAM in 1-to-many
> style.
[...]

Hi list,

I'm afraid I have some more questions about this document :).

about sctp_assoc_t.

At first sight, sctp_assoc_t seems to be an opaque type with no
indication of it being numerical or not, then there are some
inconsistencies in the document about its type:

Sometimes, we talk of an "sctp_assoc_t structure" (is it a C
struct?), sometimes it can take a value of 0 or zero (is it a
numerical type?), sometimes a value of '0' (is it a char?).

So my understanding is that the intent was to have a sort of
integer type assoc id, and that the value 0 is reserved and
shouldn't be assigned to any association.

Would it be possible to have it worded a bit more clearly in the
document?

Also, if 0 is a reserved value, it would be nice if it was
specified how that value should be handled for every call that
involves a sctp_assoc_t.

Especially, what about the SCTP_SNDRCV data option in sendmsg()?

It's not very clear what the sinfo_associd field is for. There
are several statements that a user should set that field to the
assoc id of the association he wants to shutdown/abort along
with the SCTP_EOF and SCTP_ABORT flags. Other than that, for
normal operation, it's said that the field should contain the
assoc_id returned in an ASSOC_CHANGE notification without really
explaining what for. But what if a user (in 1-to-many) wants to
send a msg to a host we are not associated to yet and for
instance using stream id 2?  Does he have to do a connect()
first? Or a setsockopt(SCTP_DEFAULT_SEND_PARAM) with
sinfo_associd == 0 and do a sendmsg() without SCTP_SNDRCV?

If both a destination address and an assoc_id (in a sctp_sndrcv
structure) are provided, how should a sctp stack look up the
association? What takes precedence?

In the description of the msghdr structure:
  1187     In the msghdr structure, the usage of msg_name has been discussed in
  1188     previous sections (see Section 3.1.3 and Section 4.1.8).

I can see nothing about msg_name in section 3.1.3. There's a
similar wrong link in section 4.1.8. I suspect 3.1.4 was meant
instead.

Section 3.1.4 says what to do when there is no association
already for the given address, but doesn't say what to do if
there is one or if there are several. For instance, if one does
a sendmsg with msg_name containing address X, with a SCTP_SNDRCV
with a sinfo_associd being zero, and a SCTP_EOF in the
sinfo_flags, should we shutdown every association to address X,
or just the first, or just the first one that is not in the
ESTABLISHED state. Same for just sending data. And what if a
non-zero assoc_id is provided...

Also, why doesn't sctp_sendmsg() take an assoc_id argument?

Also, could anyone please help me understand this statement in
section 7:

>  All options that support specific settings on an association by
>  filling in either an association id variable or a sockaddr_storage
>  SHOULD also support setting of the same value for the entire endpoint
>  (i.e. future associations).  To accomplish this the following logic
>  is used when setting one of these options:
>
>  a) If an address is specified via a sockaddr_storage that is included
>     in the structure, the address is used to lookup the association
>     and the settings are applied to the specific address (if
>     appropriate) or to the entire association.
>  b) If an association identification is filled in but not a
>     sockaddr_storage (if present), the association is found using the
>     association identification and the settings should be applied to
>     the entire association (since a specific address is not
>     specified).  Note this also applies to options that hold an
>     association identification in their structure but do not have a
>     sockaddr_storage field.
>  c) If neither the sockaddr_storage or association identification is
>     set, i.e. the sockaddr_storage is set to all 0's (INADDR_ANY) and
>     the association identification is 0, the settings are a default
>     and to be applied to the endpoint (all future associations).

I can't think of any option to which it applies. Does anyone
have an example?

I've spotted a few typos in the document:

   353	   setup an association implicitly.  It cannot be used to send data to
   354	   an established association as the association ID cannot be specified.
   355	
   356	   Once as association ID is assigned to an SCTP association, that ID

typo: "once as"


  2468	7.  Socket Options
  2469	
  2470	   The following sub-section describes various SCTP level socket options
  2471	   that are common to both styles.  SCTP associations can be multi-
  2472	   homed.  Therefore, certain option parameters include a
  2473	   sockaddr_storage structure to select which peer address the option
  2474	   should be applied to.
  2475	
  2476	   For the one-to-many style sockets, an sctp_assoc_t structure
  2477	   (association ID) is used to identify the the association instance

typo: "the the"


  2650	   This information may be examined for either the endpoint or a
  2651	   specific association.  To examine a endpoints default parameters the
  2652	   association id (sasoc_assoc_id) should must be set to the value '0'.

typo: "should must"

Best regards,
Stephane





From tsvwg-bounces@ietf.org Tue Jul 24 05:48:09 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDGzp-0005ZO-Kl; Tue, 24 Jul 2007 05:48:01 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IDGzo-0005ZH-3L
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 24 Jul 2007 05:48:00 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDGzn-0005Z9-ON
	for tsvwg@ietf.org; Tue, 24 Jul 2007 05:47:59 -0400
Received: from exprod7og51.obsmtp.com ([64.18.2.157])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDGzm-00017n-Ui
	for tsvwg@ietf.org; Tue, 24 Jul 2007 05:47:59 -0400
Received: from source ([67.96.16.12]) (using TLSv1) by exprod7ob51.obsmtp.com
	([64.18.6.12]) with SMTP; Tue, 24 Jul 2007 02:47:57 PDT
Received: from ETSMSG-CINAV06.etsmsg.org ([65.90.82.49]) by
	naout-cinexs02.nasmtpout.emrsn.com with Microsoft
	SMTPSVC(6.0.3790.3959); Tue, 24 Jul 2007 05:59:34 -0400
Received: from etsmsg-cinexs03.etsmsg.org ([65.90.82.49]) by
	ETSMSG-CINAV06.etsmsg.org with InterScan Message Security Suite;
	Tue, 24 Jul 2007 05:47:56 -0400
Received: from ETSMSG-CINEXS01.etsmsg.org ([65.90.82.81]) by
	etsmsg-cinexs03.etsmsg.org with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 24 Jul 2007 05:47:56 -0400
Received: from ant.artesyncp.com ([65.90.82.49]) by ETSMSG-CINEXS01.etsmsg.org
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 24 Jul 2007 05:47:55 -0400
Received: from stephane by ant.artesyncp.com with local (Exim 4.67)
	(envelope-from <stephane@artesyncp.com>)
	id 1IDGzi-00009q-Qp; Tue, 24 Jul 2007 10:47:54 +0100
Date: Tue, 24 Jul 2007 10:47:54 +0100
From: Stephane Chazelas <stephane@artesyncp.com>
To: Vlad Yasevich <vladislav.yasevich@hp.com>
Subject: Re: [Tsvwg] comments and questions on draft-ietf-tsvwg-sctpsocket-15
Message-ID: <20070724094754.GL27625@artesyncp.com>
References: <20070711163947.GD6418@artesyncp.com> <46A0B9A0.3010400@hp.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <46A0B9A0.3010400@hp.com>
User-Agent: mutt-ng/devel-r562 (Linux)
X-OriginalArrivalTime: 24 Jul 2007 09:47:55.0838 (UTC)
	FILETIME=[B5FEB5E0:01C7CDD7]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Cc: tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

On Fri, Jul 20, 2007 at 09:33:20AM -0400, Vlad Yasevich wrote:
[...]
> > 3.1.5: (knitpicking)
> >   > To gracefully shutdown a specific association represented by the one-
> >   > to-many style socket, an application should use the sendmsg() call,
> >   > and including the SCTP_EOF flag.  A user may optionally terminate an
> >   > association non-gracefully by sending with the SCTP_ABORT flag and
> >   > possibly passing a user specified abort code in the data field.  Both
> > 
> >   What "data field"? 5.2.2 indicates that that's msg_iov, but that field
> >   is described as "scatter/gather array", not "data".
> 
> Would the following be better?
> 
>     A user may optionally terminate an association non-gracefully by sending with
>     the SCTP_ABORT flag and possibly providing a user specified abort code as
>     data.

Hi Vlad,

thank you for taking the time to respond.

In this occurrence, given that it mentions sendmsg()
explicitely, I would rather say "in the msgiov field".

[...]
> > 6.1:
> >   > Note, if an application calls a send function with no user data and
> >   > no ancillary data the SCTP implementation should reject the request
> >   > with an appropriate error message.  An implementation is NOT allowed
> >   > to send a Data chunk with no user data RFC2960 [RFC2960].
> > 
> >   OK, but then what about a sendmsg() with ancillary data and no user
> >   data?
> > 
> >   The draft suggests that we may send a SCTP_SNDRCV structure with
> >   SCTP_EOF and no data if we want to close a 1-to-many association.
> > 
> >   It suggests as well that we may be able to use SCTP_ABORT with no data
> >   if we want to abort an association without giving a reason.
> > 
> >   But what about the other possible usages of SCTP_SNDRCV and SCTP_INIT?
> 
> Those would be invalid.

That's arguable. As the draft is currently worded, it is valid
as only no-control *and* no-data is invalid.

It's true that a user can use a setsockopt followed by a connect
to initiate an association with specific init parameters, but if
he wants to use those parameters only for a specific address,
allowing to establish an association with an empty sendmsg()
with control data would be useful (otherwise, he'd need to do
another setsockopt to revert to the previous parameters).

Also given that we can close an association with a sendmsg(), it
would make sense to be able to initiate it with a sendmsg() as
well.

But if we allow a sendmsg with no-data to initiate an
association with specific init parameters, I don't think it
makes sense to forbid a sendmsg() without control-data to allow
to establish an association with the default init parameters.

[...]
> >   Also, what about a sendmsg() with SCTP_ABORT (or SCTP_EOF and no data)
> >   to a destination to which we're not associated yet? Should it
> >   establish and then close an association?
> 
> No.
[...]

I'd agree with you. But then, the draft would need to be
updated. As it's worded today, it's not clear.

There's also the case of SCTP_EOF *with* user data that is not
clearly covered. One may want to use that to send datagrams and
make sure a new association is created for every send message.
It's not clear whether the draft allows that at the moment.

Best regards,
Stephane





From tsvwg-bounces@ietf.org Tue Jul 24 13:01:26 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDNlD-0002NQ-Jh; Tue, 24 Jul 2007 13:01:23 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IDNlD-0002NE-61
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 24 Jul 2007 13:01:23 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDNlC-0002N0-Oh
	for tsvwg@ietf.org; Tue, 24 Jul 2007 13:01:22 -0400
Received: from hiltonsmtp.worldspice.net ([216.37.94.58])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDNlC-0000LI-2R
	for tsvwg@ietf.org; Tue, 24 Jul 2007 13:01:22 -0400
Received: (qmail 12677 invoked by uid 0); 24 Jul 2007 16:53:46 -0000
Received: by simscan 1.2.0 ppid: 12662, pid: 12672, t: 1.0360s
	scanners: clamav: 0.90.2/m: spam: 3.1.8
X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on
	hiltonsmtp.worldspice.net
X-Spam-Level: ****
X-Spam-Status: No, score=4.2 required=6.5 tests=ALL_TRUSTED,BAYES_99
	autolearn=disabled version=3.2.1
Received: from unknown (HELO ?172.28.169.190?) (sallyfloyd@67.97.210.2)
	by hiltonsmtp.worldspice.net with ESMTPA; 24 Jul 2007 16:53:44 -0000
In-Reply-To: <5.2.1.1.2.20070721102131.051439c0@pop3.jungle.bt.co.uk>
References: <5.2.1.1.2.20070721102131.051439c0@pop3.jungle.bt.co.uk>
Mime-Version: 1.0 (Apple Message framework v624)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <c73ebd49050a446fbab11646dc6b750a@mac.com>
Content-Transfer-Encoding: 7bit
From: Sally Floyd <sallyfloyd@mac.com>
Date: Tue, 24 Jul 2007 10:01:17 -0700
To: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
X-Mailer: Apple Mail (2.624)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Cc: tsvwg IETF list <tsvwg@ietf.org>, Mark Allman <mallman@icir.org>
Subject: [Tsvwg] Re: terminology issues in draft-floyd-tsvwg-besteffort -
	"simple best effort"
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Bob -

I am answering the email one item at a time, as I find time.

> 1/ Simple?
>
> The term 'Simple Best Effort' contains a value judgement about 
> simplicity.
>
> Many ISPs already limit their heavy users using various metrics: 
> Volume caps, volume pricing, deep packet inspection (=infering an app 
> implies heavy usage), or vaguely worded acceptable use policies tied 
> to various forms of monitoring that allow them to issue email 
> warnings, reduce priority and/or issue disconnection notices.
>
> By saying that 'Simple BE' is the dominant traffic class in the 
> current Internet, you are either discounting all this policing as "not 
> really policing" or as "not really complex", or you are implying most 
> ISPs don't do any of this or most ISPs aren't planning to do more of 
> this.
>
> What we're trying to do is provide the simplest possible principled 
> and effective policing metric that is application-neutral and 
> user-neutral; as an alternative to all the kludges being introduced 
> that are complex and/or too blunt and/or non-neutral. It's most 
> disheartening to be accused of making the world more complex, when we 
> believe we're making it simpler than it would otherwise be.
>
> The best way to avoid that value judgement altogether is to just say 
> "non-policed" or "unlimited", which is what you actually mean. And it 
> would be best not to claim (without evidence) that ISPs who don't do 
> any limiting are still predominant.

We defined the phrase "simple best effort" as follows:
In the abstract:
    "This document presents some observations on "simple best-effort"
     traffic, defined loosely for the purposes of this document as
     Internet traffic that is not covered by Quality of Service
     mechanisms, congestion-based pricing, or the like."

And later in the Introduction:
    "For the purposes of this document, we define "simple
    best-effort traffic" as traffic that does not *rely* on the
    *differential treatment* of flows either in routers or in policers,
    enforcers, or other middleboxes along the path."

I am happy to clarify the definition of "simple best effort" as
used in our draft to say that it can include a wide range of things
done by ISPs, including volume caps, volume pricing, deep packet
inspection, vaguely worded acceptable use policies tied to various
forms of monitoring, and other things done by ISPs.  But not including
traffic that uses diffserv, intserv, congestion-based pricing,
cost-based fairness mechanisms, *requirements* for ECN enabled at
congested routers coupled with policers at the two ends of the
connection, etc.

I will also try to clarify the definition to make it clear that,
for the purposes of this document, we are using the phrase "simple
best-effort traffic" to mean "best-effort traffic like most of the
traffic in the current Internet today".  We *don't* mean "non-policed",
or "unlimited".

We are not trying to imply that moving packets from point A to point
B is simple, with or without volume caps, volume pricing, deep
packet inspection, vaguely worded acceptable use policies tied to
various forms of monitoring.

> 2/ BE?
>
> This resource allocation debate is not about policing solely BE 
> scheduled traffic. It could just as easily be about policing AF (say). 
> The core issue that concerns you is whether ECN has to be turned on or 
> not, so the most precise term is surely "non-ECN".

I understand that the resource allocation debate is not about
policing solely BE scheduled traffic.  As I said in the introduction
to this draft, "This document does not attempt to be a rebuttal to
[B07], or to answer any or all of the issues raised in [B07]".  This
document is specifically about best-effort traffic, as it tries to
make clear.

"Non-ECN" was not what I had in mind.  I will clarify the definition
of "simple best effort traffic" to say that it can include ECN.
And that traffic that does not quality as "simple best-effort
traffic", for the definition used in this draft, might or might not
use ECN (e.g, diffserv traffic).

But I am not going to try for an exhaustive definition of "simple
best-effort traffic".  I think I can make the points in the draft,
for most readers, without that.

> Points 1/ & 2/ summarised: Something like "Unlimited Non-ECN" would be 
> more precise and preferable to 'Simple BE'.

As I explained above, that is not what I had in mind.
As I said above, I will clarify our definition of
simple best-effort traffic.

- Sally
http://www.icir.org/floyd/
http://tools.ietf.org/html/draft-floyd-tsvwg-besteffort-00






From tsvwg-bounces@ietf.org Tue Jul 24 13:16:59 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDO0I-00010g-FF; Tue, 24 Jul 2007 13:16:58 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IDO0G-0000xz-Ln
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 24 Jul 2007 13:16:56 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDO0G-0000vU-59
	for tsvwg@ietf.org; Tue, 24 Jul 2007 13:16:56 -0400
Received: from hiltonsmtp.worldspice.net ([216.37.94.58])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDO0F-000120-PC
	for tsvwg@ietf.org; Tue, 24 Jul 2007 13:16:56 -0400
Received: (qmail 13974 invoked by uid 0); 24 Jul 2007 17:09:19 -0000
Received: by simscan 1.2.0 ppid: 13962, pid: 13970, t: 0.7565s
	scanners: clamav: 0.90.2/m: spam: 3.1.8
X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on
	hiltonsmtp.worldspice.net
X-Spam-Level: ****
X-Spam-Status: No, score=4.2 required=6.5 tests=ALL_TRUSTED,BAYES_99
	autolearn=disabled version=3.2.1
Received: from unknown (HELO ?172.28.169.190?) (sallyfloyd@67.97.210.2)
	by hiltonsmtp.worldspice.net with ESMTPA; 24 Jul 2007 17:09:19 -0000
In-Reply-To: <5.2.1.1.2.20070721102131.051439c0@pop3.jungle.bt.co.uk>
References: <5.2.1.1.2.20070721102131.051439c0@pop3.jungle.bt.co.uk>
Mime-Version: 1.0 (Apple Message framework v624)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <5a31970f1159b2e836c378b0e9c99e4c@mac.com>
Content-Transfer-Encoding: 7bit
From: Sally Floyd <sallyfloyd@mac.com>
Date: Tue, 24 Jul 2007 10:16:51 -0700
To: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
X-Mailer: Apple Mail (2.624)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: tsvwg IETF list <tsvwg@ietf.org>, Mark Allman <mallman@icir.org>
Subject: [Tsvwg] Re: terminology issues in draft-floyd-tsvwg-besteffort -
	flat monthly pricing
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

> 3/ User pricing: Flat monthly (in our simplest effective proposal).
>
> Please don't imply we're advocating user congestion pricing, given the 
> whole reason we brought re-ECN to the IETF back in 2005 was because we 
> found a way to limit congestion without constraining how operators 
> price their services to their customers. Specifically, re-ECN is 
> designed to work with flat monthly pricing.

This draft is not about re-ECN.  It is about the usefulness of
"simple best-effort traffic", and the usefulness of flow-rate fairness
for simple best-effort traffic.

This draft is not about the presence or absence of flat monthly
pricing for users.  One could have flat monthly pricing with no
other limitations, one could have flat monthly pricing with volume
limits, or one could have flat monthly pricing with some form of
"you get what you pay for".  The first two forms don't result in
"rich" users getting all of the bandwidth in times of high congestion
(e.g., after the earthquake).  The third form easily could.  E.g.,
if all of the traffic was "you get what you pay for", even with
flat monthly fees, then it could be really expensive to send packets
in the time interval after the earthquake, or some other 
highly-congested
period, and only the rich would be able to send packets.  I would
be opposed to setting such a "you get what you pay for" goal as the
overriding goal for the global Internet, with or without flat monthly
fees.

- Sally
http://www.icir.org/floyd/






From tsvwg-bounces@ietf.org Tue Jul 24 13:29:23 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDOCD-0004je-O7; Tue, 24 Jul 2007 13:29:17 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IDOCC-0004jW-9T
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 24 Jul 2007 13:29:16 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDOCB-0004jO-Uo
	for tsvwg@ietf.org; Tue, 24 Jul 2007 13:29:15 -0400
Received: from hiltonsmtp.worldspice.net ([216.37.94.58])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDOCB-0001cf-GV
	for tsvwg@ietf.org; Tue, 24 Jul 2007 13:29:15 -0400
Received: (qmail 14758 invoked by uid 0); 24 Jul 2007 17:21:39 -0000
Received: by simscan 1.2.0 ppid: 14751, pid: 14754, t: 0.7281s
	scanners: clamav: 0.90.2/m: spam: 3.1.8
X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on
	hiltonsmtp.worldspice.net
X-Spam-Level: ****
X-Spam-Status: No, score=4.2 required=6.5 tests=ALL_TRUSTED,BAYES_99
	autolearn=disabled version=3.2.1
Received: from unknown (HELO ?172.28.169.190?) (sallyfloyd@67.97.210.2)
	by hiltonsmtp.worldspice.net with ESMTPA; 24 Jul 2007 17:21:38 -0000
In-Reply-To: <5.2.1.1.2.20070721102131.051439c0@pop3.jungle.bt.co.uk>
References: <5.2.1.1.2.20070721102131.051439c0@pop3.jungle.bt.co.uk>
Mime-Version: 1.0 (Apple Message framework v624)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <80cbbf6f29fe311e534c72629df8b466@mac.com>
Content-Transfer-Encoding: 7bit
From: Sally Floyd <sallyfloyd@mac.com>
Date: Tue, 24 Jul 2007 10:29:11 -0700
To: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
X-Mailer: Apple Mail (2.624)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: tsvwg IETF list <tsvwg@ietf.org>, Mark Allman <mallman@icir.org>
Subject: [Tsvwg] Re: terminology issues in draft-floyd-tsvwg-besteffort -
	per flow or per user
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Bob -

> 4/ User policing: Bulk per-customer (in our simplest effective 
> proposal).
>
> Please don't imply that we're advocating per-flow policing. Admittedly 
> we have always shown how you could do either per-flow or per-user. 
> Before Oct-06 when I wrote that I-D on dismantling flow rate fairness, 
> the community wanted to be able to police flow rates, so we wanted to 
> show we could. But we neither require it nor recommend it. Our 
> per-user policing makes per-flow policing redundant (but it's still 
> there if an IPS wants it).
>
> For the avoidance of doubt, "Bulk per-customer" policing means 
> policing all traffic crossing the customer's sending access interface 
> using a bulk token bucket to regulate the bit rate of congestion 
> marked packets to all destinations together.

If you let me know where the draft implied that you were
advocating per-flow policing, I would be happy to correct it.
(I looked, but I didn't see it.)

The draft is not intended to be about any specific proposed mechanism.
It is simply in support of "simple best-effort traffic", and in support 
of
flow-based fairness for simple best-effort traffic.

- Sally
http://www.icir.org/floyd/






From tsvwg-bounces@ietf.org Tue Jul 24 13:43:44 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDOQA-00051h-Vv; Tue, 24 Jul 2007 13:43:42 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IDOQ8-0004zQ-VA
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 24 Jul 2007 13:43:40 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDOQ8-0004zD-In
	for tsvwg@ietf.org; Tue, 24 Jul 2007 13:43:40 -0400
Received: from hiltonsmtp.worldspice.net ([216.37.94.58])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDOQ8-000203-3K
	for tsvwg@ietf.org; Tue, 24 Jul 2007 13:43:40 -0400
Received: (qmail 15493 invoked by uid 0); 24 Jul 2007 17:36:04 -0000
Received: by simscan 1.2.0 ppid: 15480, pid: 15489, t: 0.7673s
	scanners: clamav: 0.90.2/m: spam: 3.1.8
X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on
	hiltonsmtp.worldspice.net
X-Spam-Level: ****
X-Spam-Status: No, score=4.2 required=6.5 tests=ALL_TRUSTED,BAYES_99
	autolearn=disabled version=3.2.1
Received: from unknown (HELO ?172.28.169.190?) (sallyfloyd@67.97.210.2)
	by hiltonsmtp.worldspice.net with ESMTPA; 24 Jul 2007 17:36:03 -0000
In-Reply-To: <5.2.1.1.2.20070721102131.051439c0@pop3.jungle.bt.co.uk>
References: <5.2.1.1.2.20070721102131.051439c0@pop3.jungle.bt.co.uk>
Mime-Version: 1.0 (Apple Message framework v624)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <9359d93f7aa2aa2768b04107fa12d5ef@mac.com>
Content-Transfer-Encoding: 7bit
From: Sally Floyd <sallyfloyd@mac.com>
Date: Tue, 24 Jul 2007 10:43:35 -0700
To: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
X-Mailer: Apple Mail (2.624)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: "FLOYD, Sally" <floyd@acm.org>, tsvwg IETF list <tsvwg@ietf.org>,
	mallman@icir.org
Subject: [Tsvwg] Re: terminology issues in draft-floyd-tsvwg-besteffort -
	simple pair-wise relationships
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

> 5/ Economic infrastructure: Simple pair-wise relationships (in our 
> simplest proposal)
>
> Please don't imply we're making economic infrastructure more complex. 
> All network layer relationships would still be between directly 
> connected neighbours (pairwise).
>
> Currently many border contracts between privately connected ISPs or 
> between ISPs and a peering exchange include an element of usage 
> charging (as well as interface capacity pricing). Whether based on 
> volume, on some notion of peak demand, or on a hybrid. We propose 
> adding a metric (congestion volume) that is only slightly less simple 
> than monthly byte-volume.
>
> However, congestion volume is much more effective, as it can be used 
> to make networks precisely accountable for the costs they cause in 
> other networks (unlike a volume metric, which depresses usage even 
> when the capacity is there for it).
>
> So most of the inter-domain contracts that currently include an 
> element of usage might switch to using congestion volume. And those 
> that don't include any form of usage measurements in their contracts 
> might stick that way. That doesn't make any contracts any more 
> complex.

Our draft says the following:

    "The difficulties of deployment for end-to-end intserv or diffserv
    mechanisms are well-known, having in part to do with the difficulties
    of deployment for the economic infrastructure that would be needed
    [B03].  It seems likely that cost-based pricing based on re-ECN could
    also have a difficult deployment path, involving the deployment of
    ECN-marking at routers, policers at both ends of a connection, and a
    complex set of economic relationships [B07]."

I would be happy to clarify it that the set of economic relationships
required for "cost-based pricing based on re-ECN" would be pairwise,
with a metric for congestion volume.

(Note that this sentence is not about all possible forms of re-ECN,
but about "cost-based pricing based on re-ECN".  Our draft is not
about re-ECN - it is simply in support of "simple best-effort
traffic", and in support of flow-based fairness for simple best-effort
traffic.)

- Sally
http://www.icir.org/floyd/






From tsvwg-bounces@ietf.org Tue Jul 24 19:34:37 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDTss-0006lw-Kf; Tue, 24 Jul 2007 19:33:42 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IDTsr-0006lr-20
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 24 Jul 2007 19:33:41 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDTsq-0006lj-Mj
	for tsvwg@ietf.org; Tue, 24 Jul 2007 19:33:40 -0400
Received: from smtpout.mac.com ([17.250.248.184])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDTsq-00015L-8c
	for tsvwg@ietf.org; Tue, 24 Jul 2007 19:33:40 -0400
Received: from mac.com (smtpin06-en2 [10.13.10.151])
	by smtpout.mac.com (Xserve/smtpout14/MantshX 4.0) with ESMTP id
	l6ONXdYA000528; Tue, 24 Jul 2007 16:33:39 -0700 (PDT)
Received: from [130.129.32.125] (dhcp-207d.ietf69.org [130.129.32.125])
	(authenticated bits=0)
	by mac.com (Xserve/smtpin06/MantshX 4.0) with ESMTP id l6ONX8uN026529; 
	Tue, 24 Jul 2007 16:33:20 -0700 (PDT)
In-Reply-To: <XFE-SJC-2111o8yfogk000000fa@xfe-sjc-211.amer.cisco.com>
References: <XFE-SJC-2111o8yfogk000000fa@xfe-sjc-211.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v624)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <5996a98ad940c00ef49b67a944a17555@mac.com>
Content-Transfer-Encoding: 7bit
From: Sally Floyd <sallyfloyd@mac.com>
Subject: Re: [Tsvwg] FINAL Agenda for Chicago
Date: Tue, 24 Jul 2007 16:33:09 -0700
To: "James M. Polk" <jmpolk@cisco.com>
X-Mailer: Apple Mail (2.624)
X-Brightmail-Tracker: AAAAAA==
X-Brightmail-scanned: yes
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Cc: tsvwg <tsvwg@ietf.org>, Mark Allman <mallman@icir.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Our slides for "Comments on the Usefulness of Simple Best-Effort 
Traffic"
are at:

http://www.icir.org/floyd/talks/besteffort-jul07.pdf, .ppt

- Sally
http://www.icir.org/floyd/






From tsvwg-bounces@ietf.org Wed Jul 25 12:23:02 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDjda-0003ZG-Pk; Wed, 25 Jul 2007 12:22:58 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IDjdX-0003Td-44
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 25 Jul 2007 12:22:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDjdV-0003Sd-Va
	for tsvwg@ietf.org; Wed, 25 Jul 2007 12:22:54 -0400
Received: from smtp2.smtp.bt.com ([217.32.164.150])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDjdU-00044I-DY
	for tsvwg@ietf.org; Wed, 25 Jul 2007 12:22:53 -0400
Received: from i2kc08-ukbr.domain1.systemhost.net ([193.113.197.71]) by
	smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 25 Jul 2007 17:22:49 +0100
Received: from cbibipnt08.iuser.iroot.adidom.com ([147.149.100.81]) by
	i2kc08-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 25 Jul 2007 17:22:49 +0100
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by
	cbibipnt08.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a
	P0803.399); id 1185380568679; Wed, 25 Jul 2007 17:22:48 +0100
Received: from mut.jungle.bt.co.uk ([10.86.7.146])
	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id
	l6PGMigH003317; Wed, 25 Jul 2007 17:22:47 +0100
Message-Id: <5.2.1.1.2.20070725170014.042e6d18@pop3.jungle.bt.co.uk>
X-Sender: rbriscoe@pop3.jungle.bt.co.uk
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Wed, 25 Jul 2007 17:22:51 +0100
To: re-ECN unIETF list <re-ecn@ietf.org>
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
Mime-Version: 1.0
Content-Type: text/html; charset="us-ascii"
X-Spam-Score: -0.334 () ALL_TRUSTED,HTML_40_50,HTML_MESSAGE,MIME_HTML_ONLY
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 25 Jul 2007 16:22:49.0412 (UTC)
	FILETIME=[0AE0F040:01C7CED8]
X-Spam-Score: 1.7 (+)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Cc: PCN IETF list <pcn@ietf.org>, Aaron Falk <falk@ISI.EDU>,
	tsvwg IETF list <tsvwg@ietf.org>
Subject: [Tsvwg] Fwd: [re-ECN] Re-ECN meeting in Chicago
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

<html>
<body>
Folks,<br><br>
Just a reminder and link to slides for remote participants:<br><br>
Ad hoc unofficial BoF on re-ECN at the Chicago IETF and on audio. 1-3pm
today 25 Jul 07 (Chicago time), Room: Red Lacquar.<br><br>
Agenda as posted originally below, but in overview: <br>
1-2pm moving on the work of the group. <br>
2-3pm repeat 'Architectural Intent of re-ECN' from IETF-68, incl long
Q&amp;A<br><br>
Slides:<br>
&lt;<a href="http://www.cs.ucl.ac.uk/staff/B.Briscoe/projects/refb/#Presentations" eudora="autourl">http://www.cs.ucl.ac.uk/staff/B.Briscoe/projects/refb/#Presentations</a>&gt;<br>
(notes/audio will also be posted there when produced).<br><br>
Acknowledgement: Thanks to the IETF for the use of a room and mailing
list hosting. And thanks to Aaron Falk for agreeing to chair
again.<br><br>
<br>
Bob<br><br>
<blockquote type=cite class=cite cite>Date: Tue, 17 Jul 2007 13:38:13
+0100<br>
From: &lt;toby.moncaster@bt.com&gt;<br>
To: &lt;re-ecn@ietf.org&gt;<br>
Cc: tsv-area@ietf.org, tsvwg@ietf.org<br>
Subject: [re-ECN] Re-ECN meeting in Chicago<br>
<br><br>
<font face="Arial, Helvetica" size=2>All,</font> <br><br>
<font face="Arial, Helvetica" size=2>There will be another re-ECN
unofficial &quot;Bar BoF&quot; 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
&lt;</font><a href="http://www.cs.ucl.ac.uk/staff/B.Briscoe/projects/refb/#Presentations"><font face="Arial, Helvetica" size=2 color="#0000FF"><u>http://www.cs.ucl.ac.uk/staff/B.Briscoe/projects/refb/#Presentations</a></u></font><font face="Arial, Helvetica" size=2>&gt;)<br>
</font><br>
<font face="Arial, Helvetica" size=2>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. <br>
</font></blockquote><br>
---1pm---<br><br>
<blockquote type=cite class=cite cite>5
mins&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Administrivia
<br>
25 mins&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; presentation and
discussion on encoding in IP v4 and v6 (rationale behind choices,
alternatives, etc) [Bob B + mostly open mic]<br>
10 mins&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; How to deploy
experimentally (open mic) <br>
10 mins&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Deployment
Scenarios [Bob Briscoe]<br>
10 mins&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Next Steps: 
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
- format of the encoding (in v4, in v6) <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
- mechanics of the protocol in TCP/IP <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
- implementation of the dropper and the policer <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
- extension for use by TCP proxies or other congestion control
proxies&nbsp;&nbsp; <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
- extension for use by other transports <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
- etc <br>
</blockquote><br>
---2pm---<br><br>
25 mins Architectural Intent of re-ECN<br>
35 mins Q&amp;A<br><br>
---3pm--- End<br><br>
<blockquote type=cite class=cite cite><font face="Arial, Helvetica" size=2>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.<br>
</font><br>
<font face="Arial, Helvetica" size=2>All Internet drafts and other
documentation relevant to re-ECN can be found at:
&lt;</font><a href="http://www.cs.ucl.ac.uk/staff/B.Briscoe/projects/refb/"><font face="Arial, Helvetica" size=2 color="#0000FF"><u>http://www.cs.ucl.ac.uk/staff/B.Briscoe/projects/refb/</a></u></font><font face="Arial, Helvetica" size=2>&gt;
including draft-briscoe-tsvwg-re-ecn-tcp which describes the protocol and
the rationale behind it.<br>
</font><br>
<font face="Arial, Helvetica" size=2>Please could you address any replies
to this message to the unofficial IETF mailing list
re-ecn@ietf.org.</font> <br><br>
<font face="Arial, Helvetica" size=2><b>Toby
Moncaster</b></font><font face="Times New Roman, Times"> </font><br>
<font size=2>____________________________________________________________________________</font>
<br>
<font size=2>Toby Moncaster, &lt;toby.moncaster@bt.com&gt; Networks Research Centre, BT Research</font> <br>
<font size=2>B54/70 Adastral Park, Martlesham Heath, Ipswich, IP53RE, UK.&nbsp; +44 1473 648734</font> <br>
_______________________________________________<br>
re-ECN mailing list<br>
re-ECN@ietf.org<br>
<a href="https://www1.ietf.org/mailman/listinfo/re-ecn" eudora="autourl">https://www1.ietf.org/mailman/listinfo/re-ecn</a></blockquote>
<x-sigsep><p></x-sigsep>
____________________________________________________________________________<br>
Notice: This contribution is the personal view of the author and does not necessarily reflect the technical nor commercial direction of BT plc.<br>
____________________________________________________________________________<br>
Bob Briscoe,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Networks Research Centre, BT Research<br>
B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.&nbsp;&nbsp;&nbsp; +44 1473 645196</body>
</html>







From tsvwg-bounces@ietf.org Wed Jul 25 12:31:33 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDjlp-0006TA-1f; Wed, 25 Jul 2007 12:31:29 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IDjln-0006Sr-M3
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 25 Jul 2007 12:31:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDjln-0006Si-CC; Wed, 25 Jul 2007 12:31:27 -0400
Received: from smtp1.smtp.bt.com ([217.32.164.137])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IDjll-0004HX-Jl; Wed, 25 Jul 2007 12:31:27 -0400
Received: from E03MVZ4-UKDY.domain1.systemhost.net ([193.113.30.64]) by
	smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 25 Jul 2007 17:31:25 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7CED9.3DDF186C"
Date: Wed, 25 Jul 2007 17:31:34 +0100
Message-ID: <BAB4DC0CD5148948A86BD047A85CE2A7035EFA32@E03MVZ4-UKDY.domain1.systemhost.net>
In-Reply-To: <5.2.1.1.2.20070725170014.042e6d18@pop3.jungle.bt.co.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [re-ECN] Re-ECN meeting in Chicago
Thread-Index: AcfO2A70gdvfwYf/QgeSzCWH74nztgAALx5g
From: <toby.moncaster@bt.com>
To: <rbriscoe@jungle.bt.co.uk>,
	<re-ecn@ietf.org>
X-OriginalArrivalTime: 25 Jul 2007 16:31:25.0040 (UTC)
	FILETIME=[3E378700:01C7CED9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1c0c3d540ad9f95212b1c2a9a2cc2595
Cc: pcn@ietf.org, falk@ISI.EDU, tsvwg@ietf.org
Subject: [Tsvwg] RE: [re-ECN] Re-ECN meeting in Chicago
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7CED9.3DDF186C
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

For remote participants the audio stream is on channel 4:
http://videolab.uoregon.edu/events/ietf/ietf694.m3u
=20
We have been unable to set up a jabber stream...
=20
Toby

________________________________

From: Bob Briscoe [mailto:rbriscoe@jungle.bt.co.uk]=20
Sent: 25 July 2007 11:23
To: re-ECN unIETF list
Cc: PCN IETF list; Aaron Falk; tsvwg IETF list
Subject: Fwd: [re-ECN] Re-ECN meeting in Chicago


Folks,

Just a reminder and link to slides for remote participants:

Ad hoc unofficial BoF on re-ECN at the Chicago IETF and on audio. 1-3pm
today 25 Jul 07 (Chicago time), Room: Red Lacquar.

Agenda as posted originally below, but in overview:=20
1-2pm moving on the work of the group.=20
2-3pm repeat 'Architectural Intent of re-ECN' from IETF-68, incl long
Q&A

Slides:
<http://www.cs.ucl.ac.uk/staff/B.Briscoe/projects/refb/#Presentations>
(notes/audio will also be posted there when produced).

Acknowledgement: Thanks to the IETF for the use of a room and mailing
list hosting. And thanks to Aaron Falk for agreeing to chair again.


Bob



	Date: Tue, 17 Jul 2007 13:38:13 +0100
	From: <toby.moncaster@bt.com>
	To: <re-ecn@ietf.org>
	Cc: tsv-area@ietf.org, tsvwg@ietf.org
	Subject: [re-ECN] Re-ECN meeting in Chicago
=09
=09
	All,=20
=09
	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
<http://www.cs.ucl.ac.uk/staff/B.Briscoe/projects/refb/#Presentations>
>)
=09
	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.=20
=09


---1pm---



	5 mins          Administrivia=20
	25 mins         presentation and discussion on encoding in IP v4
and v6 (rationale behind choices, alternatives, etc) [Bob B + mostly
open mic]
	10 mins         How to deploy experimentally (open mic)=20
	10 mins         Deployment Scenarios [Bob Briscoe]
	10 mins         Next Steps:=20
	                   - format of the encoding (in v4, in v6)=20
	                   - mechanics of the protocol in TCP/IP=20
	                   - implementation of the dropper and the
policer=20
	                   - extension for use by TCP proxies or other
congestion control proxies  =20
	                   - extension for use by other transports=20
	                   - etc=20
=09


---2pm---

25 mins Architectural Intent of re-ECN
35 mins Q&A

---3pm--- End



	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.
=09
	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/
<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.
=09
	Please could you address any replies to this message to the
unofficial IETF mailing list re-ecn@ietf.org.=20
=09
	Toby Moncaster=20
=09
________________________________________________________________________
____=20
	Toby Moncaster, <toby.moncaster@bt.com> Networks Research
Centre, BT Research=20
	B54/70 Adastral Park, Martlesham Heath, Ipswich, IP53RE, UK.
+44 1473 648734=20
	_______________________________________________
	re-ECN mailing list
	re-ECN@ietf.org
	https://www1.ietf.org/mailman/listinfo/re-ecn

________________________________________________________________________
____
Notice: This contribution is the personal view of the author and does
not necessarily reflect the technical nor commercial direction of BT
plc.
________________________________________________________________________
____
Bob Briscoe,                           Networks Research Centre, BT
Research
B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473
645196=20


------_=_NextPart_001_01C7CED9.3DDF186C
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2769" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D457122816-25072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>For remote participants the audio =
stream&nbsp;is on channel=20
4: <A=20
href=3D"http://videolab.uoregon.edu/events/ietf/ietf694.m3u">http://video=
lab.uoregon.edu/events/ietf/ietf694.m3u</A></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D457122816-25072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D457122816-25072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>We have been unable to set up a jabber=20
stream...</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D457122816-25072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D457122816-25072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Toby</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Bob Briscoe=20
[mailto:rbriscoe@jungle.bt.co.uk] <BR><B>Sent:</B> 25 July 2007=20
11:23<BR><B>To:</B> re-ECN unIETF list<BR><B>Cc:</B> PCN IETF list; =
Aaron Falk;=20
tsvwg IETF list<BR><B>Subject:</B> Fwd: [re-ECN] Re-ECN meeting in=20
Chicago<BR></FONT><BR></DIV>
<DIV></DIV>Folks,<BR><BR>Just a reminder and link to slides for remote=20
participants:<BR><BR>Ad hoc unofficial BoF on re-ECN at the Chicago IETF =
and on=20
audio. 1-3pm today 25 Jul 07 (Chicago time), Room: Red =
Lacquar.<BR><BR>Agenda as=20
posted originally below, but in overview: <BR>1-2pm moving on the work =
of the=20
group. <BR>2-3pm repeat 'Architectural Intent of re-ECN' from IETF-68, =
incl long=20
Q&amp;A<BR><BR>Slides:<BR>&lt;<A=20
href=3D"http://www.cs.ucl.ac.uk/staff/B.Briscoe/projects/refb/#Presentati=
ons"=20
eudora=3D"autourl">http://www.cs.ucl.ac.uk/staff/B.Briscoe/projects/refb/=
#Presentations</A>&gt;<BR>(notes/audio=20
will also be posted there when produced).<BR><BR>Acknowledgement: Thanks =
to the=20
IETF for the use of a room and mailing list hosting. And thanks to Aaron =
Falk=20
for agreeing to chair again.<BR><BR><BR>Bob<BR><BR>
<BLOCKQUOTE class=3Dcite cite=3D"" type=3D"cite">Date: Tue, 17 Jul 2007 =
13:38:13=20
  +0100<BR>From: &lt;toby.moncaster@bt.com&gt;<BR>To:=20
  &lt;re-ecn@ietf.org&gt;<BR>Cc: tsv-area@ietf.org, =
tsvwg@ietf.org<BR>Subject:=20
  [re-ECN] Re-ECN meeting in Chicago<BR><BR><BR><FONT face=3D"Arial, =
Helvetica"=20
  size=3D2>All,</FONT> <BR><BR><FONT face=3D"Arial, Helvetica" =
size=3D2>There will be=20
  another re-ECN unofficial "Bar BoF" happening at IETF69 in Chicago =
next=20
  Wednesday July 25th. It will be at 1300-1500 in the Red Lacquar room. =
This is=20
  a follow on to the meeting held in Prague in March (slides and notes =
for which=20
  can be found at &lt;</FONT><A=20
  =
href=3D"http://www.cs.ucl.ac.uk/staff/B.Briscoe/projects/refb/#Presentati=
ons"><FONT=20
  face=3D"Arial, Helvetica" color=3D#0000ff=20
  =
size=3D2><U>http://www.cs.ucl.ac.uk/staff/B.Briscoe/projects/refb/#Presen=
tations</A></U></FONT><FONT=20
  face=3D"Arial, Helvetica" size=3D2>&gt;)<BR></FONT><BR><FONT=20
  face=3D"Arial, Helvetica" size=3D2>The aim of the meeting will be to =
discuss the=20
  next steps that need to be taken to move re-ECN forward. The draft =
agenda is=20
  as follows. If anyone would like to add any items please contact me on =
or off=20
  list. <BR></FONT></BLOCKQUOTE><BR>---1pm---<BR><BR>
<BLOCKQUOTE class=3Dcite cite=3D"" type=3D"cite">5=20
  mins&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Administrivia=20
  <BR>25 mins&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
presentation and=20
  discussion on encoding in IP v4 and v6 (rationale behind choices,=20
  alternatives, etc) [Bob B + mostly open mic]<BR>10=20
  mins&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; How to deploy=20
  experimentally (open mic) <BR>10=20
  mins&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Deployment =
Scenarios [Bob=20
  Briscoe]<BR>10 mins&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Next=20
  Steps:=20
  =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  - format of the encoding (in v4, in v6)=20
  =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  - mechanics of the protocol in TCP/IP=20
  =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  - implementation of the dropper and the policer=20
  =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  - extension for use by TCP proxies or other congestion control=20
  proxies&nbsp;&nbsp;=20
  =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  - extension for use by other transports=20
  =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  - etc <BR></BLOCKQUOTE><BR>---2pm---<BR><BR>25 mins Architectural =
Intent of=20
re-ECN<BR>35 mins Q&amp;A<BR><BR>---3pm--- End<BR><BR>
<BLOCKQUOTE class=3Dcite cite=3D"" type=3D"cite"><FONT face=3D"Arial, =
Helvetica"=20
  size=3D2>For those that missed it, we could use the second hour of the =
session=20
  to do a repeat of the presentation given in Prague in March. This was =
intended=20
  to present the architectural intent behind re-ECN as well as =
explaining how=20
  the base protocol works.<BR></FONT><BR><FONT face=3D"Arial, Helvetica" =

  size=3D2>All Internet drafts and other documentation relevant to =
re-ECN can be=20
  found at: &lt;</FONT><A=20
  href=3D"http://www.cs.ucl.ac.uk/staff/B.Briscoe/projects/refb/"><FONT=20
  face=3D"Arial, Helvetica" color=3D#0000ff=20
  =
size=3D2><U>http://www.cs.ucl.ac.uk/staff/B.Briscoe/projects/refb/</A></U=
></FONT><FONT=20
  face=3D"Arial, Helvetica" size=3D2>&gt; including =
draft-briscoe-tsvwg-re-ecn-tcp=20
  which describes the protocol and the rationale behind =
it.<BR></FONT><BR><FONT=20
  face=3D"Arial, Helvetica" size=3D2>Please could you address any =
replies to this=20
  message to the unofficial IETF mailing list re-ecn@ietf.org.</FONT>=20
  <BR><BR><FONT face=3D"Arial, Helvetica" size=3D2><B>Toby =
Moncaster</B></FONT><FONT=20
  face=3D"Times New Roman, Times"> </FONT><BR><FONT=20
  =
size=3D2>________________________________________________________________=
____________</FONT>=20
  <BR><FONT size=3D2>Toby Moncaster, &lt;toby.moncaster@bt.com&gt; =
Networks=20
  Research Centre, BT Research</FONT> <BR><FONT size=3D2>B54/70 Adastral =
Park,=20
  Martlesham Heath, Ipswich, IP53RE, UK.&nbsp; +44 1473 648734</FONT>=20
  <BR>_______________________________________________<BR>re-ECN mailing=20
  list<BR>re-ECN@ietf.org<BR><A=20
  href=3D"https://www1.ietf.org/mailman/listinfo/re-ecn"=20
  =
eudora=3D"autourl">https://www1.ietf.org/mailman/listinfo/re-ecn</A></BLO=
CKQUOTE><X-SIGSEP>
<P></X-SIGSEP>___________________________________________________________=
_________________<BR>Notice:=20
This contribution is the personal view of the author and does not =
necessarily=20
reflect the technical nor commercial direction of BT=20
plc.<BR>_________________________________________________________________=
___________<BR>Bob=20
Briscoe,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;=20
Networks Research Centre, BT Research<BR>B54/77 Adastral Park,Martlesham =

Heath,Ipswich,IP5 3RE,UK.&nbsp;&nbsp;&nbsp; +44 1473 645196 =
</P></BODY></HTML>

------_=_NextPart_001_01C7CED9.3DDF186C--





From tsvwg-bounces@ietf.org Thu Jul 26 07:51:02 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE1rO-0001Zk-St; Thu, 26 Jul 2007 07:50:26 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE1rN-0001ZU-US
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 07:50:25 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE1rN-0001ZK-8A
	for tsvwg@ietf.org; Thu, 26 Jul 2007 07:50:25 -0400
Received: from smtp2.smtp.bt.com ([217.32.164.150])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE1rM-0001kv-M3
	for tsvwg@ietf.org; Thu, 26 Jul 2007 07:50:25 -0400
Received: from i2kc06-ukbr.domain1.systemhost.net ([193.113.197.70]) by
	smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 12:50:23 +0100
Received: from cbibipnt05.iuser.iroot.adidom.com ([147.149.196.177]) by
	i2kc06-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 26 Jul 2007 12:50:23 +0100
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 1185450622258; Thu, 26 Jul 2007 12:50:22 +0100
Received: from mut.jungle.bt.co.uk ([10.86.5.78])
	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id
	l6QBoFQm012721; Thu, 26 Jul 2007 12:50:19 +0100
Message-Id: <5.2.1.1.2.20070726121842.04ce46a0@pop3.jungle.bt.co.uk>
X-Sender: rbriscoe@pop3.jungle.bt.co.uk
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Thu, 26 Jul 2007 12:49:37 +0100
To: "Michal Behringer" <mbehring@cisco.com>
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: -1.36 () ALL_TRUSTED
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 26 Jul 2007 11:50:23.0570 (UTC)
	FILETIME=[26692320:01C7CF7B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: PCN IETF list <pcn@ietf.org>, tsvwg IETF list <tsvwg@ietf.org>
Subject: [Tsvwg] draft-behringer-tsvwg-rsvp-security-groupkeying: Scope?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Michael,

Last night I read this draft, which you will be presenting today in tsvwg.

It was a useful tutorial for me, because I wasn't aware of all the group 
keying work for signalling that you describe.

1/ First a classic (picky?) security question: You talk about one RSVP node 
trusting the next. A future draft needs to answer the question "Trust to do 
what?"

You seem to imply you mean "Trust to maintain the integrity of RSVP 
messages and to maintain the next link in the chain of integrity checking". 
And later you implicitly add "Trust to keep the contents of the RSVP 
messages secret"

But, as this is a key management draft, you probably mean trust in message 
integrity _and_ semantics, ie "Trust to do all the things the RSVP protocol 
says you will do", e.g. things like traffic policing on behalf of others 
[RFC2210], protecting downstream RSVP nodes from overload [RFC2209] etc.

2/ WG Scope

2.1 PCN: Second, your draft is very relevant to the PCN working group. In 
PCN, the next RSVP hop is deliberately very distant from the previous one 
in IP hop terms. On Tue I raised this point and referred to your draft in 
my review of the PCN architecture:
<http://www1.ietf.org/mail-archive/web/pcn/current/msg00584.html>
(long - scroll right to the last para).
After yesterday's mtg, the PCN WG chairs are about to put this draft to the 
list for consideration as a WG item.

The PCN WG scope is currently restricted to one domain. So only message 
integrity is relevant (so a node receiving a message knows it didn't come 
from some random user spoofing the neighbouring RSVP router).

The PCN charter also says multi-domain should be kept in mind where it 
might change anything done for single domain. You'll see I also refer to 
the problem of trust in the semantics of reservation messages in my 
currently individual draft on solving (some) PCN security problems in a 
multi-domain scenario:
<draft-briscoe-re-pcn-border-cheat-00.txt>

2.2 NSIS: I guess your draft is just as relevant to NSIS as to RSVP, but to 
remain concrete, you will probably want to just say that the scope is wider 
but focus on one signalling system.


Bob


____________________________________________________________________________
Bob Briscoe, <bob.briscoe@bt.com>      Networks Research Centre, BT Research
B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 645196 







From tsvwg-bounces@ietf.org Thu Jul 26 08:05:18 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE25e-0004Rx-QZ; Thu, 26 Jul 2007 08:05:10 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE25e-0004Rd-9u
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 08:05:10 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE25d-0004Os-Sg
	for tsvwg@ietf.org; Thu, 26 Jul 2007 08:05:09 -0400
Received: from smtp2.smtp.bt.com ([217.32.164.150])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE25c-00022B-W0
	for tsvwg@ietf.org; Thu, 26 Jul 2007 08:05:09 -0400
Received: from i2kc08-ukbr.domain1.systemhost.net ([193.113.197.71]) by
	smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 13:05:08 +0100
Received: from cbibipnt08.iuser.iroot.adidom.com ([147.149.100.81]) by
	i2kc08-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 26 Jul 2007 13:05:07 +0100
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by
	cbibipnt08.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a
	P0803.399); id 1185451506656; Thu, 26 Jul 2007 13:05:06 +0100
Received: from mut.jungle.bt.co.uk ([10.86.5.78])
	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id
	l6QC51u6012894; Thu, 26 Jul 2007 13:05:05 +0100
Message-Id: <5.2.1.1.2.20070726125421.04e80400@pop3.jungle.bt.co.uk>
X-Sender: rbriscoe@pop3.jungle.bt.co.uk
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Thu, 26 Jul 2007 13:05:09 +0100
To: Sally Floyd <sallyfloyd@mac.com>
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
In-Reply-To: <c73ebd49050a446fbab11646dc6b750a@mac.com>
References: <5.2.1.1.2.20070721102131.051439c0@pop3.jungle.bt.co.uk>
	<5.2.1.1.2.20070721102131.051439c0@pop3.jungle.bt.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: -1.36 () ALL_TRUSTED
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 26 Jul 2007 12:05:07.0415 (UTC)
	FILETIME=[35392E70:01C7CF7D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
Cc: tsvwg IETF list <tsvwg@ietf.org>, Mark Allman <mallman@icir.org>
Subject: [Tsvwg] Re: terminology issues in draft-floyd-tsvwg-besteffort -
 "simple best effort"
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Sally,

At 18:01 24/07/2007, Sally Floyd wrote:
>Bob -
>
>I am answering the email one item at a time, as I find time.
>
>>1/ Simple?
>>
>>The term 'Simple Best Effort' contains a value judgement about simplicity.
>>
>>Many ISPs already limit their heavy users using various metrics: Volume 
>>caps, volume pricing, deep packet inspection (=infering an app implies 
>>heavy usage), or vaguely worded acceptable use policies tied to various 
>>forms of monitoring that allow them to issue email warnings, reduce 
>>priority and/or issue disconnection notices.
>>
>>By saying that 'Simple BE' is the dominant traffic class in the current 
>>Internet, you are either discounting all this policing as "not really 
>>policing" or as "not really complex", or you are implying most ISPs don't 
>>do any of this or most ISPs aren't planning to do more of this.
>>
>>What we're trying to do is provide the simplest possible principled and 
>>effective policing metric that is application-neutral and user-neutral; 
>>as an alternative to all the kludges being introduced that are complex 
>>and/or too blunt and/or non-neutral. It's most disheartening to be 
>>accused of making the world more complex, when we believe we're making it 
>>simpler than it would otherwise be.
>>
>>The best way to avoid that value judgement altogether is to just say 
>>"non-policed" or "unlimited", which is what you actually mean. And it 
>>would be best not to claim (without evidence) that ISPs who don't do any 
>>limiting are still predominant.
>
>We defined the phrase "simple best effort" as follows:
>In the abstract:
>    "This document presents some observations on "simple best-effort"
>     traffic, defined loosely for the purposes of this document as
>     Internet traffic that is not covered by Quality of Service
>     mechanisms, congestion-based pricing, or the like."
>
>And later in the Introduction:
>    "For the purposes of this document, we define "simple
>    best-effort traffic" as traffic that does not *rely* on the
>    *differential treatment* of flows either in routers or in policers,
>    enforcers, or other middleboxes along the path."
>
>I am happy to clarify the definition of "simple best effort" as
>used in our draft to say that it can include a wide range of things
>done by ISPs, including volume caps, volume pricing, deep packet
>inspection, vaguely worded acceptable use policies tied to various
>forms of monitoring, and other things done by ISPs.  But not including
>traffic that uses diffserv, intserv, congestion-based pricing,
>cost-based fairness mechanisms, *requirements* for ECN enabled at
>congested routers coupled with policers at the two ends of the
>connection, etc.
>
>I will also try to clarify the definition to make it clear that,
>for the purposes of this document, we are using the phrase "simple
>best-effort traffic" to mean "best-effort traffic like most of the
>traffic in the current Internet today".  We *don't* mean "non-policed",
>or "unlimited".
>
>We are not trying to imply that moving packets from point A to point
>B is simple, with or without volume caps, volume pricing, deep
>packet inspection, vaguely worded acceptable use policies tied to
>various forms of monitoring.

Then I don't see the point of the draft. You are saying "simple" traffic is 
useful because it is simple, even though you are willing to include all the 
non-simple things that need to be done to limit this traffic - so it isn't 
actually simple.

Now you've clarified your definition, I really don't know what the purpose 
of this draft is. It makes little sense with this new definition of simple 
to include non-simple.


>>2/ BE?
>>
>>This resource allocation debate is not about policing solely BE scheduled 
>>traffic. It could just as easily be about policing AF (say). The core 
>>issue that concerns you is whether ECN has to be turned on or not, so the 
>>most precise term is surely "non-ECN".
>
>I understand that the resource allocation debate is not about
>policing solely BE scheduled traffic.  As I said in the introduction
>to this draft, "This document does not attempt to be a rebuttal to
>[B07], or to answer any or all of the issues raised in [B07]".  This
>document is specifically about best-effort traffic, as it tries to
>make clear.
>
>"Non-ECN" was not what I had in mind.  I will clarify the definition
>of "simple best effort traffic" to say that it can include ECN.
>And that traffic that does not quality as "simple best-effort
>traffic", for the definition used in this draft, might or might not
>use ECN (e.g, diffserv traffic).
>
>But I am not going to try for an exhaustive definition of "simple
>best-effort traffic".  I think I can make the points in the draft,
>for most readers, without that.

OK, fair enough - you're allowed to confine your own scope to BE and that's 
a v relevant thing to focus on.


>>Points 1/ & 2/ summarised: Something like "Unlimited Non-ECN" would be 
>>more precise and preferable to 'Simple BE'.
>
>As I explained above, that is not what I had in mind.
>As I said above, I will clarify our definition of
>simple best-effort traffic.

So it's down to this question of simple including non-simple.


Bob

>- Sally
>http://www.icir.org/floyd/
>http://tools.ietf.org/html/draft-floyd-tsvwg-besteffort-00

____________________________________________________________________________
Bob Briscoe, <bob.briscoe@bt.com>      Networks Research Centre, BT Research
B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 645196 







From tsvwg-bounces@ietf.org Thu Jul 26 08:23:53 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE2Nc-00013H-Qz; Thu, 26 Jul 2007 08:23:44 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE2Na-0000tR-HK
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 08:23:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE2Na-0000tI-7d
	for tsvwg@ietf.org; Thu, 26 Jul 2007 08:23:42 -0400
Received: from smtp5.smtp.bt.com ([217.32.164.139])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE2NY-0003rw-NH
	for tsvwg@ietf.org; Thu, 26 Jul 2007 08:23:42 -0400
Received: from i2kc06-ukbr.domain1.systemhost.net ([193.113.197.70]) by
	smtp5.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 13:23:40 +0100
Received: from cbibipnt05.iuser.iroot.adidom.com ([147.149.196.177]) by
	i2kc06-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 26 Jul 2007 13:23:39 +0100
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 1185452618712; Thu, 26 Jul 2007 13:23:38 +0100
Received: from mut.jungle.bt.co.uk ([10.86.5.78])
	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id
	l6QCNWao013040; Thu, 26 Jul 2007 13:23:36 +0100
Message-Id: <5.2.1.1.2.20070726130544.04e7abd0@pop3.jungle.bt.co.uk>
X-Sender: rbriscoe@pop3.jungle.bt.co.uk
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Thu, 26 Jul 2007 13:23:46 +0100
To: Sally Floyd <sallyfloyd@mac.com>
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
In-Reply-To: <5a31970f1159b2e836c378b0e9c99e4c@mac.com>
References: <5.2.1.1.2.20070721102131.051439c0@pop3.jungle.bt.co.uk>
	<5.2.1.1.2.20070721102131.051439c0@pop3.jungle.bt.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: -1.36 () ALL_TRUSTED
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 26 Jul 2007 12:23:39.0899 (UTC)
	FILETIME=[CC50C4B0:01C7CF7F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: tsvwg IETF list <tsvwg@ietf.org>, Mark Allman <mallman@icir.org>
Subject: [Tsvwg] Re: terminology issues in draft-floyd-tsvwg-besteffort -
 flat monthly pricing
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Sally,

At 18:16 24/07/2007, Sally Floyd wrote:
>>3/ User pricing: Flat monthly (in our simplest effective proposal).
>>
>>Please don't imply we're advocating user congestion pricing, given the 
>>whole reason we brought re-ECN to the IETF back in 2005 was because we 
>>found a way to limit congestion without constraining how operators price 
>>their services to their customers. Specifically, re-ECN is designed to 
>>work with flat monthly pricing.
>
>This draft is not about re-ECN.  It is about the usefulness of
>"simple best-effort traffic", and the usefulness of flow-rate fairness
>for simple best-effort traffic.
>
>This draft is not about the presence or absence of flat monthly
>pricing for users.  One could have flat monthly pricing with no
>other limitations, one could have flat monthly pricing with volume
>limits, or one could have flat monthly pricing with some form of
>"you get what you pay for".  The first two forms don't result in
>"rich" users getting all of the bandwidth in times of high congestion
>(e.g., after the earthquake).  The third form easily could.  E.g.,
>if all of the traffic was "you get what you pay for", even with
>flat monthly fees, then it could be really expensive to send packets
>in the time interval after the earthquake, or some other highly-congested
>period, and only the rich would be able to send packets.  I would
>be opposed to setting such a "you get what you pay for" goal as the
>overriding goal for the global Internet, with or without flat monthly
>fees.

I know. It's distasteful to me to (I am a life-long socialist). But the 
alternatives are worse. I have thought about this long and hard.

On the demand side: If the rich don't get to be able to buy the right to 
use capacity, the alternative is that the malicious and selfish get to 
drive out those trying to be sociable in their use of the Internet. And 
that's for always, not just during earthquakes. Also, the lack of any 
resource sharing arbitration will lead to a vacuum that will be filled by 
the rich and powerful (which is what deep packet inspection represents - 
those with power and influence controlling what can and can't be done on 
the Internet).

On the supply side: The malicious and selfish will use the Internet 
excessively, but not pay their share, so there won't be sufficient 
incentives for anyone to invest in more capacity for those of us who want 
to use the Internet responsibly.

In summary, a knee-jerk reaction against a market mechanism needs to be 
tempered by the thought of what will otherwise fill the vacuum - the lesson 
of the Soviet Union?

However, you will notice in my draft on fairness (and in my design of 
re-ECN) that I have been careful to enable more equitable resource 
allocation schemes locally. This can give _true_ equality, whereas flow 
rate equality is just a license for the selfish and malicious to take what 
they want.

Overall, I put my hands up and admit it: we don't have a better system for 
allocating resources on planet scale than a market. I wish we did. We do 
have better resource sharing capabilities locally though, and I want to 
enable them.


Bob


>- Sally
>http://www.icir.org/floyd/

____________________________________________________________________________
Notice: This contribution is the personal view of the author and does not 
necessarily reflect the technical nor commercial direction of BT plc.
____________________________________________________________________________
Bob Briscoe,                           Networks Research Centre, BT Research
B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 645196 







From tsvwg-bounces@ietf.org Thu Jul 26 08:26:26 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE2QD-0003zf-QA; Thu, 26 Jul 2007 08:26:25 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE2QC-0003zN-4m
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 08:26:24 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE2QB-0003zF-QB
	for tsvwg@ietf.org; Thu, 26 Jul 2007 08:26:23 -0400
Received: from mail.gmx.net ([213.165.64.20])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IE2QB-0002Pw-4i
	for tsvwg@ietf.org; Thu, 26 Jul 2007 08:26:23 -0400
Received: (qmail invoked by alias); 26 Jul 2007 12:26:21 -0000
Received: from dhcp-15f4.ietf69.org (EHLO [130.129.21.244]) [130.129.21.244]
	by mail.gmx.net (mp007) with SMTP; 26 Jul 2007 14:26:21 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1/TcY0tcBXTpSMKUaZpIWBDmEbQoo04IBFR7cyQfq
	3cqmTQiW3vk3At
Message-ID: <46A892EE.8040908@gmx.net>
Date: Thu, 26 Jul 2007 14:26:22 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
References: <5.2.1.1.2.20070726121842.04ce46a0@pop3.jungle.bt.co.uk>
In-Reply-To: <5.2.1.1.2.20070726121842.04ce46a0@pop3.jungle.bt.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: PCN IETF list <pcn@ietf.org>, tsvwg IETF list <tsvwg@ietf.org>,
	Michal Behringer <mbehring@cisco.com>
Subject: [Tsvwg] Re: [PCN] draft-behringer-tsvwg-rsvp-security-groupkeying:
	Scope?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi

Bob Briscoe wrote:
> Michael,
>
> Last night I read this draft, which you will be presenting today in 
> tsvwg.
>
> It was a useful tutorial for me, because I wasn't aware of all the 
> group keying work for signalling that you describe.
>
> 1/ First a classic (picky?) security question: You talk about one RSVP 
> node trusting the next. A future draft needs to answer the question 
> "Trust to do what?"
>
> You seem to imply you mean "Trust to maintain the integrity of RSVP 
> messages and to maintain the next link in the chain of integrity 
> checking". And later you implicitly add "Trust to keep the contents of 
> the RSVP messages secret"
>
> But, as this is a key management draft, you probably mean trust in 
> message integrity _and_ semantics, ie "Trust to do all the things the 
> RSVP protocol says you will do", e.g. things like traffic policing on 
> behalf of others [RFC2210], protecting downstream RSVP nodes from 
> overload [RFC2209] etc.
>
The term "trust" is always confusing.

In short: You want to deal with a modified threat model in RSVP where 
you would like to protect the communication between  RSVP nodes when 
they traverse non-RSVP nodes.

> 2/ WG Scope
>
> 2.1 PCN: Second, your draft is very relevant to the PCN working group. 
> In PCN, the next RSVP hop is deliberately very distant from the 
> previous one in IP hop terms. On Tue I raised this point and referred 
> to your draft in my review of the PCN architecture:
> <http://www1.ietf.org/mail-archive/web/pcn/current/msg00584.html>
> (long - scroll right to the last para).
> After yesterday's mtg, the PCN WG chairs are about to put this draft 
> to the list for consideration as a WG item.
>
> The PCN WG scope is currently restricted to one domain. So only 
> message integrity is relevant (so a node receiving a message knows it 
> didn't come
>> from some random user spoofing the neighbouring RSVP router).
>
> The PCN charter also says multi-domain should be kept in mind where it 
> might change anything done for single domain. You'll see I also refer 
> to the problem of trust in the semantics of reservation messages in my 
> currently individual draft on solving (some) PCN security problems in 
> a multi-domain scenario:
> <draft-briscoe-re-pcn-border-cheat-00.txt>
>
I also think that PCN is a good use case for Michael's draft.
> 2.2 NSIS: I guess your draft is just as relevant to NSIS as to RSVP, 
> but to remain concrete, you will probably want to just say that the 
> scope is wider but focus on one signalling system.
>
No; it is isn't relevant based on how NSIS works. It does provide this 
functionality already but in a different way.

Ciao
Hannes

>
> Bob
>
>
> ____________________________________________________________________________ 
>
> Bob Briscoe, <bob.briscoe@bt.com>      Networks Research Centre, BT 
> Research
> B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 
> 645196
>
>
>
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www1.ietf.org/mailman/listinfo/pcn






From tsvwg-bounces@ietf.org Thu Jul 26 08:46:09 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE2jG-0000t3-M8; Thu, 26 Jul 2007 08:46:06 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE2jE-0000sV-Tz
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 08:46:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE2jE-0000sM-K6; Thu, 26 Jul 2007 08:46:04 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IE2jD-0004OE-5R; Thu, 26 Jul 2007 08:46:04 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 26 Jul 2007 14:46:02 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAGg0qEaQ/uCLZmdsb2JhbACPaAsKJA
X-IronPort-AV: i="4.16,584,1175464800"; 
	d="scan'208"; a="149071659:sNHT33138758"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6QCk2lo001990; 
	Thu, 26 Jul 2007 14:46:02 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6QCjklF029487; 
	Thu, 26 Jul 2007 12:46:01 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 14:45:46 +0200
Received: from [172.28.168.46] ([10.61.64.162]) by xfe-ams-331.emea.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 14:45:46 +0200
In-Reply-To: <46A892EE.8040908@gmx.net>
References: <5.2.1.1.2.20070726121842.04ce46a0@pop3.jungle.bt.co.uk>
	<46A892EE.8040908@gmx.net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <37BC7597-1DDF-4831-9EE2-F5FC90F9C5D0@cisco.com>
Content-Transfer-Encoding: 7bit
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
Date: Thu, 26 Jul 2007 07:42:46 -0500
To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 26 Jul 2007 12:45:46.0238 (UTC)
	FILETIME=[E2E009E0:01C7CF82]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=377; t=1185453962;
	x=1186317962; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.com>
	|Subject:=20Re=3A=20[PCN]=20draft-behringer-tsvwg-rsvp-security-groupkeyi
	ng=3A=20Scope? |Sender:=20;
	bh=LmHM/2ZlQU9DHO+FO76QM008JPpG2saNxXJYgBFqj70=;
	b=vcaVfmnIXRZDvl3pZXCUgnvca/9pJPGLx/H8d8g/YTUAJeilpXh/Y8T8qP7MU5z3cgPjrwpT
	1MS1j5w8+PGN6hfKg91xi9upU4x3GjATVjpzdxgNEHQbLlPudnTCWnFV;
Authentication-Results: ams-dkim-2; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: PCN IETF list <pcn@ietf.org>, Michal Behringer <mbehring@cisco.com>,
	tsvwg IETF list <tsvwg@ietf.org>
Subject: [Tsvwg] Re: [PCN] draft-behringer-tsvwg-rsvp-security-groupkeying:
	Scope?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi,

>>
> I also think that PCN is a good use case for Michael's draft.

Group keying should come in handy for any form of "aggregation" where  
RSVP nodes are separated by an aggregation cloud and where the  
Aggregator does not know ahead of time what is the Deaggregator. So  
besides PCN, it should also be applicable to RFC3175 and RFC4860.

Cheers

Francois





From tsvwg-bounces@ietf.org Thu Jul 26 08:48:30 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE2lZ-0004Ds-Qv; Thu, 26 Jul 2007 08:48:29 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE2lY-0004Di-8r
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 08:48:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE2lX-0004DY-VQ
	for tsvwg@ietf.org; Thu, 26 Jul 2007 08:48:27 -0400
Received: from smtp1.smtp.bt.com ([217.32.164.137])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE2lW-0004SK-F9
	for tsvwg@ietf.org; Thu, 26 Jul 2007 08:48:27 -0400
Received: from i2kc08-ukbr.domain1.systemhost.net ([193.113.197.71]) by
	smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 13:48:25 +0100
Received: from cbibipnt08.iuser.iroot.adidom.com ([147.149.100.81]) by
	i2kc08-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 26 Jul 2007 13:48:17 +0100
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by
	cbibipnt08.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a
	P0803.399); id 1185454096948; Thu, 26 Jul 2007 13:48:16 +0100
Received: from mut.jungle.bt.co.uk ([10.86.5.78])
	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id
	l6QCmCR2013200; Thu, 26 Jul 2007 13:48:15 +0100
Message-Id: <5.2.1.1.2.20070726132435.04e81750@pop3.jungle.bt.co.uk>
X-Sender: rbriscoe@pop3.jungle.bt.co.uk
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Thu, 26 Jul 2007 13:48:25 +0100
To: Sally Floyd <sallyfloyd@mac.com>
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
In-Reply-To: <80cbbf6f29fe311e534c72629df8b466@mac.com>
References: <5.2.1.1.2.20070721102131.051439c0@pop3.jungle.bt.co.uk>
	<5.2.1.1.2.20070721102131.051439c0@pop3.jungle.bt.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: -1.36 () ALL_TRUSTED
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 26 Jul 2007 12:48:17.0933 (UTC)
	FILETIME=[3D4ADBD0:01C7CF83]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: tsvwg IETF list <tsvwg@ietf.org>, Mark Allman <mallman@icir.org>
Subject: [Tsvwg] Re: terminology issues in draft-floyd-tsvwg-besteffort - per
 flow or per user
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Sally,

At 18:29 24/07/2007, Sally Floyd wrote:
>Bob -
>
>>4/ User policing: Bulk per-customer (in our simplest effective proposal).
>>
>>Please don't imply that we're advocating per-flow policing. Admittedly we 
>>have always shown how you could do either per-flow or per-user. Before 
>>Oct-06 when I wrote that I-D on dismantling flow rate fairness, the 
>>community wanted to be able to police flow rates, so we wanted to show we 
>>could. But we neither require it nor recommend it. Our per-user policing 
>>makes per-flow policing redundant (but it's still there if an IPS wants it).
>>
>>For the avoidance of doubt, "Bulk per-customer" policing means policing 
>>all traffic crossing the customer's sending access interface using a bulk 
>>token bucket to regulate the bit rate of congestion marked packets to all 
>>destinations together.
>
>If you let me know where the draft implied that you were
>advocating per-flow policing, I would be happy to correct it.
>(I looked, but I didn't see it.)

I think you're right. I can't find it either now. Sorry.


>The draft is not intended to be about any specific proposed mechanism.
>It is simply in support of "simple best-effort traffic", and in support of
>flow-based fairness for simple best-effort traffic.

Yes, I know. But saying it's a "separate viewpoint about some related 
topics" reminded me a bit of the polite opener "With the greatest of 
respect...".

Cheers


Bob

>- Sally
>http://www.icir.org/floyd/

____________________________________________________________________________
Bob Briscoe, <bob.briscoe@bt.com>      Networks Research Centre, BT Research
B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 645196 







From tsvwg-bounces@ietf.org Thu Jul 26 08:53:33 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE2pz-0000DZ-WB; Thu, 26 Jul 2007 08:53:04 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE2py-0000DS-U3
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 08:53:02 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE2py-0000DK-JC
	for tsvwg@ietf.org; Thu, 26 Jul 2007 08:53:02 -0400
Received: from smtp3.smtp.bt.com ([217.32.164.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE2py-00033X-0l
	for tsvwg@ietf.org; Thu, 26 Jul 2007 08:53:02 -0400
Received: from i2kc08-ukbr.domain1.systemhost.net ([193.113.197.71]) by
	smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 13:53:00 +0100
Received: from cbibipnt08.iuser.iroot.adidom.com ([147.149.100.81]) by
	i2kc08-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 26 Jul 2007 13:53:00 +0100
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by
	cbibipnt08.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a
	P0803.399); id 1185454379720; Thu, 26 Jul 2007 13:52:59 +0100
Received: from mut.jungle.bt.co.uk ([10.86.5.78])
	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id
	l6QCqrf5013224; Thu, 26 Jul 2007 13:52:57 +0100
Message-Id: <5.2.1.1.2.20070726134851.04e7f740@pop3.jungle.bt.co.uk>
X-Sender: rbriscoe@pop3.jungle.bt.co.uk
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Thu, 26 Jul 2007 13:53:08 +0100
To: Sally Floyd <sallyfloyd@mac.com>
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
In-Reply-To: <9359d93f7aa2aa2768b04107fa12d5ef@mac.com>
References: <5.2.1.1.2.20070721102131.051439c0@pop3.jungle.bt.co.uk>
	<5.2.1.1.2.20070721102131.051439c0@pop3.jungle.bt.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: -1.36 () ALL_TRUSTED
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 26 Jul 2007 12:53:00.0798 (UTC)
	FILETIME=[E5E4A1E0:01C7CF83]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: "FLOYD, Sally" <floyd@acm.org>, tsvwg IETF list <tsvwg@ietf.org>,
	mallman@icir.org
Subject: [Tsvwg] Re: terminology issues in draft-floyd-tsvwg-besteffort -
 simple pair-wise relationships
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Sally,

At 18:43 24/07/2007, Sally Floyd wrote:
>>5/ Economic infrastructure: Simple pair-wise relationships (in our 
>>simplest proposal)
>>
>>Please don't imply we're making economic infrastructure more complex. All 
>>network layer relationships would still be between directly connected 
>>neighbours (pairwise).
>>
>>Currently many border contracts between privately connected ISPs or 
>>between ISPs and a peering exchange include an element of usage charging 
>>(as well as interface capacity pricing). Whether based on volume, on some 
>>notion of peak demand, or on a hybrid. We propose adding a metric 
>>(congestion volume) that is only slightly less simple than monthly byte-volume.
>>
>>However, congestion volume is much more effective, as it can be used to 
>>make networks precisely accountable for the costs they cause in other 
>>networks (unlike a volume metric, which depresses usage even when the 
>>capacity is there for it).
>>
>>So most of the inter-domain contracts that currently include an element 
>>of usage might switch to using congestion volume. And those that don't 
>>include any form of usage measurements in their contracts might stick 
>>that way. That doesn't make any contracts any more complex.
>
>Our draft says the following:
>
>    "The difficulties of deployment for end-to-end intserv or diffserv
>    mechanisms are well-known, having in part to do with the difficulties
>    of deployment for the economic infrastructure that would be needed
>    [B03].  It seems likely that cost-based pricing based on re-ECN could
>    also have a difficult deployment path, involving the deployment of
>    ECN-marking at routers, policers at both ends of a connection, and a
>    complex set of economic relationships [B07]."
>
>I would be happy to clarify it that the set of economic relationships
>required for "cost-based pricing based on re-ECN" would be pairwise,
>with a metric for congestion volume.
>
>(Note that this sentence is not about all possible forms of re-ECN,
>but about "cost-based pricing based on re-ECN".

Good - that's v precise - thanks.

re-ECN is a proposal to solely add an additional metric to IP. You are 
correct that all the possible economic structures that might be built over 
it are just what I predict might happen. And in that sense, it _can_ 
support a structure of simple pairwise relationships that could also give 
precise incentives for everyone to limit the congestion they cause.

>Our draft is not
>about re-ECN - it is simply in support of "simple best-effort
>traffic", and in support of flow-based fairness for simple best-effort
>traffic.)

Understood.

Cheers


bob

>- Sally
>http://www.icir.org/floyd/

____________________________________________________________________________
Bob Briscoe, <bob.briscoe@bt.com>      Networks Research Centre, BT Research
B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 645196 







From tsvwg-bounces@ietf.org Thu Jul 26 09:13:48 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE39y-0006vt-OF; Thu, 26 Jul 2007 09:13:42 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE39x-0006vF-6X
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 09:13:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE39w-0006v6-Sy
	for tsvwg@ietf.org; Thu, 26 Jul 2007 09:13:40 -0400
Received: from smtp1.smtp.bt.com ([217.32.164.137])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE39v-0004ze-JG
	for tsvwg@ietf.org; Thu, 26 Jul 2007 09:13:40 -0400
Received: from i2kc06-ukbr.domain1.systemhost.net ([193.113.197.70]) by
	smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 14:13:37 +0100
Received: from cbibipnt05.iuser.iroot.adidom.com ([147.149.196.177]) by
	i2kc06-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 26 Jul 2007 13:54:35 +0100
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 1185454467876; Thu, 26 Jul 2007 13:54:27 +0100
Received: from mut.jungle.bt.co.uk ([10.86.5.78])
	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id
	l6QCsD9N013238; Thu, 26 Jul 2007 13:54:24 +0100
Message-Id: <5.2.1.1.2.20070726135405.04dca858@pop3.jungle.bt.co.uk>
X-Sender: rbriscoe@pop3.jungle.bt.co.uk
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Thu, 26 Jul 2007 13:54:28 +0100
To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
In-Reply-To: <46A892EE.8040908@gmx.net>
References: <5.2.1.1.2.20070726121842.04ce46a0@pop3.jungle.bt.co.uk>
	<5.2.1.1.2.20070726121842.04ce46a0@pop3.jungle.bt.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: -1.36 () ALL_TRUSTED
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 26 Jul 2007 12:54:36.0380 (UTC)
	FILETIME=[1EDD49C0:01C7CF84]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: PCN IETF list <pcn@ietf.org>, tsvwg IETF list <tsvwg@ietf.org>,
	Michal Behringer <mbehring@cisco.com>
Subject: [Tsvwg] Re: [PCN] draft-behringer-tsvwg-rsvp-security-groupkeying:
 Scope?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hannes,

At 13:26 26/07/2007, Hannes Tschofenig wrote:
>>2.2 NSIS: I guess your draft is just as relevant to NSIS as to RSVP, but 
>>to remain concrete, you will probably want to just say that the scope is 
>>wider but focus on one signalling system.
>No; it is isn't relevant based on how NSIS works. It does provide this 
>functionality already but in a different way.

ref? I'm interested.


bob


____________________________________________________________________________
Bob Briscoe, <bob.briscoe@bt.com>      Networks Research Centre, BT Research
B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 645196 







From tsvwg-bounces@ietf.org Thu Jul 26 09:47:57 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE3h2-00060x-9b; Thu, 26 Jul 2007 09:47:52 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE3h0-00060m-Sj
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 09:47:50 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE3h0-000609-H9
	for tsvwg@ietf.org; Thu, 26 Jul 2007 09:47:50 -0400
Received: from mail.gmx.net ([213.165.64.20])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IE3gz-0004QS-Q4
	for tsvwg@ietf.org; Thu, 26 Jul 2007 09:47:50 -0400
Received: (qmail invoked by alias); 26 Jul 2007 13:47:48 -0000
Received: from dhcp-15f4.ietf69.org (EHLO [130.129.21.244]) [130.129.21.244]
	by mail.gmx.net (mp053) with SMTP; 26 Jul 2007 15:47:48 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX18gusU3s3gghmqAJDtDwY3NBQ07key3W7fL9ML7Qd
	5/SGBC23lTsOe1
Message-ID: <46A8A606.6070608@gmx.net>
Date: Thu, 26 Jul 2007 15:47:50 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: Francois Le Faucheur IMAP <flefauch@cisco.com>
References: <5.2.1.1.2.20070726121842.04ce46a0@pop3.jungle.bt.co.uk>
	<46A892EE.8040908@gmx.net>
	<37BC7597-1DDF-4831-9EE2-F5FC90F9C5D0@cisco.com>
In-Reply-To: <37BC7597-1DDF-4831-9EE2-F5FC90F9C5D0@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: PCN IETF list <pcn@ietf.org>, tsvwg IETF list <tsvwg@ietf.org>,
	Michal Behringer <mbehring@cisco.com>
Subject: [Tsvwg] Re: [PCN] draft-behringer-tsvwg-rsvp-security-groupkeying:
	Scope?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi Francois,

>> I also think that PCN is a good use case for Michael's draft.
>
> Group keying should come in handy for any form of "aggregation" where 
> RSVP nodes are separated by an aggregation cloud and where the 
> Aggregator does not know ahead of time what is the Deaggregator. So 
> besides PCN, it should also be applicable to RFC3175 and RFC4860.
>
I agree with you.

Ciao
Hannes

> Cheers
>
> Francois






From tsvwg-bounces@ietf.org Thu Jul 26 09:50:25 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE3jV-000739-7q; Thu, 26 Jul 2007 09:50:25 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE3jT-00072Q-U4
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 09:50:23 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE3jT-00072A-74
	for tsvwg@ietf.org; Thu, 26 Jul 2007 09:50:23 -0400
Received: from mail.gmx.net ([213.165.64.20])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IE3jS-0004UJ-Eh
	for tsvwg@ietf.org; Thu, 26 Jul 2007 09:50:23 -0400
Received: (qmail invoked by alias); 26 Jul 2007 13:50:20 -0000
Received: from dhcp-15f4.ietf69.org (EHLO [130.129.21.244]) [130.129.21.244]
	by mail.gmx.net (mp008) with SMTP; 26 Jul 2007 15:50:20 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1/I6KcTK4TI0Mqug5lNi/gRZcXGGUVLp1NH1da3fE
	N1E73FraYx0qnP
Message-ID: <46A8A69E.6030706@gmx.net>
Date: Thu, 26 Jul 2007 15:50:22 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
References: <5.2.1.1.2.20070726121842.04ce46a0@pop3.jungle.bt.co.uk>
	<5.2.1.1.2.20070726121842.04ce46a0@pop3.jungle.bt.co.uk>
	<5.2.1.1.2.20070726135405.04dca858@pop3.jungle.bt.co.uk>
In-Reply-To: <5.2.1.1.2.20070726135405.04dca858@pop3.jungle.bt.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: PCN IETF list <pcn@ietf.org>, tsvwg IETF list <tsvwg@ietf.org>,
	Michal Behringer <mbehring@cisco.com>
Subject: [Tsvwg] Re: [PCN] draft-behringer-tsvwg-rsvp-security-groupkeying:
	Scope?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi Bob,

Bob Briscoe wrote:
> Hannes,
>
> At 13:26 26/07/2007, Hannes Tschofenig wrote:
>>> 2.2 NSIS: I guess your draft is just as relevant to NSIS as to RSVP, 
>>> but to remain concrete, you will probably want to just say that the 
>>> scope is wider but focus on one signalling system.
>> No; it is isn't relevant based on how NSIS works. It does provide 
>> this functionality already but in a different way.
>
> ref? I'm interested.
>
The functionality was dumped into the main specification:
http://www.ietf.org/internet-drafts/draft-ietf-nsis-ntlp-14.txt

Let me know if you need a bit of background.

Ciao
Hannes

>
> bob
>
>
> ____________________________________________________________________________ 
>
> Bob Briscoe, <bob.briscoe@bt.com>      Networks Research Centre, BT 
> Research
> B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 
> 645196






From tsvwg-bounces@ietf.org Thu Jul 26 09:50:32 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE3jb-0007Ca-O6; Thu, 26 Jul 2007 09:50:32 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE3jZ-0007Bs-MD
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 09:50:29 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE3jZ-0007BW-9U
	for tsvwg@ietf.org; Thu, 26 Jul 2007 09:50:29 -0400
Received: from mail.gmx.net ([213.165.64.20])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IE3jY-0004Ua-OS
	for tsvwg@ietf.org; Thu, 26 Jul 2007 09:50:29 -0400
Received: (qmail invoked by alias); 26 Jul 2007 13:50:27 -0000
Received: from dhcp-15f4.ietf69.org (EHLO [130.129.21.244]) [130.129.21.244]
	by mail.gmx.net (mp041) with SMTP; 26 Jul 2007 15:50:27 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX184sGFaHq04VEbNzeKZ56nV0i/FGD5iwTs9OMakng
	rA8EzbFDqpqFkt
Message-ID: <46A8A6A5.4000604@gmx.net>
Date: Thu, 26 Jul 2007 15:50:29 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
References: <5.2.1.1.2.20070726121842.04ce46a0@pop3.jungle.bt.co.uk>
	<5.2.1.1.2.20070726121842.04ce46a0@pop3.jungle.bt.co.uk>
	<5.2.1.1.2.20070726135405.04dca858@pop3.jungle.bt.co.uk>
In-Reply-To: <5.2.1.1.2.20070726135405.04dca858@pop3.jungle.bt.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: PCN IETF list <pcn@ietf.org>, tsvwg IETF list <tsvwg@ietf.org>,
	Michal Behringer <mbehring@cisco.com>
Subject: [Tsvwg] Re: [PCN] draft-behringer-tsvwg-rsvp-security-groupkeying:
	Scope?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi Bob,

Bob Briscoe wrote:
> Hannes,
>
> At 13:26 26/07/2007, Hannes Tschofenig wrote:
>>> 2.2 NSIS: I guess your draft is just as relevant to NSIS as to RSVP, 
>>> but to remain concrete, you will probably want to just say that the 
>>> scope is wider but focus on one signalling system.
>> No; it is isn't relevant based on how NSIS works. It does provide 
>> this functionality already but in a different way.
>
> ref? I'm interested.
>
The functionality was dumped into the main specification:
http://www.ietf.org/internet-drafts/draft-ietf-nsis-ntlp-14.txt

Let me know if you need a bit of background.

Ciao
Hannes

>
> bob
>
>
> ____________________________________________________________________________ 
>
> Bob Briscoe, <bob.briscoe@bt.com>      Networks Research Centre, BT 
> Research
> B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 
> 645196






From tsvwg-bounces@ietf.org Thu Jul 26 09:51:11 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE3kF-0008Ii-16; Thu, 26 Jul 2007 09:51:11 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE3kD-0008IS-8C
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 09:51:09 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE3kC-0008IK-St
	for tsvwg@ietf.org; Thu, 26 Jul 2007 09:51:08 -0400
Received: from smtp1.smtp.bt.com ([217.32.164.137])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE3kB-0004VS-Hx
	for tsvwg@ietf.org; Thu, 26 Jul 2007 09:51:08 -0400
Received: from i2kc06-ukbr.domain1.systemhost.net ([193.113.197.70]) by
	smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 14:49:02 +0100
Received: from cbibipnt05.iuser.iroot.adidom.com ([147.149.196.177]) by
	i2kc06-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 26 Jul 2007 14:26:17 +0100
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 1185456352678; Thu, 26 Jul 2007 14:25:52 +0100
Received: from mut.jungle.bt.co.uk ([10.86.5.78])
	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id
	l6QDPm3S013539; Thu, 26 Jul 2007 14:25:51 +0100
Message-Id: <5.2.1.1.2.20070726141117.04e7a828@pop3.jungle.bt.co.uk>
X-Sender: rbriscoe@pop3.jungle.bt.co.uk
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Thu, 26 Jul 2007 14:26:02 +0100
To: Sally Floyd <sallyfloyd@mac.com>
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: -1.36 () ALL_TRUSTED
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 26 Jul 2007 13:26:17.0369 (UTC)
	FILETIME=[8BF13090:01C7CF88]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Cc: tsvwg IETF list <tsvwg@ietf.org>, Mark Allman <mallman@icir.org>
Subject: [Tsvwg] Re: terminology issues in draft-floyd-tsvwg-besteffort -
 flat monthly pricing
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Sally,

I just realised that I should have added a very important point about "who 
controls the choice" to the rather philosophical response below.

I'm trying to make sure we at the IETF don't have to decide whether the 
Internet more favours rich people, malicious people or selfish people. I'm 
trying to make it so what you think or what I think about this doesn't 
matter (at least any more than what everyone else in the world thinks).

Firstly, what I'm proposing would sit alongside the current Internet 
(re-ECN packets are distinguishable from non-re-ECN packets, so they 
effectively partition all traffic orthogonally to Diffserv).

Secondly, one partition would be the current Internet, with all its 
vulnerabilites to selfish and malicious users as well as all its strengths. 
The other partition would be this new proposal where the market and social 
governance can control the way the Internet shares out resources.

At a grander level, the choice of how much resource each of the two 
partitions gets would be under the direct control of ISPs, but in turn 
their choices are also affected by the market and perhaps by social control 
through government regulation.

I know this fits your preferred model of how new resource allocation 
strategies should be added to the Internet. The question is whether it is 
sufficiently important to use IP header space to provide this choice. We 
don't need to decide that now, but we do need to debate it widely - more 
widely than tsvwg.


Bob

At 18:16 24/07/2007, Sally Floyd wrote:
>>3/ User pricing: Flat monthly (in our simplest effective proposal).
>>
>>Please don't imply we're advocating user congestion pricing, given the 
>>whole reason we brought re-ECN to the IETF back in 2005 was because we 
>>found a way to limit congestion without constraining how operators price 
>>their services to their customers. Specifically, re-ECN is designed to 
>>work with flat monthly pricing.
>
>This draft is not about re-ECN.  It is about the usefulness of
>"simple best-effort traffic", and the usefulness of flow-rate fairness
>for simple best-effort traffic.
>
>This draft is not about the presence or absence of flat monthly
>pricing for users.  One could have flat monthly pricing with no
>other limitations, one could have flat monthly pricing with volume
>limits, or one could have flat monthly pricing with some form of
>"you get what you pay for".  The first two forms don't result in
>"rich" users getting all of the bandwidth in times of high congestion
>(e.g., after the earthquake).  The third form easily could.  E.g.,
>if all of the traffic was "you get what you pay for", even with
>flat monthly fees, then it could be really expensive to send packets
>in the time interval after the earthquake, or some other highly-congested
>period, and only the rich would be able to send packets.  I would
>be opposed to setting such a "you get what you pay for" goal as the
>overriding goal for the global Internet, with or without flat monthly
>fees.

I know. It's distasteful to me to (I am a life-long socialist). But the 
alternatives are worse. I have thought about this long and hard.

On the demand side: If the rich don't get to be able to buy the right to 
use capacity, the alternative is that the malicious and selfish get to 
drive out those trying to be sociable in their use of the Internet. And 
that's for always, not just during earthquakes. Also, the lack of any 
resource sharing arbitration will lead to a vacuum that will be filled by 
the rich and powerful (which is what deep packet inspection represents - 
those with power and influence controlling what can and can't be done on 
the Internet).

On the supply side: The malicious and selfish will use the Internet 
excessively, but not pay their share, so there won't be sufficient 
incentives for anyone to invest in more capacity for those of us who want 
to use the Internet responsibly.

In summary, a knee-jerk reaction against a market mechanism needs to be 
tempered by the thought of what will otherwise fill the vacuum - the lesson 
of the Soviet Union?

However, you will notice in my draft on fairness (and in my design of 
re-ECN) that I have been careful to enable more equitable resource 
allocation schemes locally. This can give _true_ equality, whereas flow 
rate equality is just a license for the selfish and malicious to take what 
they want.

Overall, I put my hands up and admit it: we don't have a better system for 
allocating resources on planet scale than a market. I wish we did. We do 
have better resource sharing capabilities locally though, and I want to 
enable them.


Bob


>- Sally
>http://www.icir.org/floyd/

____________________________________________________________________________
Notice: This contribution is the personal view of the author and does not 
necessarily reflect the technical nor commercial direction of BT plc.
____________________________________________________________________________
Bob Briscoe,                           Networks Research Centre, BT Research
B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 645196  







From tsvwg-bounces@ietf.org Thu Jul 26 10:25:49 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE4FU-0001uy-15; Thu, 26 Jul 2007 10:23:28 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE4FR-0001u8-Hr
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 10:23:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE4FR-0001tr-7l; Thu, 26 Jul 2007 10:23:25 -0400
Received: from drew.ipv6.franken.de ([2001:638:a02:a001:20e:cff:fe4a:feaa]
	helo=mail-n.franken.de) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IE4FP-0006p4-IH; Thu, 26 Jul 2007 10:23:25 -0400
Received: from [130.129.82.234] (unknown [130.129.82.234])
	by mail-n.franken.de (Postfix) with ESMTP id C16D4801AC1A;
	Thu, 26 Jul 2007 16:23:19 +0200 (CEST)
	(KNF-authenticated sender: macmic)
In-Reply-To: <OFFC8632AB.5A75783C-ON48257324.000D06E1@chinamobile.com>
References: <OFFC8632AB.5A75783C-ON48257324.000D06E1@chinamobile.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=UTF-8; delsp=yes; format=flowed
Message-Id: <15F44738-6468-43CE-AABF-E9A7CBF65158@lurchi.franken.de>
Content-Transfer-Encoding: quoted-printable
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Date: Thu, 26 Jul 2007 16:23:20 +0200
To: chenxu <chenxu@chinamobile.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 1.9 (+)
X-Scan-Signature: 93b4f10b2112e1468b61e19ea6180478
Cc: SIGTRAN <sigtran@ietf.org>, TSWG <tsvwg@ietf.org>
Subject: [Tsvwg] Re: [Sigtran] The requiremnts and proposals
	forM2PA/M3UA/SCTPExtension from China Mobile
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Dear all,

I'm sending this also to TSVWG, since the SCTP discussion has to be
done the that WG.

Addressing the SCTP statement:

1. What does "unionize of the primary paths between nodes" mean?
2. Not sure about the SACK issue: You are currently allowed to
    send the SACK back to an addresses different from the source
    address of the corresponding DATA chunk. As far as I know
    it is only a SHOULD describing that you send the SACK back
    to the source address of the DATA chunk.

Best regards
Michael

On Jul 26, 2007, at 4:22 AM, chenxu wrote:

> Dear all,
>
>      Sorry to submit the rar file! And thanks Rui Gomes!
>
> The contents of the attachments are as follows:
>
>   =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>   for SCTP of China Mobile.ppt
>  =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>
>  The Requirement and Proposal
>   for SCTP Specification Extension
>   of China Mobile
>
>  Chen Xu , Zhang Hao
>  China Mobile
>
>  Content
>
>  Background
>  Problem description
>  Requirement for Supplement of RFC4460
>  Proposal for Supplement of RFC4460
>
>  Background
>
>  The world trend of IP bearer for signalling will make SIGTRAN
>  standard widely used in signalling network.
>  Traditional and new Telecom carriers implement signalling over IP to
>  Reduce  cost for extended capacity
>  Removes the links/linkset limitation imposed by traditional TDM
>  linksets for traffic growth
>  Avoid major network re-engineering when traffic grows
>  SCTP is the basis of signalling over IP
>
>  SCTP is also important to China Mobile
>  Applying to the Nc interface to transport BICC messages
>  Applying to the Mc interface to transport H.248 messages
>  Applying to the interface between MSC Server and the embedded SG to
>  transport access network signalling
>  Applying to signalling network
>  the interface between IPSEPs
>  the interface between IPSTPs
>  the interface between IPSEP and IPSTP
>
>
> Problem description
>
> China Mobile has a large number of subscribers and has built the
>  largest soft-switch network in the world. The signaling traffic
>  between two nodes is very large.
>  China Mobile imports multi-vender=E2=80=99s products. The =
compatibility
>  between different vender=E2=80=99s products is important.
>  The illegibility of Multi-homing mechanism in SCTP protocol brings
>  on compatibility problems
>  SCTP did not define the mechanism how the SACK is send back to
>  endpoint by other path when one path fails.
>  SCTP defines multi-homing, but it did not define how the primary
>  path can be unionized between two nodes.
>  Requirement for Supplement of RFC4460
>  Define the mechanism that SACK is send back to endpoint by the
>  secondary path if the primary path fails .
>  Define  the mechanism how the primary path can be unionized between
>  two nodes.
>
>
>  Proposal for Supplement of RFC4460
>
>
>  1=EF=BC=89Add the mechanism how the primary path can be unionized =
between
>  two nodes in Section 5  =E2=80=98Association Initialization =E2=80=99.
>  2=EF=BC=89 Add the mechanism that SACK is send back to endpoint by =
the
>  secondary path if the primary path fails in Section 6.2
>  =E2=80=98Acknowledgement on Reception of DATA Chunks =E2=80=99.
>
> (That's all for SCTP)
>
>
>  =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>  for M3UA of China Mobile.ppt
>  =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>
>  The Requirement and Proposal
>   for M3UA Specification Extension
>   of China Mobile
>
>  Chen Xu
>  China Mobile
>
>
>  Content
>
> Background
>  Problem Description
>  Requirement for Extension of RFC4666
>  Proposal for Extension of RFC4666
>
>
>
>  Background
>
>  The application of SIGTRAN standard for SG has ever solved the
>  problems of  No.7 Signalling System Interworking IP and
>  transmission of  access network signalling  in  R4 CS core network.
>  The world trend of IP bearer for signalling will make SIGTRAN
>  standard widely used in signalling network.
>  Traditional and new Telecom carriers implement signalling over IP to
>  Reduce  cost for extended capacity
>  Removes the links/linkset limitation imposed by traditional TDM
>  linksets for traffic growth
>  Avoid major network re-engineering as traffic grows
>
>  SIGTRAN is also important to China Mobile
>  Applying to the Nc interface of BICC network to transport BICC
>  messages
>  Applying to the interface between MSC Server and embeded SG to
>  transport access network signalling
>  Applying to signalling network
>  the interface between IPSEPs=E2=80=94=E2=80=94M3UA
>  the interface between IPSTPs=E2=80=94=E2=80=94M2PA
>  the interface between IPSEP and IPSTP=E2=80=94=E2=80=94M3UA
>
>  Problem description
>
>  M3UA specification doesn=E2=80=99t  define signaling network  =
management
>  function
>  M3UA is designed for SG-IPSEP and IPSEP-IPSEP applications,
>  therefore network level management function isn=E2=80=99t required.
>  SSNM messages defined in M3UA are only used for interworking with =20
> SS7.
>  China Mobile has a large number of subscribers and has built the
>  largest soft-switch network in the world, its signaling network
>  will be the multi-level and multi-area mode.
>  It will has two signalling routeing  scene:IPSEP-IPSTP-IPSTP-IPSEP
>  and IPSEP-IPSTP-IPSEP
>  The interworking  function with MTP3 in M3UA can realize the
>  signaling network  management for  IPSEP-IPSTP-IPSTP-IPSEP scene;
>  Current M3UA  can not  realize the signaling network  management
>  for  IPSEP-IPSTP-IPSEP scene.
>
>  Requirement for Extension of RFC4666
>
>  Define the Application for IPSTP-IPSEP interface.(Still uses SGP-
>  ASP procedures)
>  Define the signalling network management function=EF=BC=8Cmessages =
,and
>  procedures.(Describe how to use SSNM messages to support signaling
>  network management for IPSEP-(M3UA)-IPSTP-(M3UA)-IPSEP scene. )
>
>  Proposal for Extension of RFC4666
>
>  1=EF=BC=89Add different kinds of routing scenes applications for =
IPSEP-
>  IPSTP interface in Section 1.5  =E2=80=98Sample Configuration =E2=80=99=
.
>  2=EF=BC=89Add the M3UA signalling network management function in =
Section
>  1.4  =E2=80=98Functional Areas=E2=80=99.
>  3=EF=BC=89 Add the Client/Server Model for IPSTP-IPSEP interface in
>  Section 1.4.8.  =E2=80=98SCTP Client/Server Model=E2=80=99.
>  4=EF=BC=89Extend the DUPU message code in Chapter 3 =E2=80=98M3UA =
Protocol
>  Elements=E2=80=99.
>  5=EF=BC=89Add the signalling network management procedure in Chapter
>  4=E2=80=99procedure=E2=80=99.
>  6) Add the requirement of Multi user data streams for M3UA over
>  SCTP Application in Section 1.4.7 =E2=80=98 SCTP Stream Mapping=E2=80=99=
.
>
> (That's all for M3UA)
>
>
>  =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>  for M2PA of China Mobile.ppt
>  =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>
>  The Requirement and Proposal
>   for M2PA Specification Revision
>   of China Mobile
>
>  Chen Xu
>  China Mobile
>
>  Content
>
>  Background
>  Problem Description
>  Requirement for Revision of RFC4165
>  Proposal for Revision of RFC4165
>
>
>  Background
>
>  M2PA protocol is a peer to peer protocol, it not only supports
>  seamless management operation of MTP3 protocol peers over an IP
>  network connection, but also removes the links/linkset limitation
>  imposed by traditional TDM linksets for traffic growth.
>
>  The Standardization of M2PA is behind the application of it.
>  Although the RFC edition is released in 2005, M2PA is widely used
>  in the  Signaling network rebuilding over IP for traditional
>  operators and in the Signaling network construction for  new
>  operators  since 2002.
>
>  Various draft editions and the major differences between them make
>  problems when one  IPSTP provider interworking with another.
>
>  Problem Description
>
>
>  RFC4165 needs to be supplemented and revised =EF=BC=9A
>  Some  procedures  are  described a little bit simply and referred
>  to MTP2 directly ,  which  makes IPSTP  providers realizing the
>  procedures in different ways ,for  there=E2=80=99s difference between =
MTP2
>  and M2PA in some aspects.      .
>  Some IPSTP providers use the same idea as MTP2
>  Others take the relation between M2PA and SCTP into account.
>
>  T7 isn=E2=80=99t defined and given the range, which makes IPSTP =
providers
>  realizing it in different ways.
>
>  How to fill in and process FSN and BSN in M2PA Header isn=E2=80=99t
>  defined clearly.
>
>
>  Requirement for Revision of RFC4165
>
>  Supplement the description of the whole idea for Link Alignment
>  procedure and Processor Outage procedure.
>  Supplement the definition and range of M2PA Timers.
>  Supplement the rules of usage of FSN and BSN in M2PA Header.
>
>
>  Proposal for Revision of RFC4165
>
>  1=EF=BC=89Supplement the whole idea , the phase division , the =
correlated
>  messages and Timers of Link Alignment procedure in Section 4.1.3.
>  2=EF=BC=89Supplement the whole idea of Processor Outage procedure, =
and
>  describe the rules of LPO and RPO processing separately .
>  3=EF=BC=89Supplement the rules of usage of FSN and BSN in M2PA Header =
in
>  Section 4.2.1
>  4=EF=BC=89Supplement the definition and range of M2PA Timers in =
Appendix.
>
> (That's all for M2PA)
>
> Chen Xu
> China Mobile
> chenxu@chinamobile.com
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran






From tsvwg-bounces@ietf.org Thu Jul 26 10:43:00 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE4YN-0001xZ-AT; Thu, 26 Jul 2007 10:42:59 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE4YL-0001l2-Bz
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 10:42:57 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE4YK-0001ia-Vn; Thu, 26 Jul 2007 10:42:57 -0400
Received: from mail2.microsoft.com ([131.107.115.215] helo=smtp.microsoft.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IE4YK-0006O4-Hs; Thu, 26 Jul 2007 10:42:56 -0400
Received: from tk5-exhub-c103.redmond.corp.microsoft.com (157.54.70.186) by
	TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with
	Microsoft
	SMTP Server (TLS) id 8.0.700.0; Thu, 26 Jul 2007 07:42:55 -0700
Received: from NA-EXMSG-C110.redmond.corp.microsoft.com ([157.54.62.150]) by
	tk5-exhub-c103.redmond.corp.microsoft.com ([157.54.70.186]) with mapi;
	Thu, 26 Jul 2007 07:42:55 -0700
From: Murari Sridharan <muraris@microsoft.com>
To: tsvwg WG <tsvwg@ietf.org>
Date: Thu, 26 Jul 2007 07:42:42 -0700
Subject: RE: [Tsvwg] Re: [tcpm] Revision of
	draft-larsen-tsvwg-port-randomization
Thread-Topic: [Tsvwg] Re: [tcpm] Revision of
	draft-larsen-tsvwg-port-randomization
Thread-Index: Ace+JxXMdyd0r6m8RjWOhYwptpupIgRazzkA
Message-ID: <FCA794787FDE0D4DBE9FFA11053ECEB60C26A1618E@NA-EXMSG-C110.redmond.corp.microsoft.com>
References: <200702111621.l1BGL6mw029875@venus.xmundo.net>
	<0E46EBE9-1C13-44B6-9C04-476D418F5A6D@nokia.com>
	<A6CE6259-646E-4C35-9DA3-8911A8CB2B54@nokia.com>
In-Reply-To: <A6CE6259-646E-4C35-9DA3-8911A8CB2B54@nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: ext, "tcpm@ietf.org" <tcpm@ietf.org>, DCCP mailing list <dccp@ietf.org>,
	Fernando Gont <fernando@gont.com.ar>, TSV Dir <tsv-dir@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

In this context I wanted to bring up a related issue that might also streng=
then this sort of a port randomization proposal.

Today the 64k port limitation is starting to become a huge problem and most=
 often admins add ip addresses to increase the scalability. Given that most=
 often the destination port (and sometimes the destination address) is well=
 known, the only scalability left is the source address. Increasing ip addr=
esses to improve scalability seems a fairly round about approach and frankl=
y doesn't scale well. Given that the 64k limit is not fundamental why not p=
rovide a scaling factor similar to the receive window to scale the number o=
f usable ports. This also makes randomization much more meaningful because =
in certain proxy scenarios the number of connections quickly exhausts the a=
vailable ports and at that point the attacker can simply use any port assum=
ing he can guess the source address.

Murari

-----Original Message-----
From: Lars Eggert [mailto:lars.eggert@nokia.com]
Sent: Wednesday, July 04, 2007 3:35 AM
To: tsvwg WG
Cc: tcpm@ietf.org; DCCP mailing list; ext Fernando Gont; TSV Dir
Subject: Re: [Tsvwg] Re: [tcpm] Revision of draft-larsen-tsvwg-port-randomi=
zation

On 2007-5-31, at 17:51, ext Lars Eggert wrote:
> The concepts in this draft are likely relevant to most of our
> transport protocols, and hence would be in scope for TSVWG. The
> TSVWG chairs are interested in comments on whether there is group
> interest in this draft - please comment on tsvwg@ietf.org.

We've received some positive feedback on adopting this draft, but I'd
like to see a stronger show of support, because this draft impacts
several of our transport protocols at the same time.

Please comment on tsvwg@ietf.org - reply-to set accordingly.

Lars







From tsvwg-bounces@ietf.org Thu Jul 26 10:56:58 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE4lF-0003WO-M0; Thu, 26 Jul 2007 10:56:17 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE4lD-0003WB-Ui
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 10:56:15 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE4lD-0003Vq-8c; Thu, 26 Jul 2007 10:56:15 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IE4lC-0006rb-K5; Thu, 26 Jul 2007 10:56:15 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 26 Jul 2007 07:56:14 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAOBSqEarR7PD/2dsb2JhbAA
X-IronPort-AV: i="4.16,584,1175497200"; 
	d="scan'208"; a="189078335:sNHT30437271"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l6QEuDb2015410; 
	Thu, 26 Jul 2007 07:56:13 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l6QEuD6C019840;
	Thu, 26 Jul 2007 14:56:13 GMT
Received: from xmb-sjc-21c.amer.cisco.com ([171.70.151.176]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 07:56:13 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Tsvwg] Re: [tcpm] Revision
	ofdraft-larsen-tsvwg-port-randomization
Date: Thu, 26 Jul 2007 07:56:11 -0700
Message-ID: <0C53DCFB700D144284A584F54711EC5803B6C62F@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <FCA794787FDE0D4DBE9FFA11053ECEB60C26A1618E@NA-EXMSG-C110.redmond.corp.microsoft.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Tsvwg] Re: [tcpm] Revision
	ofdraft-larsen-tsvwg-port-randomization
Thread-Index: Ace+JxXMdyd0r6m8RjWOhYwptpupIgRazzkAAABLFiA=
From: "Anantha Ramaiah \(ananth\)" <ananth@cisco.com>
To: "Murari Sridharan" <muraris@microsoft.com>, "tsvwg WG" <tsvwg@ietf.org>
X-OriginalArrivalTime: 26 Jul 2007 14:56:13.0474 (UTC)
	FILETIME=[1C457820:01C7CF95]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3405; t=1185461773;
	x=1186325773; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=ananth@cisco.com;
	z=From:=20=22Anantha=20Ramaiah=20\(ananth\)=22=20<ananth@cisco.com>
	|Subject:=20RE=3A=20[Tsvwg]=20Re=3A=20[tcpm]=20Revision=20ofdraft-larsen-
	tsvwg-port-randomization |Sender:=20;
	bh=L5QW9CIDUvaUFTMQwpAlzY/qEeLRhkkbm8X7R/GiTBs=;
	b=aw8TaeFatxIgO/4c/S0HMabKl3mWRzbegkef4E7wxcB/bm4Bebov2MCZhS7m9iIwlr9YhrEr
	j8eB/Wao4juChzpjpfphdsMboHdDX5bbVoStSNh9NPR2y2lMG/ukjYO6;
Authentication-Results: sj-dkim-3; header.From=ananth@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: ext@cisco.com, tcpm@ietf.org, DCCP mailing list <dccp@ietf.org>,
	Fernando Gont <fernando@gont.com.ar>, TSV Dir <tsv-dir@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Murari,

I agree it is good idea to have an extended port range. But dearth of
ports is one such issue. We could argue the same about TCP options
(there are few drafts which never moved forward, AFAIK). Also you can
argue he same about TCP seq#/ack# for better security reasons. I think
Mark Allman wrote a document TCPx2 (or something) which basically
doubles the TCP header (64 bit seq/ack, 32 ports etc.,) So some of the
questions which might come up (aka possible ways of achieving this)

- why not have complete change to TCP header ?(like Mark's draft is
suggesting). Obviously it almost like "TCP v6". Lots of change needed
everywhere :-)

- or do it in piecemeal, first buy more TCP option space, standardize
any one of the proposals for extending the TCP option space. Then have
an extended port option like yu suggest below. Then think about other
TCP fields requiring extension.

Just a few thoughts.

-Anantha

> -----Original Message-----
> From: Murari Sridharan [mailto:muraris@microsoft.com]=20
> Sent: Thursday, July 26, 2007 7:43 AM
> To: tsvwg WG
> Cc: ext@cisco.com; tcpm@ietf.org; DCCP mailing list; Fernando=20
> Gont; TSV Dir
> Subject: RE: [Tsvwg] Re: [tcpm] Revision=20
> ofdraft-larsen-tsvwg-port-randomization
>=20
> In this context I wanted to bring up a related issue that=20
> might also strengthen this sort of a port randomization proposal.
>=20
> Today the 64k port limitation is starting to become a huge=20
> problem and most often admins add ip addresses to increase=20
> the scalability. Given that most often the destination port=20
> (and sometimes the destination address) is well known, the=20
> only scalability left is the source address. Increasing ip=20
> addresses to improve scalability seems a fairly round about=20
> approach and frankly doesn't scale well. Given that the 64k=20
> limit is not fundamental why not provide a scaling factor=20
> similar to the receive window to scale the number of usable=20
> ports. This also makes randomization much more meaningful=20
> because in certain proxy scenarios the number of connections=20
> quickly exhausts the available ports and at that point the=20
> attacker can simply use any port assuming he can guess the=20
> source address.
>=20
> Murari
>=20
> -----Original Message-----
> From: Lars Eggert [mailto:lars.eggert@nokia.com]
> Sent: Wednesday, July 04, 2007 3:35 AM
> To: tsvwg WG
> Cc: tcpm@ietf.org; DCCP mailing list; ext Fernando Gont; TSV Dir
> Subject: Re: [Tsvwg] Re: [tcpm] Revision of=20
> draft-larsen-tsvwg-port-randomization
>=20
> On 2007-5-31, at 17:51, ext Lars Eggert wrote:
> > The concepts in this draft are likely relevant to most of our=20
> > transport protocols, and hence would be in scope for TSVWG.=20
> The TSVWG=20
> > chairs are interested in comments on whether there is group=20
> interest=20
> > in this draft - please comment on tsvwg@ietf.org.
>=20
> We've received some positive feedback on adopting this draft,=20
> but I'd like to see a stronger show of support, because this=20
> draft impacts several of our transport protocols at the same time.
>=20
> Please comment on tsvwg@ietf.org - reply-to set accordingly.
>=20
> Lars
>=20
>=20
>=20
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www1.ietf.org/mailman/listinfo/tcpm
>=20





From tsvwg-bounces@ietf.org Thu Jul 26 11:05:17 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE4ts-0001XF-VK; Thu, 26 Jul 2007 11:05:13 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE4tr-0001Wu-QW
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 11:05:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE4tr-0001Wl-Gp; Thu, 26 Jul 2007 11:05:11 -0400
Received: from smtp.microsoft.com ([131.107.115.212])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IE4tq-0008PL-8q; Thu, 26 Jul 2007 11:05:11 -0400
Received: from tk1-exhub-c104.redmond.corp.microsoft.com (157.56.116.117) by
	TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with
	Microsoft
	SMTP Server (TLS) id 8.0.700.0; Thu, 26 Jul 2007 08:05:09 -0700
Received: from NA-EXMSG-C110.redmond.corp.microsoft.com ([157.54.62.150]) by
	tk1-exhub-c104.redmond.corp.microsoft.com ([157.56.116.117]) with mapi;
	Thu, 26 Jul 2007 08:05:09 -0700
From: Murari Sridharan <muraris@microsoft.com>
To: "Anantha Ramaiah (ananth)" <ananth@cisco.com>, tsvwg WG <tsvwg@ietf.org>
Date: Thu, 26 Jul 2007 08:05:08 -0700
Subject: RE: [Tsvwg] Re: [tcpm] Revision
	ofdraft-larsen-tsvwg-port-randomization
Thread-Topic: [Tsvwg] Re: [tcpm] Revision
	ofdraft-larsen-tsvwg-port-randomization
Thread-Index: Ace+JxXMdyd0r6m8RjWOhYwptpupIgRazzkAAABLFiAAAJKnUA==
Message-ID: <FCA794787FDE0D4DBE9FFA11053ECEB60C26A161B5@NA-EXMSG-C110.redmond.corp.microsoft.com>
References: <FCA794787FDE0D4DBE9FFA11053ECEB60C26A1618E@NA-EXMSG-C110.redmond.corp.microsoft.com>
	<0C53DCFB700D144284A584F54711EC5803B6C62F@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <0C53DCFB700D144284A584F54711EC5803B6C62F@xmb-sjc-21c.amer.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Spam-Score: -8.0 (--------)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: "tcpm@ietf.org" <tcpm@ietf.org>, mailing list <dccp@ietf.org>,
	Fernando Gont <fernando@gont.com.ar>, TSV Dir <tsv-dir@ietf.org>,
	"ext@cisco.com" <ext@cisco.com>, DCCP
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

We'll I guess we need things to be incrementally deployable so I think piec=
emeal is more practical. Having said that I am very cautious about any exte=
nsibility proposal, primarily around non-compliant devices which makes even=
 incremental deployment slow down to a crawl, like the problems we are seei=
ng with enabling WS by default. Given this option has been around forever a=
nd still causes significant connectivity problems so piecemeal options are =
not a cake walk either.

-----Original Message-----
From: Anantha Ramaiah (ananth) [mailto:ananth@cisco.com]
Sent: Thursday, July 26, 2007 7:56 AM
To: Murari Sridharan; tsvwg WG
Cc: ext@cisco.com; tcpm@ietf.org; DCCP mailing list; Fernando Gont; TSV Dir
Subject: RE: [Tsvwg] Re: [tcpm] Revision ofdraft-larsen-tsvwg-port-randomiz=
ation

Murari,

I agree it is good idea to have an extended port range. But dearth of
ports is one such issue. We could argue the same about TCP options
(there are few drafts which never moved forward, AFAIK). Also you can
argue he same about TCP seq#/ack# for better security reasons. I think
Mark Allman wrote a document TCPx2 (or something) which basically
doubles the TCP header (64 bit seq/ack, 32 ports etc.,) So some of the
questions which might come up (aka possible ways of achieving this)

- why not have complete change to TCP header ?(like Mark's draft is
suggesting). Obviously it almost like "TCP v6". Lots of change needed
everywhere :-)

- or do it in piecemeal, first buy more TCP option space, standardize
any one of the proposals for extending the TCP option space. Then have
an extended port option like yu suggest below. Then think about other
TCP fields requiring extension.

Just a few thoughts.

-Anantha

> -----Original Message-----
> From: Murari Sridharan [mailto:muraris@microsoft.com]
> Sent: Thursday, July 26, 2007 7:43 AM
> To: tsvwg WG
> Cc: ext@cisco.com; tcpm@ietf.org; DCCP mailing list; Fernando
> Gont; TSV Dir
> Subject: RE: [Tsvwg] Re: [tcpm] Revision
> ofdraft-larsen-tsvwg-port-randomization
>
> In this context I wanted to bring up a related issue that
> might also strengthen this sort of a port randomization proposal.
>
> Today the 64k port limitation is starting to become a huge
> problem and most often admins add ip addresses to increase
> the scalability. Given that most often the destination port
> (and sometimes the destination address) is well known, the
> only scalability left is the source address. Increasing ip
> addresses to improve scalability seems a fairly round about
> approach and frankly doesn't scale well. Given that the 64k
> limit is not fundamental why not provide a scaling factor
> similar to the receive window to scale the number of usable
> ports. This also makes randomization much more meaningful
> because in certain proxy scenarios the number of connections
> quickly exhausts the available ports and at that point the
> attacker can simply use any port assuming he can guess the
> source address.
>
> Murari
>
> -----Original Message-----
> From: Lars Eggert [mailto:lars.eggert@nokia.com]
> Sent: Wednesday, July 04, 2007 3:35 AM
> To: tsvwg WG
> Cc: tcpm@ietf.org; DCCP mailing list; ext Fernando Gont; TSV Dir
> Subject: Re: [Tsvwg] Re: [tcpm] Revision of
> draft-larsen-tsvwg-port-randomization
>
> On 2007-5-31, at 17:51, ext Lars Eggert wrote:
> > The concepts in this draft are likely relevant to most of our
> > transport protocols, and hence would be in scope for TSVWG.
> The TSVWG
> > chairs are interested in comments on whether there is group
> interest
> > in this draft - please comment on tsvwg@ietf.org.
>
> We've received some positive feedback on adopting this draft,
> but I'd like to see a stronger show of support, because this
> draft impacts several of our transport protocols at the same time.
>
> Please comment on tsvwg@ietf.org - reply-to set accordingly.
>
> Lars
>
>
>
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www1.ietf.org/mailman/listinfo/tcpm
>





From tsvwg-bounces@ietf.org Thu Jul 26 11:27:18 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE5F3-00046p-EP; Thu, 26 Jul 2007 11:27:05 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE5F1-00046a-Ni
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 11:27:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE5F1-00046P-DU
	for tsvwg@ietf.org; Thu, 26 Jul 2007 11:27:03 -0400
Received: from mail1.sea5.speakeasy.net ([69.17.117.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE5F0-0000aj-3G
	for tsvwg@ietf.org; Thu, 26 Jul 2007 11:27:03 -0400
Received: (qmail 21296 invoked from network); 26 Jul 2007 15:27:00 -0000
Received: from dsl092-045-037.lax1.dsl.speakeasy.net (HELO [66.92.45.37])
	(cait@asomi.com@[66.92.45.37]) (envelope-sender <cait@asomi.com>)
	by mail1.sea5.speakeasy.net (qmail-ldap-1.03) with AES128-SHA encrypted
	SMTP for <muraris@microsoft.com>; 26 Jul 2007 15:27:00 -0000
In-Reply-To: <0C53DCFB700D144284A584F54711EC5803B6C62F@xmb-sjc-21c.amer.cisco.com>
References: <0C53DCFB700D144284A584F54711EC5803B6C62F@xmb-sjc-21c.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <13DAF96D-70E1-411E-9408-130A33987671@asomi.com>
Content-Transfer-Encoding: 7bit
From: Caitlin Bestler <cait@asomi.com>
Subject: Re: [Tsvwg] Re: [tcpm] Revision
	ofdraft-larsen-tsvwg-port-randomization
Date: Thu, 26 Jul 2007 08:26:35 -0700
To: "Anantha Ramaiah \(ananth\)" <ananth@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: Murari Sridharan <muraris@microsoft.com>, tsvwg <tsvwg@ietf.org>,
	Fernando Gont <fernando@gont.com.ar>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org


On Jul 26, 2007, at 7:56 AM, Anantha Ramaiah ((ananth)) wrote:

> Murari,
>
> I agree it is good idea to have an extended port range. But dearth of
> ports is one such issue. We could argue the same about TCP options
> (there are few drafts which never moved forward, AFAIK). Also you can
> argue he same about TCP seq#/ack# for better security reasons. I think
> Mark Allman wrote a document TCPx2 (or something) which basically
> doubles the TCP header (64 bit seq/ack, 32 ports etc.,) So some of the
> questions which might come up (aka possible ways of achieving this)
>
> - why not have complete change to TCP header ?(like Mark's draft is
> suggesting). Obviously it almost like "TCP v6". Lots of change needed
> everywhere :-)
>
> - or do it in piecemeal, first buy more TCP option space, standardize
> any one of the proposals for extending the TCP option space. Then have
> an extended port option like yu suggest below. Then think about other
> TCP fields requiring extension.
>
> Just a few thoughts.
>
> -Anantha
>

SCTP already addresses most of these points, and is already an RFC.
In my opinion, any proposal to radically "fix" TCP needs to learn  
from the
deployment barriers that SCTP has faced and come up with a better plan.
If you aren't going to be completely transparent to all existing  
middleboxes,
then there really isn't any reason not to simply declare SCTP to be  
"new TCP".






From tsvwg-bounces@ietf.org Thu Jul 26 11:38:46 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE5QK-0004QH-6r; Thu, 26 Jul 2007 11:38:44 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE5QJ-0004Ps-1J
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 11:38:43 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE5QI-0004Pi-MT
	for tsvwg@ietf.org; Thu, 26 Jul 2007 11:38:42 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE5QI-0008JO-BX
	for tsvwg@ietf.org; Thu, 26 Jul 2007 11:38:42 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 26 Jul 2007 11:38:42 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAPRcqEZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,584,1175486400"; 
	d="scan'208"; a="66237280:sNHT31488614"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l6QFcfCE004182; 
	Thu, 26 Jul 2007 11:38:41 -0400
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l6QFcaSn003523;
	Thu, 26 Jul 2007 15:38:41 GMT
Received: from xmb-sjc-21c.amer.cisco.com ([171.70.151.176]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 08:38:28 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Tsvwg] Re: [tcpm] Revision
	ofdraft-larsen-tsvwg-port-randomization
Date: Thu, 26 Jul 2007 08:37:19 -0700
Message-ID: <0C53DCFB700D144284A584F54711EC5803B6C65A@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <13DAF96D-70E1-411E-9408-130A33987671@asomi.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Tsvwg] Re: [tcpm] Revision
	ofdraft-larsen-tsvwg-port-randomization
Thread-Index: AcfPmXHTu9hY0omeTPKl95xOJywGfAAACCWQ
From: "Anantha Ramaiah \(ananth\)" <ananth@cisco.com>
To: "Caitlin Bestler" <cait@asomi.com>
X-OriginalArrivalTime: 26 Jul 2007 15:38:28.0665 (UTC)
	FILETIME=[035CEA90:01C7CF9B]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=922; t=1185464321;
	x=1186328321; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=ananth@cisco.com;
	z=From:=20=22Anantha=20Ramaiah=20\(ananth\)=22=20<ananth@cisco.com>
	|Subject:=20RE=3A=20[Tsvwg]=20Re=3A=20[tcpm]=20Revision=20ofdraft-larsen-
	tsvwg-port-randomization |Sender:=20
	|To:=20=22Caitlin=20Bestler=22=20<cait@asomi.com>;
	bh=F4jgzd0z4fjOqK38dzk+qcZUC+YS2BjwQT2HOXDoJ7w=;
	b=lu1VvALzgINRBd6+v5WVTBkj7Lvcx+5wIJodzu78hKUFlAxbAO+YyArEJrmEklbzSRzDnt7P
	TQWr6EdHA/XeIL0hbCpHbx9/QbUkNKIwGZt28lKOViiDtix35JTC/qiO;
Authentication-Results: rtp-dkim-1; header.From=ananth@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: Murari Sridharan <muraris@microsoft.com>, tsvwg <tsvwg@ietf.org>,
	Fernando Gont <fernando@gont.com.ar>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Caitlin,
=20
>=20
> SCTP already addresses most of these points, and is already an RFC.
> In my opinion, any proposal to radically "fix" TCP needs to=20
> learn from the deployment barriers that SCTP has faced and=20
> come up with a better plan.
> If you aren't going to be completely transparent to all=20
> existing middleboxes, then there really isn't any reason not=20
> to simply declare SCTP to be "new TCP".

Agreed.=20

OTOH, adding more TCP option space should not be treated as a radical
change to TCP. Also the original email and the draft reference was more
about doing some things (like port randomization) which would help
increase the robustness of a some protocols, including TCP. Currently
there is no way to do this (without limiting the options which you can
send in the SYN) without increasing the TCP option space since it is
getting over-subscribed these days.

-Anantha
>=20





From tsvwg-bounces@ietf.org Thu Jul 26 11:48:00 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE5ZE-0004g1-Bs; Thu, 26 Jul 2007 11:47:56 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE5ZC-0004fl-IQ
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 11:47:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE5ZC-0004fb-8b
	for tsvwg@ietf.org; Thu, 26 Jul 2007 11:47:54 -0400
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE5ZA-0001PC-Ql
	for tsvwg@ietf.org; Thu, 26 Jul 2007 11:47:54 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l6QFkY4v010718; Thu, 26 Jul 2007 18:47:21 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 18:47:09 +0300
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 18:47:04 +0300
Received: from mgw-int01.ntc.nokia.com ([172.21.143.96]) by
	esebh101.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 26 Jul 2007 18:46:59 +0300
Received: from [130.129.84.254] (daec-linuxvpn059128.americas.nokia.com
	[10.241.59.128])
	by mgw-int01.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l6QFku11019856; Thu, 26 Jul 2007 18:46:57 +0300
In-Reply-To: <0C53DCFB700D144284A584F54711EC5803B6C65A@xmb-sjc-21c.amer.cisco.com>
References: <0C53DCFB700D144284A584F54711EC5803B6C65A@xmb-sjc-21c.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-27-999183107;
	protocol="application/pkcs7-signature"
Message-Id: <EE1A9283-BF50-43C9-8308-37ECF1B60363@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
Subject: Re: [Tsvwg] Re: [tcpm] Revision
	ofdraft-larsen-tsvwg-port-randomization
Date: Thu, 26 Jul 2007 10:46:53 -0500
To: "ext Anantha Ramaiah (ananth)" <ananth@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 26 Jul 2007 15:46:59.0768 (UTC)
	FILETIME=[34010B80:01C7CF9C]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: Caitlin Bestler <cait@asomi.com>, tsvwg <tsvwg@ietf.org>,
	Fernando Gont <fernando@gont.com.ar>,
	Murari Sridharan <muraris@microsoft.com>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org


--Apple-Mail-27-999183107
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

Please focus the discussion in this thread around the document draft- 
larsen-tsvwg-port-randomization and start new threads for discussions  
on other topics, such as extending the port number space.

Lars
--Apple-Mail-27-999183107
Content-Transfer-Encoding: base64
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGQDCCAvkw
ggJioAMCAQICEGtxkLFHQu1g67hlmYfwPuIwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ
ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA3MDEwNDE2MTE1NFoXDTA4MDEwNDE2MTE1
NFowXDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVnZ2Vy
dDEkMCIGCSqGSIb3DQEJARYVbGFycy5lZ2dlcnRAbm9raWEuY29tMIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEA26hjntVPZMiwh4d8tyuk9KiucvG92BVUGArk5zO1jhmq7tLFgU1mqcIg
VGumfQqjkAzIuh83kxIiqBrB05Wvxp85apwt4sUCvzMe8mQWzZZZYp0rBzwpOj+VC5pxsMRYtYW+
BaTFBEmvFr7D7C7roZUk0lDppS5SZFs4SQbEe9ykB9aeUf1iTiw2+ikyP2+JEYto14WYCoxFWbms
FbQ1uaaK+yn1WH2YHhyMfi0IOxuT0jtbsngjHJMpWIqq334zBhj+rPSUug47YBHr41FCDMHbbbjv
WbyTyDYneOW3WY8LY8bGWVlAknQGB7lgduShe6e0RI/7SL/VE6X27lM9LwIDAQABozIwMDAgBgNV
HREEGTAXgRVsYXJzLmVnZ2VydEBub2tpYS5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUF
AAOBgQCx3nxxTg/WowobVTRXBiXUEEZj4LBiunWbuAnR0UbJIgijvq3JbiJvZo2gUGiW9LPaHSBz
4oxT1VR/S/6O0a4e87oV5cOQm6ReB68o9rDfUzxHTwoCfv2wwMwBrXyzQMjyQK4Lt8siV41gmZpm
rSXMhjTJdd9uYYNoZKQLq+VM+TCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJ
BgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgG
A1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMg
RGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3
DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3
MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5
KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTCBnzAN
BgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9
fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+
uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMB
Af8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3
dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgG
A1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcP
f6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH
2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8x
ggMQMIIDDAIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAo
UHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ
a3GQsUdC7WDruGWZh/A+4jAJBgUrDgMCGgUAoIIBbzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcB
MBwGCSqGSIb3DQEJBTEPFw0wNzA3MjYxNTQ2NTNaMCMGCSqGSIb3DQEJBDEWBBQhnLURoA63NNkm
cPGDYw2/g8N+zDCBhQYJKwYBBAGCNxAEMXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0ECEGtxkLFHQu1g67hlmYfwPuIwgYcGCyqGSIb3DQEJEAILMXigdjBiMQsw
CQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UE
AxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEGtxkLFHQu1g67hlmYfwPuIw
DQYJKoZIhvcNAQEBBQAEggEATgGyfhFEunOepA30EyethNSbMJzGgTsfN3g/juL4UDFDkxatNIe/
9Wye5EG0P6TdOWld/+h+JtnOSi9mOt4Tjza6wBNZNG4eITlmGG1moWF554AgxvP5ynzvDnJpLRhp
FQT3QV4WWNDAd6BOMe+dlPdLmidJMw8iVPhXeNA+0N9HdOZwqNjxt12Amfkde3cibsdIqMc9jEDv
CLAfaEw0Zp58Amxmkn7NadZVgUoP/zBzc47R5PWdSCyRNDpBxH9DyJ58fj1FruZa3RIjT6p8nao2
Q3K/+aID4G7SBG0U+nsPjbQETZeSpxjJIAKNSNGsIKooz3fqympAwZ7ZoIU+8QAAAAAAAA==

--Apple-Mail-27-999183107--





From tsvwg-bounces@ietf.org Thu Jul 26 11:49:24 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE5ad-00066t-QB; Thu, 26 Jul 2007 11:49:23 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE5ac-00066l-KI
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 11:49:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE5ac-00066d-AY
	for tsvwg@ietf.org; Thu, 26 Jul 2007 11:49:22 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE5ab-0001Sx-43
	for tsvwg@ietf.org; Thu, 26 Jul 2007 11:49:22 -0400
Received: from localhost ([127.0.0.1])
	by psg.com with esmtp (Exim 4.67 (FreeBSD))
	(envelope-from <dpapadimitriou@psg.com>) id 1IE5aV-0008Mn-GD
	for tsvwg@ietf.org; Thu, 26 Jul 2007 15:49:20 +0000
Message-ID: <46A8C277.30606@psg.com>
Date: Thu, 26 Jul 2007 17:49:11 +0200
From: dimitri papadimitriou <dpapadimitriou@psg.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: tsvwg <tsvwg@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -104.4 (---------------------------------------------------)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Subject: [Tsvwg] question on draft-ietf-tsvwg-rsvp-proxy-proto-01.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dpapadimitriou@psg.com, dimitri.papadimitriou@alcatel-lucent.be
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

this version includes use of the notify message:

RFC 3473 states

"The Notify message does not replace existing error messages."

[..]

"Notify messages are most commonly generated at nodes that detect
an error that will trigger the generation of a PathErr or ResvErr
message."

which in practice means "Notify messages" are generated when
conditions stated in RFC 3473 are met but do not replace the
generation of error messages as stated in the same reference

"If a PathErr message is to be generated and a Notify
Request object has been received in the corresponding Path message,
then a Notify message destined to the recorded node SHOULD be
generated. If a ResvErr message is to be generated and a Notify
Request object has been received in the corresponding Resv message,
then a Notify message destined to the recorded node SHOULD be
generated. "

-> question:

could authors clarify Fig.4/scenario of the proxy-proto ?

thanks,
-d.











From tsvwg-bounces@ietf.org Thu Jul 26 12:04:16 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE5oj-0002kG-EU; Thu, 26 Jul 2007 12:03:57 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE5oi-0002jk-39
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 12:03:56 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE5oh-0002jb-P1
	for tsvwg@ietf.org; Thu, 26 Jul 2007 12:03:55 -0400
Received: from smtp.microsoft.com ([131.107.115.214])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE5oh-0000fM-EC
	for tsvwg@ietf.org; Thu, 26 Jul 2007 12:03:55 -0400
Received: from tk1-exhub-c102.redmond.corp.microsoft.com (157.56.116.113) by
	TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with
	Microsoft
	SMTP Server (TLS) id 8.0.700.0; Thu, 26 Jul 2007 09:03:55 -0700
Received: from NA-EXMSG-C110.redmond.corp.microsoft.com ([157.54.62.150]) by
	tk1-exhub-c102.redmond.corp.microsoft.com ([157.56.116.113]) with mapi;
	Thu, 26 Jul 2007 09:03:54 -0700
From: Murari Sridharan <muraris@microsoft.com>
To: Lars Eggert <lars.eggert@nokia.com>, "ext Anantha Ramaiah (ananth)"
	<ananth@cisco.com>
Date: Thu, 26 Jul 2007 09:03:54 -0700
Subject: RE: [Tsvwg] Re: [tcpm] Revision
	ofdraft-larsen-tsvwg-port-randomization
Thread-Topic: [Tsvwg] Re: [tcpm] Revision
	ofdraft-larsen-tsvwg-port-randomization
Thread-Index: AcfPnFg0Qq31n6Q5T6OYqMrbLhCDZQAAcpdA
Message-ID: <FCA794787FDE0D4DBE9FFA11053ECEB60C26A16230@NA-EXMSG-C110.redmond.corp.microsoft.com>
References: <0C53DCFB700D144284A584F54711EC5803B6C65A@xmb-sjc-21c.amer.cisco.com>
	<EE1A9283-BF50-43C9-8308-37ECF1B60363@nokia.com>
In-Reply-To: <EE1A9283-BF50-43C9-8308-37ECF1B60363@nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: Caitlin Bestler <cait@asomi.com>, tsvwg <tsvwg@ietf.org>,
	Fernando Gont <fernando@gont.com.ar>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Aren't these directly related? Port randomization in general is good and ag=
reed not all scenarios exhaust ports but attacks typically are on loaded se=
rvers and proxies, and if ports get exhausted in these key scenarios where =
such a draft makes most sense, what's the point of randomization?

-----Original Message-----
From: Lars Eggert [mailto:lars.eggert@nokia.com]
Sent: Thursday, July 26, 2007 8:47 AM
To: ext Anantha Ramaiah (ananth)
Cc: Caitlin Bestler; tsvwg; Fernando Gont; Murari Sridharan
Subject: Re: [Tsvwg] Re: [tcpm] Revision ofdraft-larsen-tsvwg-port-randomiz=
ation

Please focus the discussion in this thread around the document draft-
larsen-tsvwg-port-randomization and start new threads for discussions
on other topics, such as extending the port number space.

Lars





From tsvwg-bounces@ietf.org Thu Jul 26 12:07:08 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE5rn-0004Zs-W2; Thu, 26 Jul 2007 12:07:07 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE5rm-0004Zm-Fx
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 12:07:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE5rm-0004Ze-6D
	for tsvwg@ietf.org; Thu, 26 Jul 2007 12:07:06 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE5rk-0001yV-HH
	for tsvwg@ietf.org; Thu, 26 Jul 2007 12:07:05 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 26 Jul 2007 18:07:04 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAEljqEaQ/uCKh2dsb2JhbACPaAEBAQgKJw
X-IronPort-AV: i="4.16,584,1175464800"; 
	d="scan'208"; a="149098558:sNHT52714990"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l6QG73t7022217; 
	Thu, 26 Jul 2007 18:07:03 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6QG71kt026464; 
	Thu, 26 Jul 2007 16:07:01 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 18:07:01 +0200
Received: from [130.129.84.245] ([10.61.65.62]) by xfe-ams-331.emea.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 18:07:00 +0200
In-Reply-To: <46A8C277.30606@psg.com>
References: <46A8C277.30606@psg.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <052D6CE1-5EDA-4A33-82E8-9CB00F8211FB@cisco.com>
Content-Transfer-Encoding: 7bit
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
Subject: Re: [Tsvwg] question on draft-ietf-tsvwg-rsvp-proxy-proto-01.txt
Date: Thu, 26 Jul 2007 11:04:01 -0500
To: dpapadimitriou@psg.com, dimitri.papadimitriou@alcatel-lucent.be
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 26 Jul 2007 16:07:00.0802 (UTC)
	FILETIME=[FFE04A20:01C7CF9E]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1344; t=1185466023;
	x=1186330023; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.com>
	|Subject:=20Re=3A=20[Tsvwg]=20question=20on=20draft-ietf-tsvwg-rsvp-proxy
	-proto-01.txt |Sender:=20;
	bh=79ueigVD5jXt+0eqzOR75igI5dbVZg0XtCVO1w9qi8k=;
	b=lbbEEVqeaZax6uwA5jeYIwa4k/KxMA9sQF+BC7+YUxa5Uwr08mfYSxeEpw12wvcslY5dTCPK
	5ausVZdqVikvCx+xUYH9ckYM9dmj5CS30TwSTMIIL5iJRBLtv0yfH7hR;
Authentication-Results: ams-dkim-1; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi Dimitri,

On 26 Jul 2007, at 10:49, dimitri papadimitriou wrote:

> this version includes use of the notify message:
>
> RFC 3473 states
>
> "The Notify message does not replace existing error messages."
>
> [..]
>
> "Notify messages are most commonly generated at nodes that detect
> an error that will trigger the generation of a PathErr or ResvErr
> message."
>
> which in practice means "Notify messages" are generated when
> conditions stated in RFC 3473 are met but do not replace the
> generation of error messages as stated in the same reference
>
> "If a PathErr message is to be generated and a Notify
> Request object has been received in the corresponding Path message,
> then a Notify message destined to the recorded node SHOULD be
> generated. If a ResvErr message is to be generated and a Notify
> Request object has been received in the corresponding Resv message,
> then a Notify message destined to the recorded node SHOULD be
> generated. "
>
> -> question:
>
> could authors clarify Fig.4/scenario of the proxy-proto ?

The scenario and use of Notify is illustrated in Fig 4 and described  
in the text of section 3.2 (above Fig 4).
I believe the operation described there is consistent with the text  
you quoted above.

Cheers

Francois

>
> thanks,
> -d.
>
>
>
>
>
>





From tsvwg-bounces@ietf.org Thu Jul 26 12:08:48 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE5tP-0005pX-9p; Thu, 26 Jul 2007 12:08:47 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE5tO-0005n4-6n
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 12:08:46 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE5tN-0005kC-Oc
	for tsvwg@ietf.org; Thu, 26 Jul 2007 12:08:45 -0400
Received: from mail8.sea5.speakeasy.net ([69.17.117.10])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE5tN-0000kh-C4
	for tsvwg@ietf.org; Thu, 26 Jul 2007 12:08:45 -0400
Received: (qmail 6548 invoked from network); 26 Jul 2007 16:08:44 -0000
Received: from dsl092-045-037.lax1.dsl.speakeasy.net (HELO [66.92.45.37])
	(cait@asomi.com@[66.92.45.37]) (envelope-sender <cait@asomi.com>)
	by mail8.sea5.speakeasy.net (qmail-ldap-1.03) with AES128-SHA encrypted
	SMTP for <lars.eggert@nokia.com>; 26 Jul 2007 16:08:43 -0000
In-Reply-To: <FCA794787FDE0D4DBE9FFA11053ECEB60C26A16230@NA-EXMSG-C110.redmond.corp.microsoft.com>
References: <0C53DCFB700D144284A584F54711EC5803B6C65A@xmb-sjc-21c.amer.cisco.com>
	<EE1A9283-BF50-43C9-8308-37ECF1B60363@nokia.com>
	<FCA794787FDE0D4DBE9FFA11053ECEB60C26A16230@NA-EXMSG-C110.redmond.corp.microsoft.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <B2769A1C-A07E-42BB-8992-1221B4B7151F@asomi.com>
Content-Transfer-Encoding: 7bit
From: Caitlin Bestler <cait@asomi.com>
Subject: Re: [Tsvwg] Re: [tcpm] Revision
	ofdraft-larsen-tsvwg-port-randomization
Date: Thu, 26 Jul 2007 09:08:18 -0700
To: Murari Sridharan <muraris@microsoft.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: "ext Anantha Ramaiah \(ananth\)" <ananth@cisco.com>, tsvwg <tsvwg@ietf.org>,
	Fernando Gont <fernando@gont.com.ar>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org


On Jul 26, 2007, at 9:03 AM, Murari Sridharan wrote:

> Aren't these directly related? Port randomization in general is  
> good and agreed not all scenarios exhaust ports but attacks  
> typically are on loaded servers and proxies, and if ports get  
> exhausted in these key scenarios where such a draft makes most  
> sense, what's the point of randomization?
>
>
Port randomization is admittedly a limited solution, but it is a  
fully compatible solution.
More general solutions, while theoretically better, will likely have  
deployment barriers
that will actually make them even more limited as a solution.






From tsvwg-bounces@ietf.org Thu Jul 26 14:58:35 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE8Xd-0005j6-71; Thu, 26 Jul 2007 14:58:29 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE8XZ-0005ih-MX
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 14:58:25 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE8XZ-0005iX-71; Thu, 26 Jul 2007 14:58:25 -0400
Received: from vapor.isi.edu ([128.9.64.64])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IE8XY-0005GP-Kp; Thu, 26 Jul 2007 14:58:25 -0400
Received: from [130.129.37.253] (dhcp-25fd.ietf69.org [130.129.37.253])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id l6QIw7rU003696;
	Thu, 26 Jul 2007 11:58:07 -0700 (PDT)
Message-ID: <46A8EEB8.2000304@isi.edu>
Date: Thu, 26 Jul 2007 11:58:00 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: Murari Sridharan <muraris@microsoft.com>
Subject: Re: [Tsvwg] Re: [tcpm] Revision
	of	draft-larsen-tsvwg-port-randomization
References: <200702111621.l1BGL6mw029875@venus.xmundo.net>	<0E46EBE9-1C13-44B6-9C04-476D418F5A6D@nokia.com>	<A6CE6259-646E-4C35-9DA3-8911A8CB2B54@nokia.com>
	<FCA794787FDE0D4DBE9FFA11053ECEB60C26A1618E@NA-EXMSG-C110.redmond.corp.microsoft.com>
In-Reply-To: <FCA794787FDE0D4DBE9FFA11053ECEB60C26A1618E@NA-EXMSG-C110.redmond.corp.microsoft.com>
X-Enigmail-Version: 0.95.2
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig60A748F66CFB270C55011486"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: TSV Dir <tsv-dir@ietf.org>, "tcpm@ietf.org" <tcpm@ietf.org>,
	DCCP mailing list <dccp@ietf.org>, tsvwg WG <tsvwg@ietf.org>,
	Fernando Gont <fernando@gont.com.ar>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig60A748F66CFB270C55011486
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable



Murari Sridharan wrote:
> In this context I wanted to bring up a related issue that might also
strengthen this sort of a port randomization proposal.
>=20
> Today the 64k port limitation is starting to become a huge problem
> and
> most often admins add ip addresses to increase the scalability. Given
> that most often the destination port (and sometimes the destination
> address) is well known, the only scalability left is the source address=
=2E
> Increasing ip addresses to improve scalability seems a fairly round
> about approach and frankly doesn't scale well. Given that the 64k limit=

> is not fundamental why not provide a scaling factor similar to the
> receive window to scale the number of usable ports. This also makes
> randomization much more meaningful because in certain proxy scenarios
> the number of connections quickly exhausts the available ports and at
> that point the attacker can simply use any port assuming he can guess
> the source address.

Scale works for windows because of two things:

1) the scale increases the granularity of the window info

2) the scale factor can be negotiated during SYN exchange

Neither is true for ports.

1-p) ports are specific numbers; extended fields could be provided in
options, but that's equivalent to having the port number itself in an
option anyway

2-p) we can negotiate the use of these extended port ranges with
endpoints, but it will break NATs

Portnames is a step in these directions, but is currently experimental
at best. See
http://www.isi.edu/touch/pubs/draft-touch-tcp-portnames-00.txt (to be
updated shortly).

Joe

--=20
----------------------------------------------------------------------
Joe Touch                Sr. Network Engineer, USAF TSAT Space Segment
               Postel Center Director & Research Assoc. Prof., USC/ISI


--------------enig60A748F66CFB270C55011486
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGqO64E5f5cImnZrsRAoCrAJ0UzQJFZPNm3s3bghkL5if/nK9uEgCgueg9
xyb0fVt33Nz2HWxHQ9uoBAY=
=JPbR
-----END PGP SIGNATURE-----

--------------enig60A748F66CFB270C55011486--





From tsvwg-bounces@ietf.org Thu Jul 26 14:59:51 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE8Yv-0008GH-St; Thu, 26 Jul 2007 14:59:49 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE8Yu-00087W-0M
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 14:59:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE8Yt-00086V-Lp; Thu, 26 Jul 2007 14:59:47 -0400
Received: from vapor.isi.edu ([128.9.64.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IE8Ys-0006Rq-Ab; Thu, 26 Jul 2007 14:59:47 -0400
Received: from [130.129.37.253] (dhcp-25fd.ietf69.org [130.129.37.253])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id l6QIxTJt004053;
	Thu, 26 Jul 2007 11:59:30 -0700 (PDT)
Message-ID: <46A8EF0A.1040400@isi.edu>
Date: Thu, 26 Jul 2007 11:59:22 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
Subject: Re: [Tsvwg] Re: [tcpm]
	Revision	ofdraft-larsen-tsvwg-port-randomization
References: <0C53DCFB700D144284A584F54711EC5803B6C62F@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <0C53DCFB700D144284A584F54711EC5803B6C62F@xmb-sjc-21c.amer.cisco.com>
X-Enigmail-Version: 0.95.2
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig203C0F0FD98BF13F0706B39E"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: tcpm@ietf.org, tsvwg WG <tsvwg@ietf.org>, DCCP mailing list <dccp@ietf.org>,
	Fernando Gont <fernando@gont.com.ar>, TSV Dir <tsv-dir@ietf.org>,
	ext@cisco.com, Murari Sridharan <muraris@microsoft.com>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig203C0F0FD98BF13F0706B39E
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable



Anantha Ramaiah (ananth) wrote:
> Murari,
=2E..
> - or do it in piecemeal, first buy more TCP option space, standardize
> any one of the proposals for extending the TCP option space. Then have
> an extended port option like yu suggest below. Then think about other
> TCP fields requiring extension.

The problem is that buying more option space is equivalent to requiring
a whole new TCP header - it has the same problems with backward
compatibility. Previous attempts explored this space, and I think this
was Mark's motivation for a doubled-field TCP header.

Joe

--=20
----------------------------------------------------------------------
Joe Touch                Sr. Network Engineer, USAF TSAT Space Segment
               Postel Center Director & Research Assoc. Prof., USC/ISI


--------------enig203C0F0FD98BF13F0706B39E
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGqO8KE5f5cImnZrsRAmZtAJ9Bu9hfqG1vIYT1LZlPVmURnSI1cACg9Sl/
fDrPJ04LFu9zqIpxgZN8eJE=
=w/YC
-----END PGP SIGNATURE-----

--------------enig203C0F0FD98BF13F0706B39E--





From tsvwg-bounces@ietf.org Thu Jul 26 15:04:23 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE8dK-00046v-Lt; Thu, 26 Jul 2007 15:04:22 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE8dF-00046T-KZ
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 15:04:17 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE8dF-00046L-3K
	for tsvwg@ietf.org; Thu, 26 Jul 2007 15:04:17 -0400
Received: from vapor.isi.edu ([128.9.64.64])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE8dE-0005Ng-LF
	for tsvwg@ietf.org; Thu, 26 Jul 2007 15:04:17 -0400
Received: from [130.129.37.253] (dhcp-25fd.ietf69.org [130.129.37.253])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id l6QJ3rWg005272;
	Thu, 26 Jul 2007 12:03:53 -0700 (PDT)
Message-ID: <46A8F00E.3010904@isi.edu>
Date: Thu, 26 Jul 2007 12:03:42 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: Caitlin Bestler <cait@asomi.com>
Subject: Re: [Tsvwg] Re: [tcpm]
	Revision	ofdraft-larsen-tsvwg-port-randomization
References: <0C53DCFB700D144284A584F54711EC5803B6C65A@xmb-sjc-21c.amer.cisco.com>	<EE1A9283-BF50-43C9-8308-37ECF1B60363@nokia.com>	<FCA794787FDE0D4DBE9FFA11053ECEB60C26A16230@NA-EXMSG-C110.redmond.corp.microsoft.com>
	<B2769A1C-A07E-42BB-8992-1221B4B7151F@asomi.com>
In-Reply-To: <B2769A1C-A07E-42BB-8992-1221B4B7151F@asomi.com>
X-Enigmail-Version: 0.95.2
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig16BE6194D00E34179AF8DD27"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: Murari Sridharan <muraris@microsoft.com>,
	"ext Anantha Ramaiah \(ananth\)" <ananth@cisco.com>,
	tsvwg <tsvwg@ietf.org>, Fernando Gont <fernando@gont.com.ar>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig16BE6194D00E34179AF8DD27
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable



Caitlin Bestler wrote:
>=20
> On Jul 26, 2007, at 9:03 AM, Murari Sridharan wrote:
>=20
>> Aren't these directly related? Port randomization in general is good
>> and agreed not all scenarios exhaust ports but attacks typically are
>> on loaded servers and proxies, and if ports get exhausted in these key=

>> scenarios where such a draft makes most sense, what's the point of
>> randomization?
>>
>>
> Port randomization is admittedly a limited solution, but it is a fully
> compatible solution.
> More general solutions, while theoretically better, will likely have
> deployment barriers
> that will actually make them even more limited as a solution.

Port randomization isn't really a 'solution' to port exhaustion; it's a
BCP-ish recommendation that's like ISN-randomization. It helps a bit and
it's low cost.

Port exhaustion, BTW, also can mean two things:
	a- we need more ports for services
	b- it's too easy to scan all port pairs to attack

Portnames and/or tcp-x2 (I think that's what Mark called it) address the
first issue. The second is, IMO, better addressed with proper security,
rather than haystack-hiding of a needle.

Joe

--=20
----------------------------------------------------------------------
Joe Touch                Sr. Network Engineer, USAF TSAT Space Segment
               Postel Center Director & Research Assoc. Prof., USC/ISI


--------------enig16BE6194D00E34179AF8DD27
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGqPAOE5f5cImnZrsRApOyAKDo/zWHSEe2xagwffrt14KTktDnrwCeNfcn
PeWA+QnC5PiQ1EjMSv6v3Ww=
=ortc
-----END PGP SIGNATURE-----

--------------enig16BE6194D00E34179AF8DD27--





From tsvwg-bounces@ietf.org Thu Jul 26 15:14:02 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE8me-0002cS-Cm; Thu, 26 Jul 2007 15:14:00 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE8mc-0002c7-T1
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 15:13:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE8mc-0002by-JO; Thu, 26 Jul 2007 15:13:58 -0400
Received: from mailc.microsoft.com ([131.107.115.214] helo=smtp.microsoft.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IE8mb-0006kD-AZ; Thu, 26 Jul 2007 15:13:58 -0400
Received: from tk1-exhub-c101.redmond.corp.microsoft.com (157.56.116.111) by
	TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with
	Microsoft
	SMTP Server (TLS) id 8.0.700.0; Thu, 26 Jul 2007 12:13:56 -0700
Received: from NA-EXMSG-C110.redmond.corp.microsoft.com ([157.54.62.150]) by
	tk1-exhub-c101.redmond.corp.microsoft.com ([157.56.116.111]) with mapi;
	Thu, 26 Jul 2007 12:13:54 -0700
From: Murari Sridharan <muraris@microsoft.com>
To: Joe Touch <touch@ISI.EDU>
Date: Thu, 26 Jul 2007 12:13:54 -0700
Subject: RE: [Tsvwg] Re: [tcpm] Revision of
	draft-larsen-tsvwg-port-randomization
Thread-Topic: [Tsvwg] Re: [tcpm] Revision of
	draft-larsen-tsvwg-port-randomization
Thread-Index: AcfPtvQxDsL76unxSIOdk+kp1iUnigAAP8TQ
Message-ID: <FCA794787FDE0D4DBE9FFA11053ECEB60C26A163C0@NA-EXMSG-C110.redmond.corp.microsoft.com>
References: <200702111621.l1BGL6mw029875@venus.xmundo.net>
	<0E46EBE9-1C13-44B6-9C04-476D418F5A6D@nokia.com>
	<A6CE6259-646E-4C35-9DA3-8911A8CB2B54@nokia.com>
	<FCA794787FDE0D4DBE9FFA11053ECEB60C26A1618E@NA-EXMSG-C110.redmond.corp.microsoft.com>
	<46A8EEB8.2000304@isi.edu>
In-Reply-To: <46A8EEB8.2000304@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Spam-Score: -8.0 (--------)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: "tcpm@ietf.org" <tcpm@ietf.org>, tsvwg WG <tsvwg@ietf.org>,
	list <dccp@ietf.org>, Fernando Gont <fernando@gont.com.ar>,
	TSV Dir <tsv-dir@ietf.org>, DCCP
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Agree on the NAT part.

However whether or not its negotiated during SYN exchange would depend on h=
ow it gets specified. For instance (again I really am thinking real-time an=
d aloud here not fully thought thru) we could do something like the followi=
ng. On the SYN packet, the sender picks a port (unscaled)and tries to negot=
iate a scaling option, (NATs that do packet inspection are free to strip th=
is option out) and the destination picks a port and may respond to the scal=
ing. If both sides agreed, then the scaled ports are used for the 4-tupe, i=
f not the unscaled version is used. The only caveat is that while a connect=
ion attempt is in progress to a destination, we cannot be trying the same l=
ocal port, since till the 3-way handshake completes you wont know whether t=
he scaled or the unscaled version is going to be used.

I am not suggesting that scaling ports is a good option, just a thought. I =
will look at the portnames draft.

-----Original Message-----
From: Joe Touch [mailto:touch@ISI.EDU]
Sent: Thursday, July 26, 2007 11:58 AM
To: Murari Sridharan
Cc: tsvwg WG; tcpm@ietf.org; DCCP mailing list; Fernando Gont; TSV Dir
Subject: Re: [Tsvwg] Re: [tcpm] Revision of draft-larsen-tsvwg-port-randomi=
zation



Murari Sridharan wrote:
> In this context I wanted to bring up a related issue that might also
strengthen this sort of a port randomization proposal.
>
> Today the 64k port limitation is starting to become a huge problem and
> most often admins add ip addresses to increase the scalability. Given
> that most often the destination port (and sometimes the destination
> address) is well known, the only scalability left is the source address.
> Increasing ip addresses to improve scalability seems a fairly round
> about approach and frankly doesn't scale well. Given that the 64k
> limit is not fundamental why not provide a scaling factor similar to
> the receive window to scale the number of usable ports. This also
> makes randomization much more meaningful because in certain proxy
> scenarios the number of connections quickly exhausts the available
> ports and at that point the attacker can simply use any port assuming
> he can guess the source address.

Scale works for windows because of two things:

1) the scale increases the granularity of the window info

2) the scale factor can be negotiated during SYN exchange

Neither is true for ports.

1-p) ports are specific numbers; extended fields could be provided in optio=
ns, but that's equivalent to having the port number itself in an option any=
way

2-p) we can negotiate the use of these extended port ranges with endpoints,=
 but it will break NATs

Portnames is a step in these directions, but is currently experimental at b=
est. See http://www.isi.edu/touch/pubs/draft-touch-tcp-portnames-00.txt (to=
 be updated shortly).

Joe

--
----------------------------------------------------------------------
Joe Touch                Sr. Network Engineer, USAF TSAT Space Segment
               Postel Center Director & Research Assoc. Prof., USC/ISI






From tsvwg-bounces@ietf.org Thu Jul 26 15:18:43 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE8rC-00087j-2l; Thu, 26 Jul 2007 15:18:42 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE8rA-00087I-SI
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 15:18:40 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE8rA-000879-HY; Thu, 26 Jul 2007 15:18:40 -0400
Received: from vapor.isi.edu ([128.9.64.64])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IE8rA-0005gV-2r; Thu, 26 Jul 2007 15:18:40 -0400
Received: from [130.129.37.253] (dhcp-25fd.ietf69.org [130.129.37.253])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id l6QJIQYF008992;
	Thu, 26 Jul 2007 12:18:26 -0700 (PDT)
Message-ID: <46A8F37A.8070508@isi.edu>
Date: Thu, 26 Jul 2007 12:18:18 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: Murari Sridharan <muraris@microsoft.com>
Subject: Re: [Tsvwg] Re: [tcpm] Revision
	of	draft-larsen-tsvwg-port-randomization
References: <200702111621.l1BGL6mw029875@venus.xmundo.net>	<0E46EBE9-1C13-44B6-9C04-476D418F5A6D@nokia.com>	<A6CE6259-646E-4C35-9DA3-8911A8CB2B54@nokia.com>
	<FCA794787FDE0D4DBE9FFA11053ECEB60C26A1618E@NA-EXMSG-C110.redmond.corp.microsoft.com>
	<46A8EEB8.2000304@isi.edu>
	<FCA794787FDE0D4DBE9FFA11053ECEB60C26A163C0@NA-EXMSG-C110.redmond.corp.microsoft.com>
In-Reply-To: <FCA794787FDE0D4DBE9FFA11053ECEB60C26A163C0@NA-EXMSG-C110.redmond.corp.microsoft.com>
X-Enigmail-Version: 0.95.2
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigA7FCCDE046A38DBE94473D1B"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: TSV Dir <tsv-dir@ietf.org>, "tcpm@ietf.org" <tcpm@ietf.org>,
	DCCP mailing list <dccp@ietf.org>, tsvwg WG <tsvwg@ietf.org>,
	Fernando Gont <fernando@gont.com.ar>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigA7FCCDE046A38DBE94473D1B
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable



Murari Sridharan wrote:
> Agree on the NAT part.
>=20
> However whether or not its negotiated during SYN exchange would
> depend
> on how it gets specified. For instance (again I really am thinking
> real-time and aloud here not fully thought thru) we could do something
> like the following. On the SYN packet, the sender picks a port
> (unscaled)and tries to negotiate a scaling option, (NATs that do packet=

> inspection are free to strip this option out) and the destination picks=

> a port and may respond to the scaling. If both sides agreed, then the
> scaled ports are used for the 4-tupe, if not the unscaled version is
> used. The only caveat is that while a connection attempt is in progress=

> to a destination, we cannot be trying the same local port, since till
> the 3-way handshake completes you wont know whether the scaled or the
> unscaled version is going to be used.

It can't get negotiated during the SYN; NATs wouldn't track that, and
will break the connection if it 'moves' to another port.

Even if it is in the SYN, it won't allow two hosts to share a port
through a NAT.

It's worth looking at the alternatives which are discussed in Mark's ID
and mine, too.

Joe

--=20
----------------------------------------------------------------------
Joe Touch                Sr. Network Engineer, USAF TSAT Space Segment
               Postel Center Director & Research Assoc. Prof., USC/ISI


--------------enigA7FCCDE046A38DBE94473D1B
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGqPN7E5f5cImnZrsRAi9xAKCHR6WObc01W6PhM6VGPkXASx4BoQCg0wDt
/kfsP+3lUkTHr2VBZihoHPg=
=IMrz
-----END PGP SIGNATURE-----

--------------enigA7FCCDE046A38DBE94473D1B--





From tsvwg-bounces@ietf.org Thu Jul 26 15:30:33 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE92e-0005EF-LI; Thu, 26 Jul 2007 15:30:32 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE92d-0005DD-6W
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 15:30:31 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE92c-0005Ct-I0; Thu, 26 Jul 2007 15:30:30 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IE92c-00061s-4d; Thu, 26 Jul 2007 15:30:30 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-2.cisco.com with ESMTP; 26 Jul 2007 12:30:30 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CABiTqEarR7O6/2dsb2JhbAA
X-IronPort-AV: i="4.16,584,1175497200"; 
	d="scan'208"; a="388472749:sNHT29476488"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6QJUQqf003177; 
	Thu, 26 Jul 2007 12:30:29 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l6QJUL6E014948;
	Thu, 26 Jul 2007 19:30:25 GMT
Received: from xmb-sjc-21c.amer.cisco.com ([171.70.151.176]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 12:30:22 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Tsvwg] Re: [tcpm]
	Revision	ofdraft-larsen-tsvwg-port-randomization
Date: Thu, 26 Jul 2007 12:30:21 -0700
Message-ID: <0C53DCFB700D144284A584F54711EC5803B6C80C@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <46A8EF0A.1040400@isi.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Tsvwg] Re: [tcpm]
	Revision	ofdraft-larsen-tsvwg-port-randomization
Thread-Index: AcfPtx4aHH3a2racRCq9/ufURPV1EAAAHRcA
From: "Anantha Ramaiah \(ananth\)" <ananth@cisco.com>
To: "Joe Touch" <touch@ISI.EDU>
X-OriginalArrivalTime: 26 Jul 2007 19:30:22.0576 (UTC)
	FILETIME=[68B33F00:01C7CFBB]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1505; t=1185478229;
	x=1186342229; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=ananth@cisco.com;
	z=From:=20=22Anantha=20Ramaiah=20\(ananth\)=22=20<ananth@cisco.com>
	|Subject:=20RE=3A=20[Tsvwg]=20Re=3A=20[tcpm]=20Revision=09ofdraft-larsen-
	tsvwg-port-randomization |Sender:=20;
	bh=0obXvOAr+C6z6dOaJp9TBgiJVgWCEUa5YavxVW5IymQ=;
	b=EXfJKeRkt4VcHWXiwVXQjCJcFnEC6gCPNVVgnAT7PAq+2F7bTGejdAC8nF53uLOMNdzGKRun
	aff42b6SYV8oDBD9p4NKjw4hdh93ExMu4784CzB6NqmqWZucctuuUo6T;
Authentication-Results: sj-dkim-2; header.From=ananth@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: tcpm@ietf.org, tsvwg WG <tsvwg@ietf.org>, DCCP mailing list <dccp@ietf.org>,
	Fernando Gont <fernando@gont.com.ar>, TSV Dir <tsv-dir@ietf.org>,
	ext@cisco.com, Murari Sridharan <muraris@microsoft.com>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Lars had sent an email to retain focus on the port randomization and
hence this is going to my last comment... Pl see inline..
=20
>=20
>=20
> Anantha Ramaiah (ananth) wrote:
> > Murari,
> ...
> > - or do it in piecemeal, first buy more TCP option space,=20
> standardize=20
> > any one of the proposals for extending the TCP option=20
> space. Then have=20
> > an extended port option like yu suggest below. Then think=20
> about other=20
> > TCP fields requiring extension.
>=20
> The problem is that buying more option space is equivalent to=20
> requiring a whole new TCP header - it has the same problems=20
> with backward compatibility. Previous attempts explored this=20

New TCP header =3D=3D "Mountain" , IMO this is equivalent to using SCTP =
in
some sense.

TCP option space =3D=3D "Molehill" , this is a "minimal" change with =
"some"
backward compat issues which can be addressed.

If I take your above para seriously, then you are in a way implying that
there is no new TCP options possible :-( or in other words users of TCP
would be rationed to use only a few options in the initial SYN exchange.


-Anantha
> space, and I think this was Mark's motivation for a=20
> doubled-field TCP header.
>=20
> Joe
>=20
> --
> ----------------------------------------------------------------------
> Joe Touch                Sr. Network Engineer, USAF TSAT Space Segment
>                Postel Center Director & Research Assoc. Prof., USC/ISI
>=20
>=20





From tsvwg-bounces@ietf.org Thu Jul 26 15:36:43 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE98c-0002Dg-4S; Thu, 26 Jul 2007 15:36:42 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE98a-0002DL-Rs
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 15:36:40 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE98a-0002DA-H8; Thu, 26 Jul 2007 15:36:40 -0400
Received: from vapor.isi.edu ([128.9.64.64])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IE98a-0006DR-1W; Thu, 26 Jul 2007 15:36:40 -0400
Received: from [130.129.37.253] (dhcp-25fd.ietf69.org [130.129.37.253])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id l6QJaJkw013673;
	Thu, 26 Jul 2007 12:36:19 -0700 (PDT)
Message-ID: <46A8F7AC.5030807@isi.edu>
Date: Thu, 26 Jul 2007 12:36:12 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
References: <0C53DCFB700D144284A584F54711EC5803B6C80C@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <0C53DCFB700D144284A584F54711EC5803B6C80C@xmb-sjc-21c.amer.cisco.com>
X-Enigmail-Version: 0.95.2
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigB40FE59FF3E3FEDED7902CED"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: tcpm@ietf.org, tsvwg WG <tsvwg@ietf.org>, DCCP mailing list <dccp@ietf.org>,
	Fernando Gont <fernando@gont.com.ar>, TSV Dir <tsv-dir@ietf.org>,
	Murari Sridharan <muraris@microsoft.com>
Subject: [Tsvwg] discussion of TCP option space
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigB40FE59FF3E3FEDED7902CED
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

changing the thread as Lars suggested...

Anantha Ramaiah (ananth) wrote:
> Lars had sent an email to retain focus on the port randomization and
> hence this is going to my last comment... Pl see inline..
> =20
>>
>> Anantha Ramaiah (ananth) wrote:
>>> Murari,
>> ...
>>> - or do it in piecemeal, first buy more TCP option space,=20
>> standardize=20
>>> any one of the proposals for extending the TCP option=20
>> space. Then have=20
>>> an extended port option like yu suggest below. Then think=20
>> about other=20
>>> TCP fields requiring extension.
>> The problem is that buying more option space is equivalent to=20
>> requiring a whole new TCP header - it has the same problems=20
>> with backward compatibility. Previous attempts explored this=20
>=20
> New TCP header =3D=3D "Mountain" , IMO this is equivalent to using SCTP=
 in
> some sense.
>=20
> TCP option space =3D=3D "Molehill" , this is a "minimal" change with "s=
ome"
> backward compat issues which can be addressed.

See my other post; it's impossible to extend TCP option space for SYNs,
and SYNs are where they matter.

> If I take your above para seriously, then you are in a way implying tha=
t
> there is no new TCP options possible :-( or in other words users of TCP=

> would be rationed to use only a few options in the initial SYN exchange=
=2E

New options are possible, but only if they are OPTIONAL and we expect
their use to be mutually exclusive with likely SYN options (SACK,
timestamps) or other proposed options. Or we should start making
progress to Mark's idea of just breaking things now.

Joe

--=20
----------------------------------------------------------------------
Joe Touch                Sr. Network Engineer, USAF TSAT Space Segment
               Postel Center Director & Research Assoc. Prof., USC/ISI


--------------enigB40FE59FF3E3FEDED7902CED
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGqPesE5f5cImnZrsRAs4KAKDCwXcYK24XS/Zcd6JuC6PIqRdJGgCfRRuO
btwmijyobcA6XclS2XPAWbQ=
=u06P
-----END PGP SIGNATURE-----

--------------enigB40FE59FF3E3FEDED7902CED--





From tsvwg-bounces@ietf.org Thu Jul 26 15:49:43 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE9LB-0003YB-SV; Thu, 26 Jul 2007 15:49:41 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE9LA-0003TQ-Vy
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 15:49:40 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE9LA-0003R3-JA
	for tsvwg@ietf.org; Thu, 26 Jul 2007 15:49:40 -0400
Received: from psg.com ([147.28.0.62])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE9LA-0006Y9-3y
	for tsvwg@ietf.org; Thu, 26 Jul 2007 15:49:40 -0400
Received: from localhost ([127.0.0.1])
	by psg.com with esmtp (Exim 4.67 (FreeBSD))
	(envelope-from <dpapadimitriou@psg.com>)
	id 1IE9L3-0002d9-Qh; Thu, 26 Jul 2007 19:49:39 +0000
Message-ID: <46A8FACA.8050409@psg.com>
Date: Thu, 26 Jul 2007 21:49:30 +0200
From: dimitri papadimitriou <dpapadimitriou@psg.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Francois Le Faucheur IMAP <flefauch@cisco.com>
Subject: Re: [Tsvwg] question on draft-ietf-tsvwg-rsvp-proxy-proto-01.txt
References: <46A8C277.30606@psg.com>
	<052D6CE1-5EDA-4A33-82E8-9CB00F8211FB@cisco.com>
In-Reply-To: <052D6CE1-5EDA-4A33-82E8-9CB00F8211FB@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -104.4 (---------------------------------------------------)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: dimitri.papadimitriou@alcatel-lucent.be, tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dpapadimitriou@psg.com, dimitri.papadimitriou@alcatel-lucent.be
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

hi francois,


indeed but more precisely what deserves imho clarification is

o) since you are reflecting the Notify request object value from the 
incoming Notify request object in the Path message, the Notify msg sent 
to the source is the one associated to the Resv

hence that notify includes the following information

<downstream notify session> ::= <SESSION> [<POLICY_DATA>...]
                                 <flow descriptor list>

sent now upstream towards the sender

o) there is apparently no need to generate notify on PathErr (the notify 
request object transported in the Path msg is only there to be reflected 
in the Resv msg) while as indicated in the extracts the RFC 3473 refers 
to a SHOULD

o) implication of the above two points is that the receiver is also not 
able to include its own Notify Request object, indeed RFC 3473 mentions
"If a message contains multiple Notify_Request objects, only the first
object is meaningful."


i think this would facilitate code re-use and prevent interop issues.

(as examples i have seen some implementations injecting a Notify Request 
object but not able to Ack (when requested) towards a destination or 
simply not able to process the Error node address in the error spec objecy)

thanks,
-d.

Francois Le Faucheur IMAP wrote:
> Hi Dimitri,
> 
> On 26 Jul 2007, at 10:49, dimitri papadimitriou wrote:
> 
>> this version includes use of the notify message:
>>
>> RFC 3473 states
>>
>> "The Notify message does not replace existing error messages."
>>
>> [..]
>>
>> "Notify messages are most commonly generated at nodes that detect
>> an error that will trigger the generation of a PathErr or ResvErr
>> message."
>>
>> which in practice means "Notify messages" are generated when
>> conditions stated in RFC 3473 are met but do not replace the
>> generation of error messages as stated in the same reference
>>
>> "If a PathErr message is to be generated and a Notify
>> Request object has been received in the corresponding Path message,
>> then a Notify message destined to the recorded node SHOULD be
>> generated. If a ResvErr message is to be generated and a Notify
>> Request object has been received in the corresponding Resv message,
>> then a Notify message destined to the recorded node SHOULD be
>> generated. "
>>
>> -> question:
>>
>> could authors clarify Fig.4/scenario of the proxy-proto ?
> 
> The scenario and use of Notify is illustrated in Fig 4 and described in 
> the text of section 3.2 (above Fig 4).
> I believe the operation described there is consistent with the text you 
> quoted above.
> 
> Cheers
> 
> Francois
> 
>>
>> thanks,
>> -d.
>>
>>
>>
>>
>>
>>
> 
> .
> 





From tsvwg-bounces@ietf.org Thu Jul 26 23:23:19 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEGPp-0001le-5h; Thu, 26 Jul 2007 23:22:57 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IEGPo-0001kr-3P
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 23:22:56 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEGPn-0001ki-OB
	for tsvwg@ietf.org; Thu, 26 Jul 2007 23:22:55 -0400
Received: from psg.com ([147.28.0.62])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IEGPm-0007b9-U4
	for tsvwg@ietf.org; Thu, 26 Jul 2007 23:22:55 -0400
Received: from localhost ([127.0.0.1])
	by psg.com with esmtp (Exim 4.67 (FreeBSD))
	(envelope-from <dpapadimitriou@psg.com>)
	id 1IEGPe-000IPH-EE; Fri, 27 Jul 2007 03:22:52 +0000
Message-ID: <46A96502.1070901@psg.com>
Date: Fri, 27 Jul 2007 05:22:42 +0200
From: dimitri papadimitriou <dpapadimitriou@psg.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
Subject: Re: [Tsvwg] Re: terminology issues in draft-floyd-tsvwg-besteffort
	- flat monthly pricing
References: <5.2.1.1.2.20070726141117.04e7a828@pop3.jungle.bt.co.uk>
In-Reply-To: <5.2.1.1.2.20070726141117.04e7a828@pop3.jungle.bt.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -104.4 (---------------------------------------------------)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c
Cc: tsvwg IETF list <tsvwg@ietf.org>, Mark Allman <mallman@icir.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dpapadimitriou@psg.com, dimitri.papadimitriou@alcatel-lucent.be
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

bob

you wrote:

"so there won't be sufficient incentives for anyone to invest in more 
capacity for those of us who want to use the Internet responsibly."

this might be indeed a concern

but as shorter life socialist ;-) i do also strongly believe that before 
discussing the solution space we should first within the IETF community 
at large come with a good, clear, and common understanding whether this 
is a concern or not, if this is the case how important & urgent it might 
be, have better understanding about of some of the root causes, etc.

-d.

Bob Briscoe wrote:
> Sally,
> 
> I just realised that I should have added a very important point about 
> "who controls the choice" to the rather philosophical response below.
> 
> I'm trying to make sure we at the IETF don't have to decide whether the 
> Internet more favours rich people, malicious people or selfish people. 
> I'm trying to make it so what you think or what I think about this 
> doesn't matter (at least any more than what everyone else in the world 
> thinks).
> 
> Firstly, what I'm proposing would sit alongside the current Internet 
> (re-ECN packets are distinguishable from non-re-ECN packets, so they 
> effectively partition all traffic orthogonally to Diffserv).
> 
> Secondly, one partition would be the current Internet, with all its 
> vulnerabilites to selfish and malicious users as well as all its 
> strengths. The other partition would be this new proposal where the 
> market and social governance can control the way the Internet shares out 
> resources.
> 
> At a grander level, the choice of how much resource each of the two 
> partitions gets would be under the direct control of ISPs, but in turn 
> their choices are also affected by the market and perhaps by social 
> control through government regulation.
> 
> I know this fits your preferred model of how new resource allocation 
> strategies should be added to the Internet. The question is whether it 
> is sufficiently important to use IP header space to provide this choice. 
> We don't need to decide that now, but we do need to debate it widely - 
> more widely than tsvwg.
> 
> 
> Bob
> 
> At 18:16 24/07/2007, Sally Floyd wrote:
>>> 3/ User pricing: Flat monthly (in our simplest effective proposal).
>>>
>>> Please don't imply we're advocating user congestion pricing, given 
>>> the whole reason we brought re-ECN to the IETF back in 2005 was 
>>> because we found a way to limit congestion without constraining how 
>>> operators price their services to their customers. Specifically, 
>>> re-ECN is designed to work with flat monthly pricing.
>>
>> This draft is not about re-ECN.  It is about the usefulness of
>> "simple best-effort traffic", and the usefulness of flow-rate fairness
>> for simple best-effort traffic.
>>
>> This draft is not about the presence or absence of flat monthly
>> pricing for users.  One could have flat monthly pricing with no
>> other limitations, one could have flat monthly pricing with volume
>> limits, or one could have flat monthly pricing with some form of
>> "you get what you pay for".  The first two forms don't result in
>> "rich" users getting all of the bandwidth in times of high congestion
>> (e.g., after the earthquake).  The third form easily could.  E.g.,
>> if all of the traffic was "you get what you pay for", even with
>> flat monthly fees, then it could be really expensive to send packets
>> in the time interval after the earthquake, or some other highly-congested
>> period, and only the rich would be able to send packets.  I would
>> be opposed to setting such a "you get what you pay for" goal as the
>> overriding goal for the global Internet, with or without flat monthly
>> fees.
> 
> I know. It's distasteful to me to (I am a life-long socialist). But the 
> alternatives are worse. I have thought about this long and hard.
> 
> On the demand side: If the rich don't get to be able to buy the right to 
> use capacity, the alternative is that the malicious and selfish get to 
> drive out those trying to be sociable in their use of the Internet. And 
> that's for always, not just during earthquakes. Also, the lack of any 
> resource sharing arbitration will lead to a vacuum that will be filled 
> by the rich and powerful (which is what deep packet inspection 
> represents - those with power and influence controlling what can and 
> can't be done on the Internet).
> 
> On the supply side: The malicious and selfish will use the Internet 
> excessively, but not pay their share, so there won't be sufficient 
> incentives for anyone to invest in more capacity for those of us who 
> want to use the Internet responsibly.
> 
> In summary, a knee-jerk reaction against a market mechanism needs to be 
> tempered by the thought of what will otherwise fill the vacuum - the 
> lesson of the Soviet Union?
> 
> However, you will notice in my draft on fairness (and in my design of 
> re-ECN) that I have been careful to enable more equitable resource 
> allocation schemes locally. This can give _true_ equality, whereas flow 
> rate equality is just a license for the selfish and malicious to take 
> what they want.
> 
> Overall, I put my hands up and admit it: we don't have a better system 
> for allocating resources on planet scale than a market. I wish we did. 
> We do have better resource sharing capabilities locally though, and I 
> want to enable them.
> 
> 
> Bob
> 
> 
>> - Sally
>> http://www.icir.org/floyd/
> 
> ____________________________________________________________________________ 
> 
> Notice: This contribution is the personal view of the author and does 
> not necessarily reflect the technical nor commercial direction of BT plc.
> ____________________________________________________________________________ 
> 
> Bob Briscoe,                           Networks Research Centre, BT 
> Research
> B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 
> 645196 
> 
> 
> 
> 
> .
> 





From tsvwg-bounces@ietf.org Fri Jul 27 08:37:34 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEP4J-0007bD-BW; Fri, 27 Jul 2007 08:37:19 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IEP4G-0007Yp-F0
	for tsvwg-confirm+ok@megatron.ietf.org; Fri, 27 Jul 2007 08:37:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEP4G-0007X8-3e; Fri, 27 Jul 2007 08:37:16 -0400
Received: from gw.openss7.com ([142.179.199.224])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IEP4D-0002x0-2e; Fri, 27 Jul 2007 08:37:16 -0400
Received: from ns.pigworks.openss7.net
	(IDENT:VBDa2sI9qKd4ESgD5Rq5JTPzPUFzBXN+@ns1.evil.openss7.net
	[192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id l6RCb8M23746;
	Fri, 27 Jul 2007 06:37:08 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id l6RCb5v13418;
	Fri, 27 Jul 2007 06:37:05 -0600
Date: Fri, 27 Jul 2007 06:37:05 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: =?iso-8859-1?Q?=B3=C2=D0=F1?= <chenxu@chinamobile.com>
Message-ID: <20070727063705.A13093@openss7.org>
Mail-Followup-To: =?iso-8859-1?Q?=B3=C2=D0=F1?= <chenxu@chinamobile.com>,
	Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
	SIGTRAN <sigtran@ietf.org>, TSWG <tsvwg@ietf.org>
References: <OF24565732.6AADA0AB-ON48257325.00301996@chinamobile.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF24565732.6AADA0AB-ON48257325.00301996@chinamobile.com>;
	from chenxu@chinamobile.com on Fri, Jul 27, 2007 at 04:45:12PM
	+0800
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id
	l6RCb8M23746
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
	SIGTRAN <sigtran@ietf.org>, TSWG <tsvwg@ietf.org>
Subject: [Tsvwg] Re: [Sigtran] The requiremnts and
	proposalsforM2PA/M3UA/SCTPExtension from China Mobile
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bidulock@openss7.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Chen,

=B3=C2=D0=F1 wrote:                                  (Fri, 27 Jul 2007 16=
:45:12)
> Dear Michael Tuexen,
>=20
> =09
> >    1. What does "unionize of the primary paths between nodes" mean?
> It means=A3=ACfor one multi-homed SCTP endpoint,the primary path=A3=A8s=
ource
> IP address=3DIP1---destination IP=3DIP2=A3=A9 shall be the same as the =
remote
> endpoint's ( source IP address=3DIP2---destination IP=3DIP1  )  =20
>   =20
> Many venders implement Multi-homing in the following way:
>=20
> one multi-homed SCTP endpoint has two local IP addresses(IP1/IP2) and
> two remote IP address(IP3/IP4) within an association.  There's two
> paths within an association:IP1-IP3,and IP2-IP4.not 4 paths.=20

That sounds rather foolish.  What I do is as follows:

  When sending to IP3, choose the best route (metric) to IP3.
  If no route to IP3 exists, don't send to IP3, send to another
    destination for the association.
  If a route to IP3 exists, and the source address of the outbound
    interface of this route includes a local address for the
    association, use that as the source address when using the route.
    Otherwise, use the first source address of the association.

  When sending to IP4, choose the best route (metric) to IP4.
  If no route to IP4 exists, don't send to IP4, send to another
    destination for the association.
  If a route to IP4 exists, and the source address of the outbound
    interface of this route includes a local address for the
    association, use that as the source address when using the route.
    Otherwise, use the first source address of the association.

This only results in IP1-IP3 and IP2-IP4 if the only route to IP3 is
from an interface with IP1 and the only route to IP4 is from an
interface with IP2.

>   =20
> For example, endpoint1 has two local IP addresses(IP1/IP2)=A3=AC and
> endpoint2 has two local IP addresses(IP3/IP4).
>=20
> if two endpoints' primary path isn't the same,that is endpoint1 use
> IP1-IP3 as the primary path, use IP2-IP4 as the second path;
> endpoint2 use IP3-IP2 as the primary path, use IP4-IP1 as the second
> path.=20
>=20
> These two endpoints can't  send data to each other successfully. =20

Yes, it is possible to set up your routing tables on two host so that
the cannot communicate.  This is even possible with TCP.

If the problem is not merely routing table, I suggest you choose another
vendor or work with your existing vendor to correct the deficiencies in
their implementation.

>        =20
>=20
> >     2. Not sure about the SACK issue: You are currently allowed to
> >    send the SACK back to an addresses different from the source
> >    address of the corresponding DATA chunk. As far as I know
> >    it is only a SHOULD describing that you send the SACK back
> >    to the source address of the DATA chunk.
>=20
> You are right,it is only a SHOULD describing that you send the SACK
> back to the source address of the DATA chunk in RFC2960.  That's why
> we get in trouble in multi-homing situation.  If the  path to the
> source address of the DATA chunk is unreachable=A3=ACthe sack can't sen=
d
> to the remote endpoint for ever although the other path is
> available.Soon the other path will be failure.

Well, no, not in the reasonable implementation.  When SACKs are being
sent to a destination and are not reaching the peer endpoint, a
retransmission timeout will result in duplicate TSNs being sent.  The
peer receiving duplicate TSNs should realized that their SACKs are
likely being sent into a black hole and begin sending SACKs to a
different destination.  This is already in RFC 2960:

6.4 Multi-homed SCTP Endpoints

   ...

   When a receiver of a duplicate DATA chunk sends a SACK to a multi-
   homed endpoint it MAY be beneficial to vary the destination address
   and not use the source address of the DATA chunk.  The reason being
   that receiving a duplicate from a multi-homed endpoint might indicate
   that the return path (as specified in the source address of the DATA
   chunk) for the SACK is broken.

   ...

If your current vendor does not implement this, I suggest that you
request them to do so.

--brian

--=20
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/





From tsvwg-bounces@ietf.org Fri Jul 27 08:51:35 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEPI3-00063y-EO; Fri, 27 Jul 2007 08:51:31 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IEPEH-0000mM-4t
	for tsvwg-confirm+ok@megatron.ietf.org; Fri, 27 Jul 2007 08:47:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEPEG-0000mE-RM
	for tsvwg@ietf.org; Fri, 27 Jul 2007 08:47:36 -0400
Received: from wx-out-0506.google.com ([66.249.82.236])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEPEF-0003BT-Cp
	for tsvwg@ietf.org; Fri, 27 Jul 2007 08:47:36 -0400
Received: by wx-out-0506.google.com with SMTP id h27so724344wxd
	for <tsvwg@ietf.org>; Fri, 27 Jul 2007 05:47:35 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=Xg/ya1CSjXmV7uIiFaZjowsWtlxqJc22YDSsowXHtyC+5OLiR7xnBnaXpy/cfrtdT93hLj7aFkLdrFfhLeZVc1kT66zpvmQU0n+FuONp19HsuPUBQ5to9FHiAamzZZsskkOZ6pJpuLd4XlvGxXROKLI0SI6EhMlWtheDBRoThxU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=iMyN2bZEa/wEK7YW2KMu/ZMva8ZB9pVsWZPpXy0wwYqshi+F1SW2SMC+Z+H/YImHkGvIy4rq1O9iwwFBQaMRp3RchtO2bgPVP8tb5Y7KWQfR3dPWNna2VcOc5jq+bJBdZy6BXOrFjOb3t3MOAHCQjoLjMwkkyy66JUcmROs8yjU=
Received: by 10.100.119.14 with SMTP id r14mr2577487anc.1185540454693;
	Fri, 27 Jul 2007 05:47:34 -0700 (PDT)
Received: by 10.90.83.12 with HTTP; Fri, 27 Jul 2007 05:47:34 -0700 (PDT)
Message-ID: <6dbbbf160707270547q4ddde312g95feca7dde736e6b@mail.gmail.com>
Date: Fri, 27 Jul 2007 18:17:34 +0530
From: "Ankit Kumar Sharma" <ankisharma@gmail.com>
To: "=?GB2312?B?s8LQ8Q==?=" <chenxu@chinamobile.com>
In-Reply-To: <OF24565732.6AADA0AB-ON48257325.00301996@chinamobile.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_5001_105760.1185540454561"
References: <OF24565732.6AADA0AB-ON48257325.00301996@chinamobile.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 64592953d6410e1f725ee21266e2f396
X-Mailman-Approved-At: Fri, 27 Jul 2007 08:51:29 -0400
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
	SIGTRAN <sigtran@ietf.org>, TSWG <tsvwg@ietf.org>
Subject: [Tsvwg] Re: Re: [Sigtran] The requiremnts and
	proposalsforM2PA/M3UA/SCTPExtension from China Mobile
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

------=_Part_5001_105760.1185540454561
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: base64
Content-Disposition: inline

Y2hlbnh1LAoKT24gNy8yNy8wNywgs8LQ8SA8Y2hlbnh1QGNoaW5hbW9iaWxlLmNvbT4gd3JvdGU6
Cj4KPiBEZWFyIE1pY2hhZWwgVHVleGVuLAo+Cj4KPiA+ICAgIDEuIFdoYXQgZG9lcyAidW5pb25p
emUgb2YgdGhlIHByaW1hcnkgcGF0aHMgYmV0d2VlbiBub2RlcyIgbWVhbj8KPiAgICBJdCBtZWFu
c6OsZm9yIG9uZSBtdWx0aS1ob21lZCBTQ1RQIGVuZHBvaW50LHRoZSBwcmltYXJ5IHBhdGijqHNv
dXJjZSBJUAo+IGFkZHJlc3M9SVAxLS0tZGVzdGluYXRpb24gSVA9SVAyo6kgc2hhbGwgYmUgdGhl
IHNhbWUgYXMgdGhlIHJlbW90ZSBlbmRwb2ludCdzCj4gKCBzb3VyY2UgSVAgYWRkcmVzcz1JUDIt
LS1kZXN0aW5hdGlvbiBJUD1JUDEgICkKPgo+ICAgIE1hbnkgdmVuZGVycyBpbXBsZW1lbnQgTXVs
dGktaG9taW5nIGluIHRoZSBmb2xsb3dpbmcgd2F5Ogo+Cj4gICAgIG9uZSBtdWx0aS1ob21lZCBT
Q1RQIGVuZHBvaW50IGhhcyB0d28gbG9jYWwgSVAgYWRkcmVzc2VzKElQMS9JUDIpIGFuZAo+IHR3
byByZW1vdGUgSVAgYWRkcmVzcyhJUDMvSVA0KSB3aXRoaW4gYW4gYXNzb2NpYXRpb24uCj4gICAg
IFRoZXJlJ3MgdHdvIHBhdGhzIHdpdGhpbiBhbiBhc3NvY2lhdGlvbjpJUDEtSVAzLGFuZCBJUDIt
SVA0Lm5vdCA0Cj4gcGF0aHMuCj4KPiAgICAgRm9yIGV4YW1wbGUsIGVuZHBvaW50MSBoYXMgdHdv
IGxvY2FsIElQIGFkZHJlc3NlcyhJUDEvSVAyKaOsIGFuZAo+IGVuZHBvaW50MiBoYXMgdHdvIGxv
Y2FsIElQIGFkZHJlc3NlcyhJUDMvSVA0KS4KPgo+IGlmIHR3byBlbmRwb2ludHMnIHByaW1hcnkg
cGF0aCBpc24ndCB0aGUgc2FtZSx0aGF0IGlzIGVuZHBvaW50MSB1c2UKPiBJUDEtSVAzIGFzIHRo
ZSBwcmltYXJ5IHBhdGgsIHVzZSBJUDItSVA0IGFzIHRoZSBzZWNvbmQgcGF0aDsgIGVuZHBvaW50
MiB1c2UKPiBJUDMtSVAyIGFzIHRoZSBwcmltYXJ5IHBhdGgsIHVzZSBJUDQtSVAxIGFzIHRoZSBz
ZWNvbmQgcGF0aC4KPgo+ICAgICBUaGVzZSB0d28gZW5kcG9pbnRzIGNhbid0ICBzZW5kIGRhdGEg
dG8gZWFjaCBvdGhlciBzdWNjZXNzZnVsbHkuCj4KID4gICAgIDIuIE5vdCBzdXJlIGFib3V0IHRo
ZSBTQUNLIGlzc3VlOiBZb3UgYXJlIGN1cnJlbnRseSBhbGxvd2VkIHRvCgo+ID4gICAgc2VuZCB0
aGUgU0FDSyBiYWNrIHRvIGFuIGFkZHJlc3NlcyBkaWZmZXJlbnQgZnJvbSB0aGUgc291cmNlCj4g
PiAgICBhZGRyZXNzIG9mIHRoZSBjb3JyZXNwb25kaW5nIERBVEEgY2h1bmsuIEFzIGZhciBhcyBJ
IGtub3cKPiA+ICAgIGl0IGlzIG9ubHkgYSBTSE9VTEQgZGVzY3JpYmluZyB0aGF0IHlvdSBzZW5k
IHRoZSBTQUNLIGJhY2sKPiA+ICAgIHRvIHRoZSBzb3VyY2UgYWRkcmVzcyBvZiB0aGUgREFUQSBj
aHVuay4KPgo+ICAgICAgWW91IGFyZSByaWdodCxpdCBpcyBvbmx5IGEgU0hPVUxEIGRlc2NyaWJp
bmcgdGhhdCB5b3Ugc2VuZCB0aGUgU0FDSwo+IGJhY2sKPiAgICB0byB0aGUgc291cmNlIGFkZHJl
c3Mgb2YgdGhlIERBVEEgY2h1bmsgaW4gUkZDMjk2MC4KPiAgICAgICBUaGF0J3Mgd2h5IHdlIGdl
dCBpbiB0cm91YmxlIGluIG11bHRpLWhvbWluZyBzaXR1YXRpb24uCj4gICAgICAgSWYgdGhlICBw
YXRoIHRvIHRoZSBzb3VyY2UgYWRkcmVzcyBvZiB0aGUgREFUQSBjaHVuayBpcwo+IHVucmVhY2hh
Ymxlo6x0aGUgc2FjayBjYW4ndCBzZW5kIHRvIHRoZSByZW1vdGUgZW5kcG9pbnQgZm9yIGV2ZXIg
YWx0aG91Z2ggdGhlCj4gb3RoZXIgcGF0aCBpcyBhdmFpbGFibGUuU29vbiB0aGUgb3RoZXIgcGF0
aCB3aWxsIGJlIGZhaWx1cmUuCgoKSSBkb24ndCBzZWUgYW55IHByb2JsZW0gaW4gU0NUUCBSRkMg
Zm9yIGFib3ZlIG1lbnRpb25lZCBzY2VuYXJpby4KQXMgcGVyIFJGQyAyNzE5LCBmb2xsb3dpbmcg
aXMgdGhlIGRlZmluYXRpb24gb2YgIlNIT1VMRCI6CgozLiBTSE9VTEQgICBUaGlzIHdvcmQsIG9y
IHRoZSBhZGplY3RpdmUgIlJFQ09NTUVOREVEIiwgbWVhbiB0aGF0IHRoZXJlCiAgbWF5IGV4aXN0
IHZhbGlkIHJlYXNvbnMgaW4gcGFydGljdWxhciBjaXJjdW1zdGFuY2VzIHRvIGlnbm9yZSBhCiAg
IHBhcnRpY3VsYXIgaXRlbSwgYnV0IHRoZSBmdWxsIGltcGxpY2F0aW9ucyBtdXN0IGJlIHVuZGVy
c3Rvb2QgYW5kCgogICBjYXJlZnVsbHkgd2VpZ2hlZCBiZWZvcmUgY2hvb3NpbmcgYSBkaWZmZXJl
bnQgY291cnNlLgoKCgpOb3cgcGxlYXNlIGxvb2sgYXQgZm9sbG93aW5nIGV4Y2VycHQgZnJvbSBz
ZWN0aW9uIDYuNChNdWx0aS1ob21lZCBTQ1RQCkVuZHBvaW50cykgb2YgU0NUUCBSRkM6CiIKCldo
ZW4gYSByZWNlaXZlciBvZiBhIGR1cGxpY2F0ZSBEQVRBIGNodW5rIHNlbmRzIGEgU0FDSyB0byBh
IG11bHRpLQogICBob21lZCBlbmRwb2ludCBpdCBNQVkgYmUgYmVuZWZpY2lhbCB0byB2YXJ5IHRo
ZSBkZXN0aW5hdGlvbiBhZGRyZXNzCiAgIGFuZCBub3QgdXNlIHRoZSBzb3VyY2UgYWRkcmVzcyBv
ZiB0aGUgREFUQSBjaHVuay4gIFRoZSByZWFzb24gYmVpbmcKCiAgIHRoYXQgcmVjZWl2aW5nIGEg
ZHVwbGljYXRlIGZyb20gYSBtdWx0aS1ob21lZCBlbmRwb2ludCBtaWdodCBpbmRpY2F0ZQogICB0
aGF0IHRoZSByZXR1cm4gcGF0aCAoYXMgc3BlY2lmaWVkIGluIHRoZSBzb3VyY2UgYWRkcmVzcyBv
ZiB0aGUgREFUQQogICBjaHVuaykgZm9yIHRoZSBTQUNLIGlzIGJyb2tlbi4KIgoKU28gYXMgcGVy
IHlvdXIgc2NlbmFyaW8sIGlmIFNPVVJDRSBhZGRyZXNzIG9mIHNlbmRlciBpcyBub3QgcmVhY2hh
YmxlIHRoZW4Kb3VyIFNBQ0sgd291bGQgYmUgbG9zdC4gQWZ0ZXIgUlRPIGV4cGlyeSBhdCBzZW5k
ZXIsIHNlbmRlciB3b3VsZCBhZ2FpbiB0cnkKdG8gc2VuZCB0aGUgREFUQSBjaHVuay4gTm93LCBy
ZWNlaXZlciBjb3VsZCBiZWhhdmUgYXMgcGVyIGFib3ZlIG1lbnRpb25lZApleGNlcnB0LgoKQmVz
dCBSZWdhcmQKPiBDaGVuIFh1Cj4gQ2hpbmEgTW9iaWxlCj4gY2hlbnh1QGNoaW5hbW9iaWxlLmNv
bQo+Cj4KPgo+Cj4KPgo+Cj4gPT09PT09PSAyMDA3LTA3LTI2IDIyOjIzOjIwIMT61NrAtNDF1tDQ
tLXAo7o9PT09PT09Cj4KPiA+RGVhciBhbGwsCj4gPgo+ID5JJ20gc2VuZGluZyB0aGlzIGFsc28g
dG8gVFNWV0csIHNpbmNlIHRoZSBTQ1RQIGRpc2N1c3Npb24gaGFzIHRvIGJlCj4gPmRvbmUgdGhl
IHRoYXQgV0cuCj4gPgo+ID5BZGRyZXNzaW5nIHRoZSBTQ1RQIHN0YXRlbWVudDoKPiA+Cj4gPjEu
IFdoYXQgZG9lcyAidW5pb25pemUgb2YgdGhlIHByaW1hcnkgcGF0aHMgYmV0d2VlbiBub2RlcyIg
bWVhbj8KPiA+Mi4gTm90IHN1cmUgYWJvdXQgdGhlIFNBQ0sgaXNzdWU6IFlvdSBhcmUgY3VycmVu
dGx5IGFsbG93ZWQgdG8KPiA+ICAgIHNlbmQgdGhlIFNBQ0sgYmFjayB0byBhbiBhZGRyZXNzZXMg
ZGlmZmVyZW50IGZyb20gdGhlIHNvdXJjZQo+ID4gICAgYWRkcmVzcyBvZiB0aGUgY29ycmVzcG9u
ZGluZyBEQVRBIGNodW5rLiBBcyBmYXIgYXMgSSBrbm93Cj4gPiAgICBpdCBpcyBvbmx5IGEgU0hP
VUxEIGRlc2NyaWJpbmcgdGhhdCB5b3Ugc2VuZCB0aGUgU0FDSyBiYWNrCj4gPiAgICB0byB0aGUg
c291cmNlIGFkZHJlc3Mgb2YgdGhlIERBVEEgY2h1bmsuCj4gPgo+ID5CZXN0IHJlZ2FyZHMKPiA+
TWljaGFlbAo+ID4KPiA+T24gSnVsIDI2LCAyMDA3LCBhdCA0OjIyIEFNLCBjaGVueHUgd3JvdGU6
Cj4gPgo+ID4+IERlYXIgYWxsLAo+ID4+Cj4gPj4gICAgICBTb3JyeSB0byBzdWJtaXQgdGhlIHJh
ciBmaWxlISBBbmQgdGhhbmtzIFJ1aSBHb21lcyEKPiA+Pgo+ID4+IFRoZSBjb250ZW50cyBvZiB0
aGUgYXR0YWNobWVudHMgYXJlIGFzIGZvbGxvd3M6Cj4gPj4KPiA+PiAgID09PT09PT09PT09PT09
PT09PT09PT09PT09PT09Cj4gPj4gICBmb3IgU0NUUCBvZiBDaGluYSBNb2JpbGUucHB0Cj4gPj4g
ID09PT09PT09PT09PT09PT09PT09PT09PT09PT09Cj4gPj4KPiA+PiAgVGhlIFJlcXVpcmVtZW50
IGFuZCBQcm9wb3NhbAo+ID4+ICAgZm9yIFNDVFAgU3BlY2lmaWNhdGlvbiBFeHRlbnNpb24KPiA+
PiAgIG9mIENoaW5hIE1vYmlsZQo+ID4+Cj4gPj4gIENoZW4gWHUgLCBaaGFuZyBIYW8KPiA+PiAg
Q2hpbmEgTW9iaWxlCj4gPj4KPiA+PiAgQ29udGVudAo+ID4+Cj4gPj4gIEJhY2tncm91bmQKPiA+
PiAgUHJvYmxlbSBkZXNjcmlwdGlvbgo+ID4+ICBSZXF1aXJlbWVudCBmb3IgU3VwcGxlbWVudCBv
ZiBSRkM0NDYwCj4gPj4gIFByb3Bvc2FsIGZvciBTdXBwbGVtZW50IG9mIFJGQzQ0NjAKPiA+Pgo+
ID4+ICBCYWNrZ3JvdW5kCj4gPj4KPiA+PiAgVGhlIHdvcmxkIHRyZW5kIG9mIElQIGJlYXJlciBm
b3Igc2lnbmFsbGluZyB3aWxsIG1ha2UgU0lHVFJBTgo+ID4+ICBzdGFuZGFyZCB3aWRlbHkgdXNl
ZCBpbiBzaWduYWxsaW5nIG5ldHdvcmsuCj4gPj4gIFRyYWRpdGlvbmFsIGFuZCBuZXcgVGVsZWNv
bSBjYXJyaWVycyBpbXBsZW1lbnQgc2lnbmFsbGluZyBvdmVyIElQIHRvCj4gPj4gIFJlZHVjZSAg
Y29zdCBmb3IgZXh0ZW5kZWQgY2FwYWNpdHkKPiA+PiAgUmVtb3ZlcyB0aGUgbGlua3MvbGlua3Nl
dCBsaW1pdGF0aW9uIGltcG9zZWQgYnkgdHJhZGl0aW9uYWwgVERNCj4gPj4gIGxpbmtzZXRzIGZv
ciB0cmFmZmljIGdyb3d0aAo+ID4+ICBBdm9pZCBtYWpvciBuZXR3b3JrIHJlLWVuZ2luZWVyaW5n
IHdoZW4gdHJhZmZpYyBncm93cwo+ID4+ICBTQ1RQIGlzIHRoZSBiYXNpcyBvZiBzaWduYWxsaW5n
IG92ZXIgSVAKPiA+Pgo+ID4+ICBTQ1RQIGlzIGFsc28gaW1wb3J0YW50IHRvIENoaW5hIE1vYmls
ZQo+ID4+ICBBcHBseWluZyB0byB0aGUgTmMgaW50ZXJmYWNlIHRvIHRyYW5zcG9ydCBCSUNDIG1l
c3NhZ2VzCj4gPj4gIEFwcGx5aW5nIHRvIHRoZSBNYyBpbnRlcmZhY2UgdG8gdHJhbnNwb3J0IEgu
MjQ4IG1lc3NhZ2VzCj4gPj4gIEFwcGx5aW5nIHRvIHRoZSBpbnRlcmZhY2UgYmV0d2VlbiBNU0Mg
U2VydmVyIGFuZCB0aGUgZW1iZWRkZWQgU0cgdG8KPiA+PiAgdHJhbnNwb3J0IGFjY2VzcyBuZXR3
b3JrIHNpZ25hbGxpbmcKPiA+PiAgQXBwbHlpbmcgdG8gc2lnbmFsbGluZyBuZXR3b3JrCj4gPj4g
IHRoZSBpbnRlcmZhY2UgYmV0d2VlbiBJUFNFUHMKPiA+PiAgdGhlIGludGVyZmFjZSBiZXR3ZWVu
IElQU1RQcwo+ID4+ICB0aGUgaW50ZXJmYWNlIGJldHdlZW4gSVBTRVAgYW5kIElQU1RQCj4gPj4K
PiA+Pgo+ID4+IFByb2JsZW0gZGVzY3JpcHRpb24KPiA+Pgo+ID4+IENoaW5hIE1vYmlsZSBoYXMg
YSBsYXJnZSBudW1iZXIgb2Ygc3Vic2NyaWJlcnMgYW5kIGhhcyBidWlsdCB0aGUKPiA+PiAgbGFy
Z2VzdCBzb2Z0LXN3aXRjaCBuZXR3b3JrIGluIHRoZSB3b3JsZC4gVGhlIHNpZ25hbGluZyB0cmFm
ZmljCj4gPj4gIGJldHdlZW4gdHdvIG5vZGVzIGlzIHZlcnkgbGFyZ2UuCj4gPj4gIENoaW5hIE1v
YmlsZSBpbXBvcnRzIG11bHRpLXZlbmRlcidzIHByb2R1Y3RzLiBUaGUgY29tcGF0aWJpbGl0eQo+
ID4+ICBiZXR3ZWVuIGRpZmZlcmVudCB2ZW5kZXIncyBwcm9kdWN0cyBpcyBpbXBvcnRhbnQuCj4g
Pj4gIFRoZSBpbGxlZ2liaWxpdHkgb2YgTXVsdGktaG9taW5nIG1lY2hhbmlzbSBpbiBTQ1RQIHBy
b3RvY29sIGJyaW5ncwo+ID4+ICBvbiBjb21wYXRpYmlsaXR5IHByb2JsZW1zCj4gPj4gIFNDVFAg
ZGlkIG5vdCBkZWZpbmUgdGhlIG1lY2hhbmlzbSBob3cgdGhlIFNBQ0sgaXMgc2VuZCBiYWNrIHRv
Cj4gPj4gIGVuZHBvaW50IGJ5IG90aGVyIHBhdGggd2hlbiBvbmUgcGF0aCBmYWlscy4KPiA+PiAg
U0NUUCBkZWZpbmVzIG11bHRpLWhvbWluZywgYnV0IGl0IGRpZCBub3QgZGVmaW5lIGhvdyB0aGUg
cHJpbWFyeQo+ID4+ICBwYXRoIGNhbiBiZSB1bmlvbml6ZWQgYmV0d2VlbiB0d28gbm9kZXMuCj4g
Pj4gIFJlcXVpcmVtZW50IGZvciBTdXBwbGVtZW50IG9mIFJGQzQ0NjAKPiA+PiAgRGVmaW5lIHRo
ZSBtZWNoYW5pc20gdGhhdCBTQUNLIGlzIHNlbmQgYmFjayB0byBlbmRwb2ludCBieSB0aGUKPiA+
PiAgc2Vjb25kYXJ5IHBhdGggaWYgdGhlIHByaW1hcnkgcGF0aCBmYWlscyAuCj4gPj4gIERlZmlu
ZSAgdGhlIG1lY2hhbmlzbSBob3cgdGhlIHByaW1hcnkgcGF0aCBjYW4gYmUgdW5pb25pemVkIGJl
dHdlZW4KPiA+PiAgdHdvIG5vZGVzLgo+ID4+Cj4gPj4KPiA+PiAgUHJvcG9zYWwgZm9yIFN1cHBs
ZW1lbnQgb2YgUkZDNDQ2MAo+ID4+Cj4gPj4KPiA+PiAgMaOpQWRkIHRoZSBtZWNoYW5pc20gaG93
IHRoZSBwcmltYXJ5IHBhdGggY2FuIGJlIHVuaW9uaXplZCBiZXR3ZWVuCj4gPj4gIHR3byBub2Rl
cyBpbiBTZWN0aW9uIDUgICdBc3NvY2lhdGlvbiBJbml0aWFsaXphdGlvbiAnLgo+ID4+ICAyo6kg
QWRkIHRoZSBtZWNoYW5pc20gdGhhdCBTQUNLIGlzIHNlbmQgYmFjayB0byBlbmRwb2ludCBieSB0
aGUKPiA+PiAgc2Vjb25kYXJ5IHBhdGggaWYgdGhlIHByaW1hcnkgcGF0aCBmYWlscyBpbiBTZWN0
aW9uIDYuMgo+ID4+ICAnQWNrbm93bGVkZ2VtZW50IG9uIFJlY2VwdGlvbiBvZiBEQVRBIENodW5r
cyAnLgo+ID4+Cj4gPj4gKFRoYXQncyBhbGwgZm9yIFNDVFApCj4gPj4KPiA+Pgo+ID4+ICA9PT09
PT09PT09PT09PT09PT09PT09PT09PT09PQo+ID4+ICBmb3IgTTNVQSBvZiBDaGluYSBNb2JpbGUu
cHB0Cj4gPj4gID09PT09PT09PT09PT09PT09PT09PT09PT09PT09Cj4gPj4KPiA+PiAgVGhlIFJl
cXVpcmVtZW50IGFuZCBQcm9wb3NhbAo+ID4+ICAgZm9yIE0zVUEgU3BlY2lmaWNhdGlvbiBFeHRl
bnNpb24KPiA+PiAgIG9mIENoaW5hIE1vYmlsZQo+ID4+Cj4gPj4gIENoZW4gWHUKPiA+PiAgQ2hp
bmEgTW9iaWxlCj4gPj4KPiA+Pgo+ID4+ICBDb250ZW50Cj4gPj4KPiA+PiBCYWNrZ3JvdW5kCj4g
Pj4gIFByb2JsZW0gRGVzY3JpcHRpb24KPiA+PiAgUmVxdWlyZW1lbnQgZm9yIEV4dGVuc2lvbiBv
ZiBSRkM0NjY2Cj4gPj4gIFByb3Bvc2FsIGZvciBFeHRlbnNpb24gb2YgUkZDNDY2Ngo+ID4+Cj4g
Pj4KPiA+Pgo+ID4+ICBCYWNrZ3JvdW5kCj4gPj4KPiA+PiAgVGhlIGFwcGxpY2F0aW9uIG9mIFNJ
R1RSQU4gc3RhbmRhcmQgZm9yIFNHIGhhcyBldmVyIHNvbHZlZCB0aGUKPiA+PiAgcHJvYmxlbXMg
b2YgIE5vLjcgU2lnbmFsbGluZyBTeXN0ZW0gSW50ZXJ3b3JraW5nIElQIGFuZAo+ID4+ICB0cmFu
c21pc3Npb24gb2YgIGFjY2VzcyBuZXR3b3JrIHNpZ25hbGxpbmcgIGluICBSNCBDUyBjb3JlIG5l
dHdvcmsuCj4gPj4gIFRoZSB3b3JsZCB0cmVuZCBvZiBJUCBiZWFyZXIgZm9yIHNpZ25hbGxpbmcg
d2lsbCBtYWtlIFNJR1RSQU4KPiA+PiAgc3RhbmRhcmQgd2lkZWx5IHVzZWQgaW4gc2lnbmFsbGlu
ZyBuZXR3b3JrLgo+ID4+ICBUcmFkaXRpb25hbCBhbmQgbmV3IFRlbGVjb20gY2FycmllcnMgaW1w
bGVtZW50IHNpZ25hbGxpbmcgb3ZlciBJUCB0bwo+ID4+ICBSZWR1Y2UgIGNvc3QgZm9yIGV4dGVu
ZGVkIGNhcGFjaXR5Cj4gPj4gIFJlbW92ZXMgdGhlIGxpbmtzL2xpbmtzZXQgbGltaXRhdGlvbiBp
bXBvc2VkIGJ5IHRyYWRpdGlvbmFsIFRETQo+ID4+ICBsaW5rc2V0cyBmb3IgdHJhZmZpYyBncm93
dGgKPiA+PiAgQXZvaWQgbWFqb3IgbmV0d29yayByZS1lbmdpbmVlcmluZyBhcyB0cmFmZmljIGdy
b3dzCj4gPj4KPiA+PiAgU0lHVFJBTiBpcyBhbHNvIGltcG9ydGFudCB0byBDaGluYSBNb2JpbGUK
PiA+PiAgQXBwbHlpbmcgdG8gdGhlIE5jIGludGVyZmFjZSBvZiBCSUNDIG5ldHdvcmsgdG8gdHJh
bnNwb3J0IEJJQ0MKPiA+PiAgbWVzc2FnZXMKPiA+PiAgQXBwbHlpbmcgdG8gdGhlIGludGVyZmFj
ZSBiZXR3ZWVuIE1TQyBTZXJ2ZXIgYW5kIGVtYmVkZWQgU0cgdG8KPiA+PiAgdHJhbnNwb3J0IGFj
Y2VzcyBuZXR3b3JrIHNpZ25hbGxpbmcKPiA+PiAgQXBwbHlpbmcgdG8gc2lnbmFsbGluZyBuZXR3
b3JrCj4gPj4gIHRoZSBpbnRlcmZhY2UgYmV0d2VlbiBJUFNFUHOhqqGqTTNVQQo+ID4+ICB0aGUg
aW50ZXJmYWNlIGJldHdlZW4gSVBTVFBzoaqhqk0yUEEKPiA+PiAgdGhlIGludGVyZmFjZSBiZXR3
ZWVuIElQU0VQIGFuZCBJUFNUUKGqoapNM1VBCj4gPj4KPiA+PiAgUHJvYmxlbSBkZXNjcmlwdGlv
bgo+ID4+Cj4gPj4gIE0zVUEgc3BlY2lmaWNhdGlvbiBkb2Vzbid0ICBkZWZpbmUgc2lnbmFsaW5n
IG5ldHdvcmsgIG1hbmFnZW1lbnQKPiA+PiAgZnVuY3Rpb24KPiA+PiAgTTNVQSBpcyBkZXNpZ25l
ZCBmb3IgU0ctSVBTRVAgYW5kIElQU0VQLUlQU0VQIGFwcGxpY2F0aW9ucywKPiA+PiAgdGhlcmVm
b3JlIG5ldHdvcmsgbGV2ZWwgbWFuYWdlbWVudCBmdW5jdGlvbiBpc24ndCByZXF1aXJlZC4KPiA+
PiAgU1NOTSBtZXNzYWdlcyBkZWZpbmVkIGluIE0zVUEgYXJlIG9ubHkgdXNlZCBmb3IgaW50ZXJ3
b3JraW5nIHdpdGgKPiA+PiBTUzcuCj4gPj4gIENoaW5hIE1vYmlsZSBoYXMgYSBsYXJnZSBudW1i
ZXIgb2Ygc3Vic2NyaWJlcnMgYW5kIGhhcyBidWlsdCB0aGUKPiA+PiAgbGFyZ2VzdCBzb2Z0LXN3
aXRjaCBuZXR3b3JrIGluIHRoZSB3b3JsZCwgaXRzIHNpZ25hbGluZyBuZXR3b3JrCj4gPj4gIHdp
bGwgYmUgdGhlIG11bHRpLWxldmVsIGFuZCBtdWx0aS1hcmVhIG1vZGUuCj4gPj4gIEl0IHdpbGwg
aGFzIHR3byBzaWduYWxsaW5nIHJvdXRlaW5nICBzY2VuZTpJUFNFUC1JUFNUUC1JUFNUUC1JUFNF
UAo+ID4+ICBhbmQgSVBTRVAtSVBTVFAtSVBTRVAKPiA+PiAgVGhlIGludGVyd29ya2luZyAgZnVu
Y3Rpb24gd2l0aCBNVFAzIGluIE0zVUEgY2FuIHJlYWxpemUgdGhlCj4gPj4gIHNpZ25hbGluZyBu
ZXR3b3JrICBtYW5hZ2VtZW50IGZvciAgSVBTRVAtSVBTVFAtSVBTVFAtSVBTRVAgc2NlbmU7Cj4g
Pj4gIEN1cnJlbnQgTTNVQSAgY2FuIG5vdCAgcmVhbGl6ZSB0aGUgc2lnbmFsaW5nIG5ldHdvcmsg
IG1hbmFnZW1lbnQKPiA+PiAgZm9yICBJUFNFUC1JUFNUUC1JUFNFUCBzY2VuZS4KPiA+Pgo+ID4+
ICBSZXF1aXJlbWVudCBmb3IgRXh0ZW5zaW9uIG9mIFJGQzQ2NjYKPiA+Pgo+ID4+ICBEZWZpbmUg
dGhlIEFwcGxpY2F0aW9uIGZvciBJUFNUUC1JUFNFUCBpbnRlcmZhY2UuKFN0aWxsIHVzZXMgU0dQ
LQo+ID4+ICBBU1AgcHJvY2VkdXJlcykKPiA+PiAgRGVmaW5lIHRoZSBzaWduYWxsaW5nIG5ldHdv
cmsgbWFuYWdlbWVudCBmdW5jdGlvbqOsbWVzc2FnZXMgLGFuZAo+ID4+ICBwcm9jZWR1cmVzLihE
ZXNjcmliZSBob3cgdG8gdXNlIFNTTk0gbWVzc2FnZXMgdG8gc3VwcG9ydCBzaWduYWxpbmcKPiA+
PiAgbmV0d29yayBtYW5hZ2VtZW50IGZvciBJUFNFUC0oTTNVQSktSVBTVFAtKE0zVUEpLUlQU0VQ
IHNjZW5lLiApCj4gPj4KPiA+PiAgUHJvcG9zYWwgZm9yIEV4dGVuc2lvbiBvZiBSRkM0NjY2Cj4g
Pj4KPiA+PiAgMaOpQWRkIGRpZmZlcmVudCBraW5kcyBvZiByb3V0aW5nIHNjZW5lcyBhcHBsaWNh
dGlvbnMgZm9yIElQU0VQLQo+ID4+ICBJUFNUUCBpbnRlcmZhY2UgaW4gU2VjdGlvbiAxLjUgICdT
YW1wbGUgQ29uZmlndXJhdGlvbiAnLgo+ID4+ICAyo6lBZGQgdGhlIE0zVUEgc2lnbmFsbGluZyBu
ZXR3b3JrIG1hbmFnZW1lbnQgZnVuY3Rpb24gaW4gU2VjdGlvbgo+ID4+ICAxLjQgICdGdW5jdGlv
bmFsIEFyZWFzJy4KPiA+PiAgM6OpIEFkZCB0aGUgQ2xpZW50L1NlcnZlciBNb2RlbCBmb3IgSVBT
VFAtSVBTRVAgaW50ZXJmYWNlIGluCj4gPj4gIFNlY3Rpb24gMS40LjguICAnU0NUUCBDbGllbnQv
U2VydmVyIE1vZGVsJy4KPiA+PiAgNKOpRXh0ZW5kIHRoZSBEVVBVIG1lc3NhZ2UgY29kZSBpbiBD
aGFwdGVyIDMgJ00zVUEgUHJvdG9jb2wKPiA+PiAgRWxlbWVudHMnLgo+ID4+ICA1o6lBZGQgdGhl
IHNpZ25hbGxpbmcgbmV0d29yayBtYW5hZ2VtZW50IHByb2NlZHVyZSBpbiBDaGFwdGVyCj4gPj4g
IDQncHJvY2VkdXJlJy4KPiA+PiAgNikgQWRkIHRoZSByZXF1aXJlbWVudCBvZiBNdWx0aSB1c2Vy
IGRhdGEgc3RyZWFtcyBmb3IgTTNVQSBvdmVyCj4gPj4gIFNDVFAgQXBwbGljYXRpb24gaW4gU2Vj
dGlvbiAxLjQuNyAnIFNDVFAgU3RyZWFtIE1hcHBpbmcnLgo+ID4+Cj4gPj4gKFRoYXQncyBhbGwg
Zm9yIE0zVUEpCj4gPj4KPiA+Pgo+ID4+ICA9PT09PT09PT09PT09PT09PT09PT09PT09PT09PQo+
ID4+ICBmb3IgTTJQQSBvZiBDaGluYSBNb2JpbGUucHB0Cj4gPj4gID09PT09PT09PT09PT09PT09
PT09PT09PT09PT09Cj4gPj4KPiA+PiAgVGhlIFJlcXVpcmVtZW50IGFuZCBQcm9wb3NhbAo+ID4+
ICAgZm9yIE0yUEEgU3BlY2lmaWNhdGlvbiBSZXZpc2lvbgo+ID4+ICAgb2YgQ2hpbmEgTW9iaWxl
Cj4gPj4KPiA+PiAgQ2hlbiBYdQo+ID4+ICBDaGluYSBNb2JpbGUKPiA+Pgo+ID4+ICBDb250ZW50
Cj4gPj4KPiA+PiAgQmFja2dyb3VuZAo+ID4+ICBQcm9ibGVtIERlc2NyaXB0aW9uCj4gPj4gIFJl
cXVpcmVtZW50IGZvciBSZXZpc2lvbiBvZiBSRkM0MTY1Cj4gPj4gIFByb3Bvc2FsIGZvciBSZXZp
c2lvbiBvZiBSRkM0MTY1Cj4gPj4KPiA+Pgo+ID4+ICBCYWNrZ3JvdW5kCj4gPj4KPiA+PiAgTTJQ
QSBwcm90b2NvbCBpcyBhIHBlZXIgdG8gcGVlciBwcm90b2NvbCwgaXQgbm90IG9ubHkgc3VwcG9y
dHMKPiA+PiAgc2VhbWxlc3MgbWFuYWdlbWVudCBvcGVyYXRpb24gb2YgTVRQMyBwcm90b2NvbCBw
ZWVycyBvdmVyIGFuIElQCj4gPj4gIG5ldHdvcmsgY29ubmVjdGlvbiwgYnV0IGFsc28gcmVtb3Zl
cyB0aGUgbGlua3MvbGlua3NldCBsaW1pdGF0aW9uCj4gPj4gIGltcG9zZWQgYnkgdHJhZGl0aW9u
YWwgVERNIGxpbmtzZXRzIGZvciB0cmFmZmljIGdyb3d0aC4KPiA+Pgo+ID4+ICBUaGUgU3RhbmRh
cmRpemF0aW9uIG9mIE0yUEEgaXMgYmVoaW5kIHRoZSBhcHBsaWNhdGlvbiBvZiBpdC4KPiA+PiAg
QWx0aG91Z2ggdGhlIFJGQyBlZGl0aW9uIGlzIHJlbGVhc2VkIGluIDIwMDUsIE0yUEEgaXMgd2lk
ZWx5IHVzZWQKPiA+PiAgaW4gdGhlICBTaWduYWxpbmcgbmV0d29yayByZWJ1aWxkaW5nIG92ZXIg
SVAgZm9yIHRyYWRpdGlvbmFsCj4gPj4gIG9wZXJhdG9ycyBhbmQgaW4gdGhlIFNpZ25hbGluZyBu
ZXR3b3JrIGNvbnN0cnVjdGlvbiBmb3IgIG5ldwo+ID4+ICBvcGVyYXRvcnMgIHNpbmNlIDIwMDIu
Cj4gPj4KPiA+PiAgVmFyaW91cyBkcmFmdCBlZGl0aW9ucyBhbmQgdGhlIG1ham9yIGRpZmZlcmVu
Y2VzIGJldHdlZW4gdGhlbSBtYWtlCj4gPj4gIHByb2JsZW1zIHdoZW4gb25lICBJUFNUUCBwcm92
aWRlciBpbnRlcndvcmtpbmcgd2l0aCBhbm90aGVyLgo+ID4+Cj4gPj4gIFByb2JsZW0gRGVzY3Jp
cHRpb24KPiA+Pgo+ID4+Cj4gPj4gIFJGQzQxNjUgbmVlZHMgdG8gYmUgc3VwcGxlbWVudGVkIGFu
ZCByZXZpc2VkIKO6Cj4gPj4gIFNvbWUgIHByb2NlZHVyZXMgIGFyZSAgZGVzY3JpYmVkIGEgbGl0
dGxlIGJpdCBzaW1wbHkgYW5kIHJlZmVycmVkCj4gPj4gIHRvIE1UUDIgZGlyZWN0bHkgLCAgd2hp
Y2ggIG1ha2VzIElQU1RQICBwcm92aWRlcnMgcmVhbGl6aW5nIHRoZQo+ID4+ICBwcm9jZWR1cmVz
IGluIGRpZmZlcmVudCB3YXlzICxmb3IgIHRoZXJlJ3MgZGlmZmVyZW5jZSBiZXR3ZWVuIE1UUDIK
PiA+PiAgYW5kIE0yUEEgaW4gc29tZSBhc3BlY3RzLiAgICAgIC4KPiA+PiAgU29tZSBJUFNUUCBw
cm92aWRlcnMgdXNlIHRoZSBzYW1lIGlkZWEgYXMgTVRQMgo+ID4+ICBPdGhlcnMgdGFrZSB0aGUg
cmVsYXRpb24gYmV0d2VlbiBNMlBBIGFuZCBTQ1RQIGludG8gYWNjb3VudC4KPiA+Pgo+ID4+ICBU
NyBpc24ndCBkZWZpbmVkIGFuZCBnaXZlbiB0aGUgcmFuZ2UsIHdoaWNoIG1ha2VzIElQU1RQIHBy
b3ZpZGVycwo+ID4+ICByZWFsaXppbmcgaXQgaW4gZGlmZmVyZW50IHdheXMuCj4gPj4KPiA+PiAg
SG93IHRvIGZpbGwgaW4gYW5kIHByb2Nlc3MgRlNOIGFuZCBCU04gaW4gTTJQQSBIZWFkZXIgaXNu
J3QKPiA+PiAgZGVmaW5lZCBjbGVhcmx5Lgo+ID4+Cj4gPj4KPiA+PiAgUmVxdWlyZW1lbnQgZm9y
IFJldmlzaW9uIG9mIFJGQzQxNjUKPiA+Pgo+ID4+ICBTdXBwbGVtZW50IHRoZSBkZXNjcmlwdGlv
biBvZiB0aGUgd2hvbGUgaWRlYSBmb3IgTGluayBBbGlnbm1lbnQKPiA+PiAgcHJvY2VkdXJlIGFu
ZCBQcm9jZXNzb3IgT3V0YWdlIHByb2NlZHVyZS4KPiA+PiAgU3VwcGxlbWVudCB0aGUgZGVmaW5p
dGlvbiBhbmQgcmFuZ2Ugb2YgTTJQQSBUaW1lcnMuCj4gPj4gIFN1cHBsZW1lbnQgdGhlIHJ1bGVz
IG9mIHVzYWdlIG9mIEZTTiBhbmQgQlNOIGluIE0yUEEgSGVhZGVyLgo+ID4+Cj4gPj4KPiA+PiAg
UHJvcG9zYWwgZm9yIFJldmlzaW9uIG9mIFJGQzQxNjUKPiA+Pgo+ID4+ICAxo6lTdXBwbGVtZW50
IHRoZSB3aG9sZSBpZGVhICwgdGhlIHBoYXNlIGRpdmlzaW9uICwgdGhlIGNvcnJlbGF0ZWQKPiA+
PiAgbWVzc2FnZXMgYW5kIFRpbWVycyBvZiBMaW5rIEFsaWdubWVudCBwcm9jZWR1cmUgaW4gU2Vj
dGlvbiA0LjEuMy4KPiA+PiAgMqOpU3VwcGxlbWVudCB0aGUgd2hvbGUgaWRlYSBvZiBQcm9jZXNz
b3IgT3V0YWdlIHByb2NlZHVyZSwgYW5kCj4gPj4gIGRlc2NyaWJlIHRoZSBydWxlcyBvZiBMUE8g
YW5kIFJQTyBwcm9jZXNzaW5nIHNlcGFyYXRlbHkgLgo+ID4+ICAzo6lTdXBwbGVtZW50IHRoZSBy
dWxlcyBvZiB1c2FnZSBvZiBGU04gYW5kIEJTTiBpbiBNMlBBIEhlYWRlciBpbgo+ID4+ICBTZWN0
aW9uIDQuMi4xCj4gPj4gIDSjqVN1cHBsZW1lbnQgdGhlIGRlZmluaXRpb24gYW5kIHJhbmdlIG9m
IE0yUEEgVGltZXJzIGluIEFwcGVuZGl4Lgo+ID4+Cj4gPj4gKFRoYXQncyBhbGwgZm9yIE0yUEEp
Cj4gPj4KPiA+PiBDaGVuIFh1Cj4gPj4gQ2hpbmEgTW9iaWxlCj4gPj4gY2hlbnh1QGNoaW5hbW9i
aWxlLmNvbQo+ID4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fCj4gPj4gU2lndHJhbiBtYWlsaW5nIGxpc3QKPiA+PiBTaWd0cmFuQGlldGYub3JnCj4gPj4g
aHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc2lndHJhbgo+Cj4KPgo+IF9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4gU2lndHJhbiBt
YWlsaW5nIGxpc3QKPiBTaWd0cmFuQGlldGYub3JnCj4gaHR0cHM6Ly93d3cxLmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vc2lndHJhbgo+Cj4K
------=_Part_5001_105760.1185540454561
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: base64
Content-Disposition: inline

Y2hlbnh1LDxicj48YnI+PGRpdj48c3BhbiBjbGFzcz0iZ21haWxfcXVvdGUiPk9uIDcvMjcvMDcs
IDxiIGNsYXNzPSJnbWFpbF9zZW5kZXJuYW1lIj6zwtDxPC9iPiAmbHQ7PGEgaHJlZj0ibWFpbHRv
OmNoZW54dUBjaGluYW1vYmlsZS5jb20iIHRhcmdldD0iX2JsYW5rIiBvbmNsaWNrPSJyZXR1cm4g
dG9wLmpzLk9wZW5FeHRMaW5rKHdpbmRvdyxldmVudCx0aGlzKSI+Y2hlbnh1QGNoaW5hbW9iaWxl
LmNvbQo8L2E+Jmd0OyB3cm90ZTo8L3NwYW4+PGJsb2NrcXVvdGUgY2xhc3M9ImdtYWlsX3F1b3Rl
IiBzdHlsZT0iYm9yZGVyLWxlZnQ6IDFweCBzb2xpZCByZ2IoMjA0LCAyMDQsIDIwNCk7IG1hcmdp
bjogMHB0IDBwdCAwcHQgMC44ZXg7IHBhZGRpbmctbGVmdDogMWV4OyI+CkRlYXIgTWljaGFlbCBU
dWV4ZW4sPGJyPjxicj48YnI+Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzEuIFdoYXQgZG9l
cyAmcXVvdDt1bmlvbml6ZSBvZiB0aGUgcHJpbWFyeSBwYXRocyBiZXR3ZWVuIG5vZGVzJnF1b3Q7
IG1lYW4/PGJyPiZuYnNwOyZuYnNwOwpJdCBtZWFuc6OsZm9yIG9uZSBtdWx0aS1ob21lZCBTQ1RQ
IGVuZHBvaW50LHRoZSBwcmltYXJ5IHBhdGijqHNvdXJjZSBJUAphZGRyZXNzPUlQMS0tLWRlc3Rp
bmF0aW9uIElQPUlQMqOpIHNoYWxsIGJlIHRoZSBzYW1lIGFzIHRoZSByZW1vdGUKZW5kcG9pbnQm
IzM5O3MgKCBzb3VyY2UgSVAgYWRkcmVzcz1JUDItLS1kZXN0aW5hdGlvbiBJUD1JUDEmbmJzcDsm
bmJzcDspPGJyPjxicj4mbmJzcDsmbmJzcDsgTWFueSB2ZW5kZXJzIGltcGxlbWVudCBNdWx0aS1o
b21pbmcgaW4gdGhlIGZvbGxvd2luZyB3YXk6PGJyPjxicj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDtvbmUKbXVsdGktaG9tZWQgU0NUUCBlbmRwb2ludCBoYXMgdHdvIGxvY2FsIElQIGFkZHJlc3Nl
cyhJUDEvSVAyKSBhbmQgdHdvCnJlbW90ZSBJUCBhZGRyZXNzKElQMy9JUDQpIHdpdGhpbiBhbiBh
c3NvY2lhdGlvbi48YnI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7VGhlcmUmIzM5O3MgdHdvIHBh
dGhzIHdpdGhpbiBhbiBhc3NvY2lhdGlvbjpJUDEtSVAzLGFuZCBJUDItSVA0Lm5vdCA0IHBhdGhz
Ljxicj48YnI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Rm9yCmV4YW1wbGUsIGVuZHBvaW50MSBo
YXMgdHdvIGxvY2FsIElQIGFkZHJlc3NlcyhJUDEvSVAyKaOsIGFuZCBlbmRwb2ludDIKaGFzIHR3
byBsb2NhbCBJUCBhZGRyZXNzZXMoSVAzL0lQNCkuPGJyPjxicj5pZiB0d28gZW5kcG9pbnRzJiMz
OTsgcHJpbWFyeQpwYXRoIGlzbiYjMzk7dCB0aGUgc2FtZSx0aGF0IGlzIGVuZHBvaW50MSB1c2Ug
SVAxLUlQMyBhcyB0aGUgcHJpbWFyeSBwYXRoLAp1c2UgSVAyLUlQNCBhcyB0aGUgc2Vjb25kIHBh
dGg7Jm5ic3A7Jm5ic3A7ZW5kcG9pbnQyIHVzZSBJUDMtSVAyIGFzIHRoZQpwcmltYXJ5IHBhdGgs
IHVzZSBJUDQtSVAxIGFzIHRoZSBzZWNvbmQgcGF0aC48YnI+PGJyPiZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwO1RoZXNlIHR3byBlbmRwb2ludHMgY2FuJiMzOTt0Jm5ic3A7Jm5ic3A7c2VuZCBkYXRh
IHRvIGVhY2ggb3RoZXIgc3VjY2Vzc2Z1bGx5Ljxicj4KPC9ibG9ja3F1b3RlPjxkaXY+Jm5ic3A7
Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAyLiBOb3Qgc3VyZSBhYm91dCB0aGUgU0FDSyBp
c3N1ZTogWW91IGFyZSBjdXJyZW50bHkgYWxsb3dlZCB0bzxicj4KPC9kaXY+PGJsb2NrcXVvdGUg
Y2xhc3M9ImdtYWlsX3F1b3RlIiBzdHlsZT0iYm9yZGVyLWxlZnQ6IDFweCBzb2xpZCByZ2IoMjA0
LCAyMDQsIDIwNCk7IG1hcmdpbjogMHB0IDBwdCAwcHQgMC44ZXg7IHBhZGRpbmctbGVmdDogMWV4
OyI+Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO3NlbmQgdGhlIFNBQ0sgYmFjayB0byBhbiBh
ZGRyZXNzZXMgZGlmZmVyZW50IGZyb20gdGhlIHNvdXJjZQo8YnI+Jmd0OyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwO2FkZHJlc3Mgb2YgdGhlIGNvcnJlc3BvbmRpbmcgREFUQSBjaHVuay4gQXMgZmFy
IGFzIEkga25vdzxicj4mZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7aXQgaXMgb25seSBhIFNI
T1VMRCBkZXNjcmliaW5nIHRoYXQgeW91IHNlbmQgdGhlIFNBQ0sgYmFjazxicj4mZ3Q7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7dG8gdGhlIHNvdXJjZSBhZGRyZXNzIG9mIHRoZSBEQVRBIGNodW5r
Ljxicj48YnI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IFlvdSBhcmUgcmlnaHQsaXQgaXMgb25s
eSBhIFNIT1VMRCBkZXNjcmliaW5nIHRoYXQgeW91IHNlbmQgdGhlIFNBQ0sgYmFjawo8YnI+Jm5i
c3A7Jm5ic3A7IHRvIHRoZSBzb3VyY2UgYWRkcmVzcyBvZiB0aGUgREFUQSBjaHVuayBpbiBSRkMy
OTYwLjxicj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtUaGF0JiMzOTtzIHdo
eSB3ZSBnZXQgaW4gdHJvdWJsZSBpbiBtdWx0aS1ob21pbmcgc2l0dWF0aW9uLjxicj4mbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtJZgp0aGUmbmJzcDsmbmJzcDtwYXRoIHRvIHRo
ZSBzb3VyY2UgYWRkcmVzcyBvZiB0aGUgREFUQSBjaHVuayBpcwp1bnJlYWNoYWJsZaOsdGhlIHNh
Y2sgY2FuJiMzOTt0IHNlbmQgdG8gdGhlIHJlbW90ZSBlbmRwb2ludCBmb3IgZXZlcgphbHRob3Vn
aCB0aGUgb3RoZXIgcGF0aCBpcyBhdmFpbGFibGUuU29vbiB0aGUgb3RoZXIgcGF0aCB3aWxsIGJl
CmZhaWx1cmUuPC9ibG9ja3F1b3RlPjxkaXY+PGJyPgpJIGRvbiYjMzk7dCBzZWUgYW55IHByb2Js
ZW0gaW4gU0NUUCBSRkMgZm9yIGFib3ZlIG1lbnRpb25lZCBzY2VuYXJpby48YnI+CkFzIHBlciBS
RkMgMjcxOSwgZm9sbG93aW5nIGlzIHRoZSBkZWZpbmF0aW9uIG9mICZxdW90O1NIT1VMRCZxdW90
Ozo8YnI+CjxwcmU+PGgyPjxhIG5hbWU9IjExNDA3NzlkNTEzOGUzYzJfczMuIj4zLiBTSE9VTEQg
ICBUaGlzIHdvcmQsIG9yIHRoZSBhZGplY3RpdmUgJnF1b3Q7UkVDT01NRU5ERUQmcXVvdDssIG1l
YW4gdGhhdCB0aGVyZTwvYT48L2gyPiAgIG1heSBleGlzdCB2YWxpZCByZWFzb25zIGluIHBhcnRp
Y3VsYXIgY2lyY3Vtc3RhbmNlcyB0byBpZ25vcmUgYTxicj4gICBwYXJ0aWN1bGFyIGl0ZW0sIGJ1
dCB0aGUgZnVsbCBpbXBsaWNhdGlvbnMgbXVzdCBiZSB1bmRlcnN0b29kIGFuZAo8YnI+PGJyPiAg
IGNhcmVmdWxseSB3ZWlnaGVkIGJlZm9yZSBjaG9vc2luZyBhIGRpZmZlcmVudCBjb3Vyc2UuPC9w
cmU+Cjxicj4KPGJyPgpOb3cgcGxlYXNlIGxvb2sgYXQgZm9sbG93aW5nIGV4Y2VycHQgZnJvbSBz
ZWN0aW9uIDYuNChNdWx0aS1ob21lZCBTQ1RQIEVuZHBvaW50cykgb2YgU0NUUCBSRkM6PGJyPgom
cXVvdDsKPHByZT5XaGVuIGEgcmVjZWl2ZXIgb2YgYSBkdXBsaWNhdGUgREFUQSBjaHVuayBzZW5k
cyBhIFNBQ0sgdG8gYSBtdWx0aS08YnI+ICAgaG9tZWQgZW5kcG9pbnQgaXQgTUFZIGJlIGJlbmVm
aWNpYWwgdG8gdmFyeSB0aGUgZGVzdGluYXRpb24gYWRkcmVzczxicj4gICBhbmQgbm90IHVzZSB0
aGUgc291cmNlIGFkZHJlc3Mgb2YgdGhlIERBVEEgY2h1bmsuICBUaGUgcmVhc29uIGJlaW5nPGJy
Pgo8YnI+ICAgdGhhdCByZWNlaXZpbmcgYSBkdXBsaWNhdGUgZnJvbSBhIG11bHRpLWhvbWVkIGVu
ZHBvaW50IG1pZ2h0IGluZGljYXRlPGJyPiAgIHRoYXQgdGhlIHJldHVybiBwYXRoIChhcyBzcGVj
aWZpZWQgaW4gdGhlIHNvdXJjZSBhZGRyZXNzIG9mIHRoZSBEQVRBPGJyPiAgIGNodW5rKSBmb3Ig
dGhlIFNBQ0sgaXMgYnJva2VuLjxicj4mcXVvdDs8YnI+PC9wcmU+CiA8L2Rpdj5TbyBhcyBwZXIg
eW91ciBzY2VuYXJpbywgaWYgU09VUkNFIGFkZHJlc3Mgb2Ygc2VuZGVyIGlzIG5vdApyZWFjaGFi
bGUgdGhlbiBvdXIgU0FDSyB3b3VsZCBiZSBsb3N0LiBBZnRlciBSVE8gZXhwaXJ5IGF0IHNlbmRl
ciwgc2VuZGVyCndvdWxkIGFnYWluIHRyeSB0byBzZW5kIHRoZSBEQVRBIGNodW5rLiBOb3csIHJl
Y2VpdmVyIGNvdWxkIGJlaGF2ZSBhcwpwZXIgYWJvdmUgbWVudGlvbmVkIGV4Y2VycHQuPGJyPgo8
YnI+PGJsb2NrcXVvdGUgY2xhc3M9ImdtYWlsX3F1b3RlIiBzdHlsZT0iYm9yZGVyLWxlZnQ6IDFw
eCBzb2xpZCByZ2IoMjA0LCAyMDQsIDIwNCk7IG1hcmdpbjogMHB0IDBwdCAwcHQgMC44ZXg7IHBh
ZGRpbmctbGVmdDogMWV4OyI+QmVzdCBSZWdhcmQ8YnI+Q2hlbiBYdTxicj5DaGluYSBNb2JpbGU8
YnI+PGEgaHJlZj0ibWFpbHRvOmNoZW54dUBjaGluYW1vYmlsZS5jb20iIHRhcmdldD0iX2JsYW5r
IiBvbmNsaWNrPSJyZXR1cm4gdG9wLmpzLk9wZW5FeHRMaW5rKHdpbmRvdyxldmVudCx0aGlzKSI+
CmNoZW54dUBjaGluYW1vYmlsZS5jb20KPC9hPjxicj48YnI+PGJyPjxicj48YnI+PGJyPjxicj48
YnI+PT09PT09PSAyMDA3LTA3LTI2IDIyOjIzOjIwIMT61NrAtNDF1tDQtLXAo7o9PT09PT09PGJy
Pjxicj4mZ3Q7RGVhciBhbGwsPGJyPiZndDs8YnI+Jmd0O0kmIzM5O20gc2VuZGluZyB0aGlzIGFs
c28gdG8gVFNWV0csIHNpbmNlIHRoZSBTQ1RQIGRpc2N1c3Npb24gaGFzIHRvIGJlPGJyPiZndDtk
b25lIHRoZSB0aGF0IFdHLjxicj4mZ3Q7Cjxicj4KJmd0O0FkZHJlc3NpbmcgdGhlIFNDVFAgc3Rh
dGVtZW50Ojxicj4mZ3Q7PGJyPiZndDsxLiBXaGF0IGRvZXMgJnF1b3Q7dW5pb25pemUgb2YgdGhl
IHByaW1hcnkgcGF0aHMgYmV0d2VlbiBub2RlcyZxdW90OyBtZWFuPzxicj4mZ3Q7Mi4gTm90IHN1
cmUgYWJvdXQgdGhlIFNBQ0sgaXNzdWU6IFlvdSBhcmUgY3VycmVudGx5IGFsbG93ZWQgdG88YnI+
Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO3NlbmQgdGhlIFNBQ0sgYmFjayB0byBhbiBhZGRy
ZXNzZXMgZGlmZmVyZW50IGZyb20gdGhlIHNvdXJjZQo8YnI+Jmd0OyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwO2FkZHJlc3Mgb2YgdGhlIGNvcnJlc3BvbmRpbmcgREFUQSBjaHVuay4gQXMgZmFyIGFz
IEkga25vdzxicj4mZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7aXQgaXMgb25seSBhIFNIT1VM
RCBkZXNjcmliaW5nIHRoYXQgeW91IHNlbmQgdGhlIFNBQ0sgYmFjazxicj4mZ3Q7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7dG8gdGhlIHNvdXJjZSBhZGRyZXNzIG9mIHRoZSBEQVRBIGNodW5rLjxi
cj4mZ3Q7PGJyPiZndDtCZXN0IHJlZ2FyZHM8YnI+CgomZ3Q7TWljaGFlbDxicj4mZ3Q7PGJyPiZn
dDtPbiBKdWwgMjYsIDIwMDcsIGF0IDQ6MjIgQU0sIGNoZW54dSB3cm90ZTo8YnI+Jmd0Ozxicj4m
Z3Q7Jmd0OyBEZWFyIGFsbCw8YnI+Jmd0OyZndDs8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDtTb3JyeSB0byBzdWJtaXQgdGhlIHJhciBmaWxlISBBbmQgdGhh
bmtzIFJ1aSBHb21lcyE8YnI+Jmd0OyZndDs8YnI+Jmd0OyZndDsgVGhlIGNvbnRlbnRzIG9mIHRo
ZSBhdHRhY2htZW50cyBhcmUgYXMgZm9sbG93czoKPGJyPiZndDsmZ3Q7PGJyPiZndDsmZ3Q7Jm5i
c3A7Jm5ic3A7ID09PT09PT09PT09PT09PT09PT09PT09PT09PT09PGJyPiZndDsmZ3Q7Jm5ic3A7
Jm5ic3A7IGZvciBTQ1RQIG9mIENoaW5hIE1vYmlsZS5wcHQ8YnI+Jmd0OyZndDsmbmJzcDsmbmJz
cDs9PT09PT09PT09PT09PT09PT09PT09PT09PT09PTxicj4mZ3Q7Jmd0Ozxicj4mZ3Q7Jmd0OyZu
YnNwOyZuYnNwO1RoZSBSZXF1aXJlbWVudCBhbmQgUHJvcG9zYWw8YnI+Jmd0OyZndDsmbmJzcDsm
bmJzcDsgZm9yIFNDVFAgU3BlY2lmaWNhdGlvbiBFeHRlbnNpb24KPGJyPiZndDsmZ3Q7Jm5ic3A7
Jm5ic3A7IG9mIENoaW5hIE1vYmlsZTxicj4mZ3Q7Jmd0Ozxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNw
O0NoZW4gWHUgLCBaaGFuZyBIYW88YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtDaGluYSBNb2JpbGU8
YnI+Jmd0OyZndDs8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtDb250ZW50PGJyPiZndDsmZ3Q7PGJy
PiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7QmFja2dyb3VuZDxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO1By
b2JsZW0gZGVzY3JpcHRpb248YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtSZXF1aXJlbWVudCBmb3Ig
U3VwcGxlbWVudCBvZiBSRkM0NDYwCjxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO1Byb3Bvc2FsIGZv
ciBTdXBwbGVtZW50IG9mIFJGQzQ0NjA8YnI+Jmd0OyZndDs8YnI+Jmd0OyZndDsmbmJzcDsmbmJz
cDtCYWNrZ3JvdW5kPGJyPiZndDsmZ3Q7PGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7VGhlIHdvcmxk
IHRyZW5kIG9mIElQIGJlYXJlciBmb3Igc2lnbmFsbGluZyB3aWxsIG1ha2UgU0lHVFJBTjxicj4m
Z3Q7Jmd0OyZuYnNwOyZuYnNwO3N0YW5kYXJkIHdpZGVseSB1c2VkIGluIHNpZ25hbGxpbmcgbmV0
d29yay4KPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7VHJhZGl0aW9uYWwgYW5kIG5ldyBUZWxlY29t
IGNhcnJpZXJzIGltcGxlbWVudCBzaWduYWxsaW5nIG92ZXIgSVAgdG88YnI+Jmd0OyZndDsmbmJz
cDsmbmJzcDtSZWR1Y2UmbmJzcDsmbmJzcDtjb3N0IGZvciBleHRlbmRlZCBjYXBhY2l0eTxicj4m
Z3Q7Jmd0OyZuYnNwOyZuYnNwO1JlbW92ZXMgdGhlIGxpbmtzL2xpbmtzZXQgbGltaXRhdGlvbiBp
bXBvc2VkIGJ5IHRyYWRpdGlvbmFsIFRETTxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO2xpbmtzZXRz
IGZvciB0cmFmZmljIGdyb3d0aAo8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtBdm9pZCBtYWpvciBu
ZXR3b3JrIHJlLWVuZ2luZWVyaW5nIHdoZW4gdHJhZmZpYyBncm93czxicj4mZ3Q7Jmd0OyZuYnNw
OyZuYnNwO1NDVFAgaXMgdGhlIGJhc2lzIG9mIHNpZ25hbGxpbmcgb3ZlciBJUDxicj4mZ3Q7Jmd0
Ozxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO1NDVFAgaXMgYWxzbyBpbXBvcnRhbnQgdG8gQ2hpbmEg
TW9iaWxlPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7QXBwbHlpbmcgdG8gdGhlIE5jIGludGVyZmFj
ZSB0byB0cmFuc3BvcnQgQklDQyBtZXNzYWdlcwo8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtBcHBs
eWluZyB0byB0aGUgTWMgaW50ZXJmYWNlIHRvIHRyYW5zcG9ydCBILjI0OCBtZXNzYWdlczxicj4m
Z3Q7Jmd0OyZuYnNwOyZuYnNwO0FwcGx5aW5nIHRvIHRoZSBpbnRlcmZhY2UgYmV0d2VlbiBNU0Mg
U2VydmVyIGFuZCB0aGUgZW1iZWRkZWQgU0cgdG88YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDt0cmFu
c3BvcnQgYWNjZXNzIG5ldHdvcmsgc2lnbmFsbGluZzxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO0Fw
cGx5aW5nIHRvIHNpZ25hbGxpbmcgbmV0d29yawo8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDt0aGUg
aW50ZXJmYWNlIGJldHdlZW4gSVBTRVBzPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7dGhlIGludGVy
ZmFjZSBiZXR3ZWVuIElQU1RQczxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO3RoZSBpbnRlcmZhY2Ug
YmV0d2VlbiBJUFNFUCBhbmQgSVBTVFA8YnI+Jmd0OyZndDs8YnI+Jmd0OyZndDs8YnI+Jmd0OyZn
dDsgUHJvYmxlbSBkZXNjcmlwdGlvbjxicj4mZ3Q7Jmd0Ozxicj4mZ3Q7Jmd0OyBDaGluYSBNb2Jp
bGUgaGFzIGEgbGFyZ2UgbnVtYmVyIG9mIHN1YnNjcmliZXJzIGFuZCBoYXMgYnVpbHQgdGhlCjxi
cj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO2xhcmdlc3Qgc29mdC1zd2l0Y2ggbmV0d29yayBpbiB0aGUg
d29ybGQuIFRoZSBzaWduYWxpbmcgdHJhZmZpYzxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO2JldHdl
ZW4gdHdvIG5vZGVzIGlzIHZlcnkgbGFyZ2UuPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Q2hpbmEg
TW9iaWxlIGltcG9ydHMgbXVsdGktdmVuZGVyJiMzOTtzIHByb2R1Y3RzLiBUaGUgY29tcGF0aWJp
bGl0eTxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO2JldHdlZW4gZGlmZmVyZW50IHZlbmRlciYjMzk7
cyBwcm9kdWN0cyBpcyBpbXBvcnRhbnQuCjxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO1RoZSBpbGxl
Z2liaWxpdHkgb2YgTXVsdGktaG9taW5nIG1lY2hhbmlzbSBpbiBTQ1RQIHByb3RvY29sIGJyaW5n
czxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO29uIGNvbXBhdGliaWxpdHkgcHJvYmxlbXM8YnI+Jmd0
OyZndDsmbmJzcDsmbmJzcDtTQ1RQIGRpZCBub3QgZGVmaW5lIHRoZSBtZWNoYW5pc20gaG93IHRo
ZSBTQUNLIGlzIHNlbmQgYmFjayB0bzxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO2VuZHBvaW50IGJ5
IG90aGVyIHBhdGggd2hlbiBvbmUgcGF0aCBmYWlscy4KPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7
U0NUUCBkZWZpbmVzIG11bHRpLWhvbWluZywgYnV0IGl0IGRpZCBub3QgZGVmaW5lIGhvdyB0aGUg
cHJpbWFyeTxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO3BhdGggY2FuIGJlIHVuaW9uaXplZCBiZXR3
ZWVuIHR3byBub2Rlcy48YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtSZXF1aXJlbWVudCBmb3IgU3Vw
cGxlbWVudCBvZiBSRkM0NDYwPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7RGVmaW5lIHRoZSBtZWNo
YW5pc20gdGhhdCBTQUNLIGlzIHNlbmQgYmFjayB0byBlbmRwb2ludCBieSB0aGUKPGJyPiZndDsm
Z3Q7Jm5ic3A7Jm5ic3A7c2Vjb25kYXJ5IHBhdGggaWYgdGhlIHByaW1hcnkgcGF0aCBmYWlscyAu
PGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7RGVmaW5lJm5ic3A7Jm5ic3A7dGhlIG1lY2hhbmlzbSBo
b3cgdGhlIHByaW1hcnkgcGF0aCBjYW4gYmUgdW5pb25pemVkIGJldHdlZW48YnI+Jmd0OyZndDsm
bmJzcDsmbmJzcDt0d28gbm9kZXMuPGJyPiZndDsmZ3Q7PGJyPiZndDsmZ3Q7PGJyPiZndDsmZ3Q7
Jm5ic3A7Jm5ic3A7UHJvcG9zYWwgZm9yIFN1cHBsZW1lbnQgb2YgUkZDNDQ2MAo8YnI+Jmd0OyZn
dDs8YnI+Jmd0OyZndDs8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDsxo6lBZGQgdGhlIG1lY2hhbmlz
bSBob3cgdGhlIHByaW1hcnkgcGF0aCBjYW4gYmUgdW5pb25pemVkIGJldHdlZW48YnI+Jmd0OyZn
dDsmbmJzcDsmbmJzcDt0d28gbm9kZXMgaW4gU2VjdGlvbiA1Jm5ic3A7Jm5ic3A7JiMzOTtBc3Nv
Y2lhdGlvbiBJbml0aWFsaXphdGlvbiAmIzM5Oy48YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDsyo6kg
QWRkIHRoZSBtZWNoYW5pc20gdGhhdCBTQUNLIGlzIHNlbmQgYmFjayB0byBlbmRwb2ludCBieSB0
aGUKPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7c2Vjb25kYXJ5IHBhdGggaWYgdGhlIHByaW1hcnkg
cGF0aCBmYWlscyBpbiBTZWN0aW9uIDYuMjxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwOyYjMzk7QWNr
bm93bGVkZ2VtZW50IG9uIFJlY2VwdGlvbiBvZiBEQVRBIENodW5rcyAmIzM5Oy48YnI+Jmd0OyZn
dDs8YnI+Jmd0OyZndDsgKFRoYXQmIzM5O3MgYWxsIGZvciBTQ1RQKTxicj4mZ3Q7Jmd0Ozxicj4m
Z3Q7Jmd0Ozxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwOz09PT09PT09PT09PT09PT09PT09PT09PT09
PT09Cjxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO2ZvciBNM1VBIG9mIENoaW5hIE1vYmlsZS5wcHQ8
YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDs9PT09PT09PT09PT09PT09PT09PT09PT09PT09PTxicj4m
Z3Q7Jmd0Ozxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO1RoZSBSZXF1aXJlbWVudCBhbmQgUHJvcG9z
YWw8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDsgZm9yIE0zVUEgU3BlY2lmaWNhdGlvbiBFeHRlbnNp
b248YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDsgb2YgQ2hpbmEgTW9iaWxlPGJyPgomZ3Q7Jmd0Owo8
YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtDaGVuIFh1PGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Q2hp
bmEgTW9iaWxlPGJyPiZndDsmZ3Q7PGJyPiZndDsmZ3Q7PGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7
Q29udGVudDxicj4mZ3Q7Jmd0Ozxicj4mZ3Q7Jmd0OyBCYWNrZ3JvdW5kPGJyPiZndDsmZ3Q7Jm5i
c3A7Jm5ic3A7UHJvYmxlbSBEZXNjcmlwdGlvbjxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO1JlcXVp
cmVtZW50IGZvciBFeHRlbnNpb24gb2YgUkZDNDY2Njxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO1By
b3Bvc2FsIGZvciBFeHRlbnNpb24gb2YgUkZDNDY2Ngo8YnI+Jmd0OyZndDs8YnI+Jmd0OyZndDs8
YnI+Jmd0OyZndDs8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtCYWNrZ3JvdW5kPGJyPiZndDsmZ3Q7
PGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7VGhlIGFwcGxpY2F0aW9uIG9mIFNJR1RSQU4gc3RhbmRh
cmQgZm9yIFNHIGhhcyBldmVyIHNvbHZlZCB0aGU8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtwcm9i
bGVtcyBvZiZuYnNwOyZuYnNwO05vLjcgU2lnbmFsbGluZyBTeXN0ZW0gSW50ZXJ3b3JraW5nIElQ
IGFuZDxicj4KCiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7dHJhbnNtaXNzaW9uIG9mJm5ic3A7Jm5ic3A7
YWNjZXNzIG5ldHdvcmsgc2lnbmFsbGluZyZuYnNwOyZuYnNwO2luJm5ic3A7Jm5ic3A7UjQgQ1Mg
Y29yZSBuZXR3b3JrLjxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO1RoZSB3b3JsZCB0cmVuZCBvZiBJ
UCBiZWFyZXIgZm9yIHNpZ25hbGxpbmcgd2lsbCBtYWtlIFNJR1RSQU48YnI+Jmd0OyZndDsmbmJz
cDsmbmJzcDtzdGFuZGFyZCB3aWRlbHkgdXNlZCBpbiBzaWduYWxsaW5nIG5ldHdvcmsuPGJyPiZn
dDsmZ3Q7Jm5ic3A7Jm5ic3A7VHJhZGl0aW9uYWwgYW5kIG5ldyBUZWxlY29tIGNhcnJpZXJzIGlt
cGxlbWVudCBzaWduYWxsaW5nIG92ZXIgSVAgdG8KPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7UmVk
dWNlJm5ic3A7Jm5ic3A7Y29zdCBmb3IgZXh0ZW5kZWQgY2FwYWNpdHk8YnI+Jmd0OyZndDsmbmJz
cDsmbmJzcDtSZW1vdmVzIHRoZSBsaW5rcy9saW5rc2V0IGxpbWl0YXRpb24gaW1wb3NlZCBieSB0
cmFkaXRpb25hbCBURE08YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtsaW5rc2V0cyBmb3IgdHJhZmZp
YyBncm93dGg8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtBdm9pZCBtYWpvciBuZXR3b3JrIHJlLWVu
Z2luZWVyaW5nIGFzIHRyYWZmaWMgZ3Jvd3MKPGJyPiZndDsmZ3Q7PGJyPiZndDsmZ3Q7Jm5ic3A7
Jm5ic3A7U0lHVFJBTiBpcyBhbHNvIGltcG9ydGFudCB0byBDaGluYSBNb2JpbGU8YnI+Jmd0OyZn
dDsmbmJzcDsmbmJzcDtBcHBseWluZyB0byB0aGUgTmMgaW50ZXJmYWNlIG9mIEJJQ0MgbmV0d29y
ayB0byB0cmFuc3BvcnQgQklDQzxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO21lc3NhZ2VzPGJyPiZn
dDsmZ3Q7Jm5ic3A7Jm5ic3A7QXBwbHlpbmcgdG8gdGhlIGludGVyZmFjZSBiZXR3ZWVuIE1TQyBT
ZXJ2ZXIgYW5kIGVtYmVkZWQgU0cgdG8KPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7dHJhbnNwb3J0
IGFjY2VzcyBuZXR3b3JrIHNpZ25hbGxpbmc8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtBcHBseWlu
ZyB0byBzaWduYWxsaW5nIG5ldHdvcms8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDt0aGUgaW50ZXJm
YWNlIGJldHdlZW4gSVBTRVBzoaqhqk0zVUE8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDt0aGUgaW50
ZXJmYWNlIGJldHdlZW4gSVBTVFBzoaqhqk0yUEE8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDt0aGUg
aW50ZXJmYWNlIGJldHdlZW4gSVBTRVAgYW5kIElQU1RQoaqhqk0zVUEKPGJyPiZndDsmZ3Q7PGJy
PiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7UHJvYmxlbSBkZXNjcmlwdGlvbjxicj4mZ3Q7Jmd0Ozxicj4m
Z3Q7Jmd0OyZuYnNwOyZuYnNwO00zVUEgc3BlY2lmaWNhdGlvbiBkb2VzbiYjMzk7dCZuYnNwOyZu
YnNwO2RlZmluZSBzaWduYWxpbmcgbmV0d29yayZuYnNwOyZuYnNwO21hbmFnZW1lbnQ8YnI+Jmd0
OyZndDsmbmJzcDsmbmJzcDtmdW5jdGlvbjxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO00zVUEgaXMg
ZGVzaWduZWQgZm9yIFNHLUlQU0VQIGFuZCBJUFNFUC1JUFNFUCBhcHBsaWNhdGlvbnMsCjxicj4m
Z3Q7Jmd0OyZuYnNwOyZuYnNwO3RoZXJlZm9yZSBuZXR3b3JrIGxldmVsIG1hbmFnZW1lbnQgZnVu
Y3Rpb24gaXNuJiMzOTt0IHJlcXVpcmVkLjxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO1NTTk0gbWVz
c2FnZXMgZGVmaW5lZCBpbiBNM1VBIGFyZSBvbmx5IHVzZWQgZm9yIGludGVyd29ya2luZyB3aXRo
PGJyPiZndDsmZ3Q7IFNTNy48YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtDaGluYSBNb2JpbGUgaGFz
IGEgbGFyZ2UgbnVtYmVyIG9mIHN1YnNjcmliZXJzIGFuZCBoYXMgYnVpbHQgdGhlCjxicj4mZ3Q7
Jmd0OyZuYnNwOyZuYnNwO2xhcmdlc3Qgc29mdC1zd2l0Y2ggbmV0d29yayBpbiB0aGUgd29ybGQs
IGl0cyBzaWduYWxpbmcgbmV0d29yazxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO3dpbGwgYmUgdGhl
IG11bHRpLWxldmVsIGFuZCBtdWx0aS1hcmVhIG1vZGUuPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7
SXQgd2lsbCBoYXMgdHdvIHNpZ25hbGxpbmcgcm91dGVpbmcmbmJzcDsmbmJzcDtzY2VuZTpJUFNF
UC1JUFNUUC1JUFNUUC1JUFNFUDxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO2FuZCBJUFNFUC1JUFNU
UC1JUFNFUAo8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtUaGUgaW50ZXJ3b3JraW5nJm5ic3A7Jm5i
c3A7ZnVuY3Rpb24gd2l0aCBNVFAzIGluIE0zVUEgY2FuIHJlYWxpemUgdGhlPGJyPiZndDsmZ3Q7
Jm5ic3A7Jm5ic3A7c2lnbmFsaW5nIG5ldHdvcmsmbmJzcDsmbmJzcDttYW5hZ2VtZW50IGZvciZu
YnNwOyZuYnNwO0lQU0VQLUlQU1RQLUlQU1RQLUlQU0VQIHNjZW5lOzxicj4mZ3Q7Jmd0OyZuYnNw
OyZuYnNwO0N1cnJlbnQgTTNVQSZuYnNwOyZuYnNwO2NhbiBub3QmbmJzcDsmbmJzcDtyZWFsaXpl
IHRoZSBzaWduYWxpbmcgbmV0d29yayZuYnNwOyZuYnNwO21hbmFnZW1lbnQKPGJyPiZndDsmZ3Q7
Jm5ic3A7Jm5ic3A7Zm9yJm5ic3A7Jm5ic3A7SVBTRVAtSVBTVFAtSVBTRVAgc2NlbmUuPGJyPiZn
dDsmZ3Q7PGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7UmVxdWlyZW1lbnQgZm9yIEV4dGVuc2lvbiBv
ZiBSRkM0NjY2PGJyPiZndDsmZ3Q7PGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7RGVmaW5lIHRoZSBB
cHBsaWNhdGlvbiBmb3IgSVBTVFAtSVBTRVAgaW50ZXJmYWNlLihTdGlsbCB1c2VzIFNHUC08YnI+
Jmd0OyZndDsmbmJzcDsmbmJzcDtBU1AgcHJvY2VkdXJlcykKPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5i
c3A7RGVmaW5lIHRoZSBzaWduYWxsaW5nIG5ldHdvcmsgbWFuYWdlbWVudCBmdW5jdGlvbqOsbWVz
c2FnZXMgLGFuZDxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO3Byb2NlZHVyZXMuKERlc2NyaWJlIGhv
dyB0byB1c2UgU1NOTSBtZXNzYWdlcyB0byBzdXBwb3J0IHNpZ25hbGluZzxicj4mZ3Q7Jmd0OyZu
YnNwOyZuYnNwO25ldHdvcmsgbWFuYWdlbWVudCBmb3IgSVBTRVAtKE0zVUEpLUlQU1RQLShNM1VB
KS1JUFNFUCBzY2VuZS4gKQo8YnI+Jmd0OyZndDs8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtQcm9w
b3NhbCBmb3IgRXh0ZW5zaW9uIG9mIFJGQzQ2NjY8YnI+Jmd0OyZndDs8YnI+Jmd0OyZndDsmbmJz
cDsmbmJzcDsxo6lBZGQgZGlmZmVyZW50IGtpbmRzIG9mIHJvdXRpbmcgc2NlbmVzIGFwcGxpY2F0
aW9ucyBmb3IgSVBTRVAtPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7SVBTVFAgaW50ZXJmYWNlIGlu
IFNlY3Rpb24gMS41Jm5ic3A7Jm5ic3A7JiMzOTtTYW1wbGUgQ29uZmlndXJhdGlvbiAmIzM5Oy4K
PGJyPgomZ3Q7Jmd0OyZuYnNwOyZuYnNwOzKjqUFkZCB0aGUgTTNVQSBzaWduYWxsaW5nIG5ldHdv
cmsgbWFuYWdlbWVudCBmdW5jdGlvbiBpbiBTZWN0aW9uPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7
MS40Jm5ic3A7Jm5ic3A7JiMzOTtGdW5jdGlvbmFsIEFyZWFzJiMzOTsuPGJyPiZndDsmZ3Q7Jm5i
c3A7Jm5ic3A7M6OpIEFkZCB0aGUgQ2xpZW50L1NlcnZlciBNb2RlbCBmb3IgSVBTVFAtSVBTRVAg
aW50ZXJmYWNlIGluPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7U2VjdGlvbiAxLjQuOAouJm5ic3A7
Jm5ic3A7JiMzOTtTQ1RQIENsaWVudC9TZXJ2ZXIgTW9kZWwmIzM5Oy4KPGJyPiZndDsmZ3Q7Jm5i
c3A7Jm5ic3A7NKOpRXh0ZW5kIHRoZSBEVVBVIG1lc3NhZ2UgY29kZSBpbiBDaGFwdGVyIDMgJiMz
OTtNM1VBIFByb3RvY29sPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7RWxlbWVudHMmIzM5Oy48YnI+
Jmd0OyZndDsmbmJzcDsmbmJzcDs1o6lBZGQgdGhlIHNpZ25hbGxpbmcgbmV0d29yayBtYW5hZ2Vt
ZW50IHByb2NlZHVyZSBpbiBDaGFwdGVyPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7NCYjMzk7cHJv
Y2VkdXJlJiMzOTsuPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7NikgQWRkIHRoZSByZXF1aXJlbWVu
dCBvZiBNdWx0aSB1c2VyIGRhdGEgc3RyZWFtcyBmb3IgTTNVQSBvdmVyCjxicj4mZ3Q7Jmd0OyZu
YnNwOyZuYnNwO1NDVFAgQXBwbGljYXRpb24gaW4gU2VjdGlvbiAxLjQuNyAmIzM5OyBTQ1RQIFN0
cmVhbSBNYXBwaW5nJiMzOTsuPGJyPiZndDsmZ3Q7PGJyPiZndDsmZ3Q7IChUaGF0JiMzOTtzIGFs
bCBmb3IgTTNVQSk8YnI+Jmd0OyZndDs8YnI+Jmd0OyZndDs8YnI+Jmd0OyZndDsmbmJzcDsmbmJz
cDs9PT09PT09PT09PT09PT09PT09PT09PT09PT09PTxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO2Zv
ciBNMlBBIG9mIENoaW5hIApNb2JpbGUucHB0Cjxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwOz09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PGJyPiZndDsmZ3Q7PGJyPiZndDsmZ3Q7Jm5ic3A7Jm5i
c3A7VGhlIFJlcXVpcmVtZW50IGFuZCBQcm9wb3NhbDxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwOyBm
b3IgTTJQQSBTcGVjaWZpY2F0aW9uIFJldmlzaW9uPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7IG9m
IENoaW5hIE1vYmlsZTxicj4mZ3Q7Jmd0Ozxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO0NoZW4gWHU8
YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtDaGluYSBNb2JpbGUKPGJyPiZndDsmZ3Q7PGJyPiZndDsm
Z3Q7Jm5ic3A7Jm5ic3A7Q29udGVudDxicj4mZ3Q7Jmd0Ozxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNw
O0JhY2tncm91bmQ8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtQcm9ibGVtIERlc2NyaXB0aW9uPGJy
PiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7UmVxdWlyZW1lbnQgZm9yIFJldmlzaW9uIG9mIFJGQzQxNjU8
YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtQcm9wb3NhbCBmb3IgUmV2aXNpb24gb2YgUkZDNDE2NTxi
cj4mZ3Q7Jmd0Ozxicj4mZ3Q7Jmd0Owo8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtCYWNrZ3JvdW5k
PGJyPiZndDsmZ3Q7PGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7TTJQQSBwcm90b2NvbCBpcyBhIHBl
ZXIgdG8gcGVlciBwcm90b2NvbCwgaXQgbm90IG9ubHkgc3VwcG9ydHM8YnI+Jmd0OyZndDsmbmJz
cDsmbmJzcDtzZWFtbGVzcyBtYW5hZ2VtZW50IG9wZXJhdGlvbiBvZiBNVFAzIHByb3RvY29sIHBl
ZXJzIG92ZXIgYW4gSVA8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtuZXR3b3JrIGNvbm5lY3Rpb24s
IGJ1dCBhbHNvIHJlbW92ZXMgdGhlIGxpbmtzL2xpbmtzZXQgbGltaXRhdGlvbgo8YnI+Jmd0OyZn
dDsmbmJzcDsmbmJzcDtpbXBvc2VkIGJ5IHRyYWRpdGlvbmFsIFRETSBsaW5rc2V0cyBmb3IgdHJh
ZmZpYyBncm93dGguPGJyPiZndDsmZ3Q7PGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7VGhlIFN0YW5k
YXJkaXphdGlvbiBvZiBNMlBBIGlzIGJlaGluZCB0aGUgYXBwbGljYXRpb24gb2YgaXQuPGJyPiZn
dDsmZ3Q7Jm5ic3A7Jm5ic3A7QWx0aG91Z2ggdGhlIFJGQyBlZGl0aW9uIGlzIHJlbGVhc2VkIGlu
IDIwMDUsIE0yUEEgaXMgd2lkZWx5IHVzZWQKPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7aW4gdGhl
Jm5ic3A7Jm5ic3A7U2lnbmFsaW5nIG5ldHdvcmsgcmVidWlsZGluZyBvdmVyIElQIGZvciB0cmFk
aXRpb25hbDxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO29wZXJhdG9ycyBhbmQgaW4gdGhlIFNpZ25h
bGluZyBuZXR3b3JrIGNvbnN0cnVjdGlvbiBmb3ImbmJzcDsmbmJzcDtuZXc8YnI+Jmd0OyZndDsm
bmJzcDsmbmJzcDtvcGVyYXRvcnMmbmJzcDsmbmJzcDtzaW5jZSAyMDAyLjxicj4mZ3Q7Jmd0Ozxi
cj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO1ZhcmlvdXMgZHJhZnQgZWRpdGlvbnMgYW5kIHRoZSBtYWpv
ciBkaWZmZXJlbmNlcyBiZXR3ZWVuIHRoZW0gbWFrZQo8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtw
cm9ibGVtcyB3aGVuIG9uZSZuYnNwOyZuYnNwO0lQU1RQIHByb3ZpZGVyIGludGVyd29ya2luZyB3
aXRoIGFub3RoZXIuPGJyPiZndDsmZ3Q7PGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7UHJvYmxlbSBE
ZXNjcmlwdGlvbjxicj4mZ3Q7Jmd0Ozxicj4mZ3Q7Jmd0Ozxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNw
O1JGQzQxNjUgbmVlZHMgdG8gYmUgc3VwcGxlbWVudGVkIGFuZCByZXZpc2VkIKO6PGJyPiZndDsm
Z3Q7Jm5ic3A7Jm5ic3A7U29tZSZuYnNwOyZuYnNwO3Byb2NlZHVyZXMmbmJzcDsmbmJzcDthcmUm
bmJzcDsmbmJzcDtkZXNjcmliZWQgYSBsaXR0bGUgYml0IHNpbXBseSBhbmQgcmVmZXJyZWQKPGJy
PiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7dG8gTVRQMiBkaXJlY3RseSAsJm5ic3A7Jm5ic3A7d2hpY2gm
bmJzcDsmbmJzcDttYWtlcyBJUFNUUCZuYnNwOyZuYnNwO3Byb3ZpZGVycyByZWFsaXppbmcgdGhl
PGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7cHJvY2VkdXJlcyBpbiBkaWZmZXJlbnQgd2F5cyAsZm9y
Jm5ic3A7Jm5ic3A7dGhlcmUmIzM5O3MgZGlmZmVyZW5jZSBiZXR3ZWVuIE1UUDI8YnI+Jmd0OyZn
dDsmbmJzcDsmbmJzcDthbmQgTTJQQSBpbiBzb21lIGFzcGVjdHMuJm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Ljxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO1NvbWUgSVBTVFAgcHJv
dmlkZXJzIHVzZSB0aGUgc2FtZSBpZGVhIGFzIE1UUDIKPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7
T3RoZXJzIHRha2UgdGhlIHJlbGF0aW9uIGJldHdlZW4gTTJQQSBhbmQgU0NUUCBpbnRvIGFjY291
bnQuPGJyPiZndDsmZ3Q7PGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7VDcgaXNuJiMzOTt0IGRlZmlu
ZWQgYW5kIGdpdmVuIHRoZSByYW5nZSwgd2hpY2ggbWFrZXMgSVBTVFAgcHJvdmlkZXJzPGJyPiZn
dDsmZ3Q7Jm5ic3A7Jm5ic3A7cmVhbGl6aW5nIGl0IGluIGRpZmZlcmVudCB3YXlzLjxicj4mZ3Q7
Jmd0Owo8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtIb3cgdG8gZmlsbCBpbiBhbmQgcHJvY2VzcyBG
U04gYW5kIEJTTiBpbiBNMlBBIEhlYWRlciBpc24mIzM5O3Q8YnI+Jmd0OyZndDsmbmJzcDsmbmJz
cDtkZWZpbmVkIGNsZWFybHkuPGJyPiZndDsmZ3Q7PGJyPiZndDsmZ3Q7PGJyPiZndDsmZ3Q7Jm5i
c3A7Jm5ic3A7UmVxdWlyZW1lbnQgZm9yIFJldmlzaW9uIG9mIFJGQzQxNjU8YnI+Jmd0OyZndDs8
YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtTdXBwbGVtZW50IHRoZSBkZXNjcmlwdGlvbiBvZiB0aGUg
d2hvbGUgaWRlYSBmb3IgTGluayBBbGlnbm1lbnQKPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7cHJv
Y2VkdXJlIGFuZCBQcm9jZXNzb3IgT3V0YWdlIHByb2NlZHVyZS48YnI+Jmd0OyZndDsmbmJzcDsm
bmJzcDtTdXBwbGVtZW50IHRoZSBkZWZpbml0aW9uIGFuZCByYW5nZSBvZiBNMlBBIFRpbWVycy48
YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtTdXBwbGVtZW50IHRoZSBydWxlcyBvZiB1c2FnZSBvZiBG
U04gYW5kIEJTTiBpbiBNMlBBIEhlYWRlci48YnI+Jmd0OyZndDs8YnI+Jmd0OyZndDs8YnI+Cgom
Z3Q7Jmd0OyZuYnNwOyZuYnNwO1Byb3Bvc2FsIGZvciBSZXZpc2lvbiBvZiBSRkM0MTY1PGJyPiZn
dDsmZ3Q7PGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7MaOpU3VwcGxlbWVudCB0aGUgd2hvbGUgaWRl
YSAsIHRoZSBwaGFzZSBkaXZpc2lvbiAsIHRoZSBjb3JyZWxhdGVkPGJyPiZndDsmZ3Q7Jm5ic3A7
Jm5ic3A7bWVzc2FnZXMgYW5kIFRpbWVycyBvZiBMaW5rIEFsaWdubWVudCBwcm9jZWR1cmUgaW4g
U2VjdGlvbiA0LjEuMy48YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDsyo6lTdXBwbGVtZW50IHRoZSB3
aG9sZSBpZGVhIG9mIFByb2Nlc3NvciBPdXRhZ2UgcHJvY2VkdXJlLCBhbmQKPGJyPiZndDsmZ3Q7
Jm5ic3A7Jm5ic3A7ZGVzY3JpYmUgdGhlIHJ1bGVzIG9mIExQTyBhbmQgUlBPIHByb2Nlc3Npbmcg
c2VwYXJhdGVseSAuPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7M6OpU3VwcGxlbWVudCB0aGUgcnVs
ZXMgb2YgdXNhZ2Ugb2YgRlNOIGFuZCBCU04gaW4gTTJQQSBIZWFkZXIgaW48YnI+Jmd0OyZndDsm
bmJzcDsmbmJzcDtTZWN0aW9uIDQuMi4xPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7NKOpU3VwcGxl
bWVudCB0aGUgZGVmaW5pdGlvbiBhbmQgcmFuZ2Ugb2YgTTJQQSBUaW1lcnMgaW4gQXBwZW5kaXgu
Cjxicj4mZ3Q7Jmd0Ozxicj4mZ3Q7Jmd0OyAoVGhhdCYjMzk7cyBhbGwgZm9yIE0yUEEpPGJyPiZn
dDsmZ3Q7PGJyPiZndDsmZ3Q7IENoZW4gWHU8YnI+Jmd0OyZndDsgQ2hpbmEgTW9iaWxlPGJyPiZn
dDsmZ3Q7IDxhIGhyZWY9Im1haWx0bzpjaGVueHVAY2hpbmFtb2JpbGUuY29tIiB0YXJnZXQ9Il9i
bGFuayIgb25jbGljaz0icmV0dXJuIHRvcC5qcy5PcGVuRXh0TGluayh3aW5kb3csZXZlbnQsdGhp
cykiPgpjaGVueHVAY2hpbmFtb2JpbGUuY29tPC9hPjxicj4mZ3Q7Jmd0OyBfX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo8YnI+Jmd0OyZndDsgU2lndHJhbiBt
YWlsaW5nIGxpc3Q8YnI+Jmd0OyZndDsgPGEgaHJlZj0ibWFpbHRvOlNpZ3RyYW5AaWV0Zi5vcmci
IHRhcmdldD0iX2JsYW5rIiBvbmNsaWNrPSJyZXR1cm4gdG9wLmpzLk9wZW5FeHRMaW5rKHdpbmRv
dyxldmVudCx0aGlzKSI+U2lndHJhbkBpZXRmLm9yZzwvYT48YnI+Jmd0OyZndDsgPGEgaHJlZj0i
aHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc2lndHJhbiIgdGFyZ2V0PSJf
YmxhbmsiIG9uY2xpY2s9InJldHVybiB0b3AuanMuT3BlbkV4dExpbmsod2luZG93LGV2ZW50LHRo
aXMpIj4KaHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc2lndHJhbjwvYT48
YnI+Cjxicj48YnI+PGJyPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fPGJyPlNpZ3RyYW4gbWFpbGluZyBsaXN0PGJyPjxhIGhyZWY9Im1haWx0bzpTaWd0cmFu
QGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayIgb25jbGljaz0icmV0dXJuIHRvcC5qcy5PcGVuRXh0
TGluayh3aW5kb3csZXZlbnQsdGhpcykiPlNpZ3RyYW5AaWV0Zi5vcmc8L2E+PGJyPjxhIGhyZWY9
Imh0dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NpZ3RyYW4iIHRhcmdldD0i
X2JsYW5rIiBvbmNsaWNrPSJyZXR1cm4gdG9wLmpzLk9wZW5FeHRMaW5rKHdpbmRvdyxldmVudCx0
aGlzKSI+Cmh0dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NpZ3RyYW4KPC9h
Pjxicj48YnI+PC9ibG9ja3F1b3RlPjwvZGl2Pjxicj4K
------=_Part_5001_105760.1185540454561--





From tsvwg-bounces@ietf.org Fri Jul 27 08:51:39 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEPIA-0006CI-Cj; Fri, 27 Jul 2007 08:51:38 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IEPI8-00068E-TY
	for tsvwg-confirm+ok@megatron.ietf.org; Fri, 27 Jul 2007 08:51:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEPI8-000681-JA
	for tsvwg@ietf.org; Fri, 27 Jul 2007 08:51:36 -0400
Received: from wx-out-0506.google.com ([66.249.82.224])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEPI7-0003GP-4m
	for tsvwg@ietf.org; Fri, 27 Jul 2007 08:51:36 -0400
Received: by wx-out-0506.google.com with SMTP id h27so725128wxd
	for <tsvwg@ietf.org>; Fri, 27 Jul 2007 05:51:34 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=hYbpv59zjKR5OQW6xpYX7GlJpuKm6L53gmAY2hals+X3wGAtEH6ScU6dxW5/a5PBh+MMT6pHAtlxSEmaj4Ye1o8X5Msq1NlcSnd9QhsMBYHJCRZEFtNvoM5nnWF9lrB/n0ZerDc1l7353Ns4esXfCO/vu9QJEZfp9v4DC0Xb7QM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=jVqGthC35Hp+11JDmFkEYvH413Y+Jwacxsu96M5pkIBc6zuovsrHOFnkthGEIEKvinh/Bq/4tfPEwbzfCWO3i2RkFxpTsmncLUyDAXDDryKgzbi+122fCDGz91low3trRQEi1IWhRSnbRkBVw77VB/k5yMI3LTmn974D1pvvr0o=
Received: by 10.100.140.6 with SMTP id n6mr2571041and.1185540694606;
	Fri, 27 Jul 2007 05:51:34 -0700 (PDT)
Received: by 10.90.83.12 with HTTP; Fri, 27 Jul 2007 05:51:34 -0700 (PDT)
Message-ID: <6dbbbf160707270551g73b85ff9x81ae3aebd3949475@mail.gmail.com>
Date: Fri, 27 Jul 2007 18:21:34 +0530
From: "Ankit Kumar Sharma" <ankisharma@gmail.com>
To: chenxu@chinamobile.com
In-Reply-To: <6dbbbf160707270547q4ddde312g95feca7dde736e6b@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_5021_16154724.1185540694520"
References: <OF24565732.6AADA0AB-ON48257325.00301996@chinamobile.com>
	<6dbbbf160707270547q4ddde312g95feca7dde736e6b@mail.gmail.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1b82b4ba484bbe86cdae6d5f8b2d2ccb
Cc: sigtran@ietf.org, tsvwg@ietf.org
Subject: [Tsvwg] Re: [Sigtran] The requiremnts and
	proposalsforM2PA/M3UA/SCTPExtension from China Mobile
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

------=_Part_5021_16154724.1185540694520
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: base64
Content-Disposition: inline

Y2hlbnh1LAoKT24gNy8yNy8wNywgs8LQ8SA8Y2hlbnh1QGNoaW5hbW9iaWxlLmNvbSA+IHdyb3Rl
Ogo+Cj4gRGVhciBNaWNoYWVsIFR1ZXhlbiwKPgo+Cj4gPiAgICAxLiBXaGF0IGRvZXMgInVuaW9u
aXplIG9mIHRoZSBwcmltYXJ5IHBhdGhzIGJldHdlZW4gbm9kZXMiIG1lYW4/Cj4gICAgSXQgbWVh
bnOjrGZvciBvbmUgbXVsdGktaG9tZWQgU0NUUCBlbmRwb2ludCx0aGUgcHJpbWFyeSBwYXRoo6hz
b3VyY2UgSVAKPiBhZGRyZXNzPUlQMS0tLWRlc3RpbmF0aW9uIElQPUlQMqOpIHNoYWxsIGJlIHRo
ZSBzYW1lIGFzIHRoZSByZW1vdGUgZW5kcG9pbnQncwo+ICggc291cmNlIElQIGFkZHJlc3M9SVAy
LS0tZGVzdGluYXRpb24gSVA9SVAxICApCj4KPiAgICBNYW55IHZlbmRlcnMgaW1wbGVtZW50IE11
bHRpLWhvbWluZyBpbiB0aGUgZm9sbG93aW5nIHdheToKPgo+ICAgICBvbmUgbXVsdGktaG9tZWQg
U0NUUCBlbmRwb2ludCBoYXMgdHdvIGxvY2FsIElQIGFkZHJlc3NlcyhJUDEvSVAyKSBhbmQKPiB0
d28gcmVtb3RlIElQIGFkZHJlc3MoSVAzL0lQNCkgd2l0aGluIGFuIGFzc29jaWF0aW9uLgo+ICAg
ICBUaGVyZSdzIHR3byBwYXRocyB3aXRoaW4gYW4gYXNzb2NpYXRpb246SVAxLUlQMyxhbmQgSVAy
LUlQNC5ub3QgNAo+IHBhdGhzLgo+Cj4gICAgIEZvciBleGFtcGxlLCBlbmRwb2ludDEgaGFzIHR3
byBsb2NhbCBJUCBhZGRyZXNzZXMoSVAxL0lQMimjrCBhbmQKPiBlbmRwb2ludDIgaGFzIHR3byBs
b2NhbCBJUCBhZGRyZXNzZXMoSVAzL0lQNCkuCj4KPiBpZiB0d28gZW5kcG9pbnRzJyBwcmltYXJ5
IHBhdGggaXNuJ3QgdGhlIHNhbWUsdGhhdCBpcyBlbmRwb2ludDEgdXNlCj4gSVAxLUlQMyBhcyB0
aGUgcHJpbWFyeSBwYXRoLCB1c2UgSVAyLUlQNCBhcyB0aGUgc2Vjb25kIHBhdGg7ICBlbmRwb2lu
dDIgdXNlCj4gSVAzLUlQMiBhcyB0aGUgcHJpbWFyeSBwYXRoLCB1c2UgSVA0LUlQMSBhcyB0aGUg
c2Vjb25kIHBhdGguCj4KPiAgICAgVGhlc2UgdHdvIGVuZHBvaW50cyBjYW4ndCAgc2VuZCBkYXRh
IHRvIGVhY2ggb3RoZXIgc3VjY2Vzc2Z1bGx5Lgo+CiA+ICAgICAyLiBOb3Qgc3VyZSBhYm91dCB0
aGUgU0FDSyBpc3N1ZTogWW91IGFyZSBjdXJyZW50bHkgYWxsb3dlZCB0bwoKPiA+ICAgIHNlbmQg
dGhlIFNBQ0sgYmFjayB0byBhbiBhZGRyZXNzZXMgZGlmZmVyZW50IGZyb20gdGhlIHNvdXJjZQo+
ID4gICAgYWRkcmVzcyBvZiB0aGUgY29ycmVzcG9uZGluZyBEQVRBIGNodW5rLiBBcyBmYXIgYXMg
SSBrbm93Cj4gPiAgICBpdCBpcyBvbmx5IGEgU0hPVUxEIGRlc2NyaWJpbmcgdGhhdCB5b3Ugc2Vu
ZCB0aGUgU0FDSyBiYWNrCj4gPiAgICB0byB0aGUgc291cmNlIGFkZHJlc3Mgb2YgdGhlIERBVEEg
Y2h1bmsuCj4KPiAgICAgIFlvdSBhcmUgcmlnaHQsaXQgaXMgb25seSBhIFNIT1VMRCBkZXNjcmli
aW5nIHRoYXQgeW91IHNlbmQgdGhlIFNBQ0sKPiBiYWNrCj4gICAgdG8gdGhlIHNvdXJjZSBhZGRy
ZXNzIG9mIHRoZSBEQVRBIGNodW5rIGluIFJGQzI5NjAuCj4gICAgICAgVGhhdCdzIHdoeSB3ZSBn
ZXQgaW4gdHJvdWJsZSBpbiBtdWx0aS1ob21pbmcgc2l0dWF0aW9uLgo+ICAgICAgIElmIHRoZSAg
cGF0aCB0byB0aGUgc291cmNlIGFkZHJlc3Mgb2YgdGhlIERBVEEgY2h1bmsgaXMKPiB1bnJlYWNo
YWJsZaOsdGhlIHNhY2sgY2FuJ3Qgc2VuZCB0byB0aGUgcmVtb3RlIGVuZHBvaW50IGZvciBldmVy
IGFsdGhvdWdoIHRoZQo+IG90aGVyIHBhdGggaXMgYXZhaWxhYmxlLlNvb24gdGhlIG90aGVyIHBh
dGggd2lsbCBiZSBmYWlsdXJlLgoKCkkgZG9uJ3Qgc2VlIGFueSBwcm9ibGVtIGluIFNDVFAgUkZD
IGZvciBhYm92ZSBtZW50aW9uZWQgc2NlbmFyaW8uCkFzIHBlciBSRkMgMjcxOSwgZm9sbG93aW5n
IGlzIHRoZSBkZWZpbmF0aW9uIG9mICJTSE9VTEQiOgoKMy4gU0hPVUxEICAgVGhpcyB3b3JkLCBv
ciB0aGUgYWRqZWN0aXZlICJSRUNPTU1FTkRFRCIsIG1lYW4gdGhhdCB0aGVyZQogIG1heSBleGlz
dCB2YWxpZCByZWFzb25zIGluIHBhcnRpY3VsYXIgY2lyY3Vtc3RhbmNlcyB0byBpZ25vcmUgYQog
ICBwYXJ0aWN1bGFyIGl0ZW0sIGJ1dCB0aGUgZnVsbCBpbXBsaWNhdGlvbnMgbXVzdCBiZSB1bmRl
cnN0b29kIGFuZAoKCiAgIGNhcmVmdWxseSB3ZWlnaGVkIGJlZm9yZSBjaG9vc2luZyBhIGRpZmZl
cmVudCBjb3Vyc2UuCgoKCk5vdyBwbGVhc2UgbG9vayBhdCBmb2xsb3dpbmcgZXhjZXJwdCBmcm9t
IHNlY3Rpb24gNi40KE11bHRpLWhvbWVkIFNDVFAKRW5kcG9pbnRzKSBvZiBTQ1RQIFJGQzoKIgoK
V2hlbiBhIHJlY2VpdmVyIG9mIGEgZHVwbGljYXRlIERBVEEgY2h1bmsgc2VuZHMgYSBTQUNLIHRv
IGEgbXVsdGktCiAgIGhvbWVkIGVuZHBvaW50IGl0IE1BWSBiZSBiZW5lZmljaWFsIHRvIHZhcnkg
dGhlIGRlc3RpbmF0aW9uIGFkZHJlc3MKICAgYW5kIG5vdCB1c2UgdGhlIHNvdXJjZSBhZGRyZXNz
IG9mIHRoZSBEQVRBIGNodW5rLiAgVGhlIHJlYXNvbiBiZWluZwoKCiAgIHRoYXQgcmVjZWl2aW5n
IGEgZHVwbGljYXRlIGZyb20gYSBtdWx0aS1ob21lZCBlbmRwb2ludCBtaWdodCBpbmRpY2F0ZQog
ICB0aGF0IHRoZSByZXR1cm4gcGF0aCAoYXMgc3BlY2lmaWVkIGluIHRoZSBzb3VyY2UgYWRkcmVz
cyBvZiB0aGUgREFUQQogICBjaHVuaykgZm9yIHRoZSBTQUNLIGlzIGJyb2tlbi4KIgoKU28gYXMg
cGVyIHlvdXIgc2NlbmFyaW8sIGlmIFNPVVJDRSBhZGRyZXNzIG9mIHNlbmRlciBpcyBub3QgcmVh
Y2hhYmxlIHRoZW4Kb3VyIFNBQ0sgd291bGQgYmUgbG9zdC4gQWZ0ZXIgUlRPIGV4cGlyeSBhdCBz
ZW5kZXIsIHNlbmRlciB3b3VsZCBhZ2FpbiB0cnkKdG8gc2VuZCB0aGUgREFUQSBjaHVuay4gTm93
LCByZWNlaXZlciBjb3VsZCBiZWhhdmUgYXMgcGVyIGFib3ZlIG1lbnRpb25lZApleGNlcnB0LgoK
QmVzdCBSZWdhcmQKPiBDaGVuIFh1Cj4gQ2hpbmEgTW9iaWxlCj4gY2hlbnh1QGNoaW5hbW9iaWxl
LmNvbQo+Cj4KPgo+Cj4KPgo+Cj4gPT09PT09PSAyMDA3LTA3LTI2IDIyOjIzOjIwIMT61NrAtNDF
1tDQtLXAo7o9PT09PT09Cj4KPiA+RGVhciBhbGwsCj4gPgo+ID5JJ20gc2VuZGluZyB0aGlzIGFs
c28gdG8gVFNWV0csIHNpbmNlIHRoZSBTQ1RQIGRpc2N1c3Npb24gaGFzIHRvIGJlCj4gPmRvbmUg
dGhlIHRoYXQgV0cuCj4gPgo+ID5BZGRyZXNzaW5nIHRoZSBTQ1RQIHN0YXRlbWVudDoKPiA+Cj4g
PjEuIFdoYXQgZG9lcyAidW5pb25pemUgb2YgdGhlIHByaW1hcnkgcGF0aHMgYmV0d2VlbiBub2Rl
cyIgbWVhbj8KPiA+Mi4gTm90IHN1cmUgYWJvdXQgdGhlIFNBQ0sgaXNzdWU6IFlvdSBhcmUgY3Vy
cmVudGx5IGFsbG93ZWQgdG8KPiA+ICAgIHNlbmQgdGhlIFNBQ0sgYmFjayB0byBhbiBhZGRyZXNz
ZXMgZGlmZmVyZW50IGZyb20gdGhlIHNvdXJjZQo+ID4gICAgYWRkcmVzcyBvZiB0aGUgY29ycmVz
cG9uZGluZyBEQVRBIGNodW5rLiBBcyBmYXIgYXMgSSBrbm93Cj4gPiAgICBpdCBpcyBvbmx5IGEg
U0hPVUxEIGRlc2NyaWJpbmcgdGhhdCB5b3Ugc2VuZCB0aGUgU0FDSyBiYWNrCj4gPiAgICB0byB0
aGUgc291cmNlIGFkZHJlc3Mgb2YgdGhlIERBVEEgY2h1bmsuCj4gPgo+ID5CZXN0IHJlZ2FyZHMK
PiA+TWljaGFlbAo+ID4KPiA+T24gSnVsIDI2LCAyMDA3LCBhdCA0OjIyIEFNLCBjaGVueHUgd3Jv
dGU6Cj4gPgo+ID4+IERlYXIgYWxsLAo+ID4+Cj4gPj4gICAgICBTb3JyeSB0byBzdWJtaXQgdGhl
IHJhciBmaWxlISBBbmQgdGhhbmtzIFJ1aSBHb21lcyEKPiA+Pgo+ID4+IFRoZSBjb250ZW50cyBv
ZiB0aGUgYXR0YWNobWVudHMgYXJlIGFzIGZvbGxvd3M6Cj4gPj4KPiA+PiAgID09PT09PT09PT09
PT09PT09PT09PT09PT09PT09Cj4gPj4gICBmb3IgU0NUUCBvZiBDaGluYSBNb2JpbGUucHB0Cj4g
Pj4gID09PT09PT09PT09PT09PT09PT09PT09PT09PT09Cj4gPj4KPiA+PiAgVGhlIFJlcXVpcmVt
ZW50IGFuZCBQcm9wb3NhbAo+ID4+ICAgZm9yIFNDVFAgU3BlY2lmaWNhdGlvbiBFeHRlbnNpb24K
PiA+PiAgIG9mIENoaW5hIE1vYmlsZQo+ID4+Cj4gPj4gIENoZW4gWHUgLCBaaGFuZyBIYW8KPiA+
PiAgQ2hpbmEgTW9iaWxlCj4gPj4KPiA+PiAgQ29udGVudAo+ID4+Cj4gPj4gIEJhY2tncm91bmQK
PiA+PiAgUHJvYmxlbSBkZXNjcmlwdGlvbgo+ID4+ICBSZXF1aXJlbWVudCBmb3IgU3VwcGxlbWVu
dCBvZiBSRkM0NDYwCj4gPj4gIFByb3Bvc2FsIGZvciBTdXBwbGVtZW50IG9mIFJGQzQ0NjAKPiA+
Pgo+ID4+ICBCYWNrZ3JvdW5kCj4gPj4KPiA+PiAgVGhlIHdvcmxkIHRyZW5kIG9mIElQIGJlYXJl
ciBmb3Igc2lnbmFsbGluZyB3aWxsIG1ha2UgU0lHVFJBTgo+ID4+ICBzdGFuZGFyZCB3aWRlbHkg
dXNlZCBpbiBzaWduYWxsaW5nIG5ldHdvcmsuCj4gPj4gIFRyYWRpdGlvbmFsIGFuZCBuZXcgVGVs
ZWNvbSBjYXJyaWVycyBpbXBsZW1lbnQgc2lnbmFsbGluZyBvdmVyIElQIHRvCj4gPj4gIFJlZHVj
ZSAgY29zdCBmb3IgZXh0ZW5kZWQgY2FwYWNpdHkKPiA+PiAgUmVtb3ZlcyB0aGUgbGlua3MvbGlu
a3NldCBsaW1pdGF0aW9uIGltcG9zZWQgYnkgdHJhZGl0aW9uYWwgVERNCj4gPj4gIGxpbmtzZXRz
IGZvciB0cmFmZmljIGdyb3d0aAo+ID4+ICBBdm9pZCBtYWpvciBuZXR3b3JrIHJlLWVuZ2luZWVy
aW5nIHdoZW4gdHJhZmZpYyBncm93cwo+ID4+ICBTQ1RQIGlzIHRoZSBiYXNpcyBvZiBzaWduYWxs
aW5nIG92ZXIgSVAKPiA+Pgo+ID4+ICBTQ1RQIGlzIGFsc28gaW1wb3J0YW50IHRvIENoaW5hIE1v
YmlsZQo+ID4+ICBBcHBseWluZyB0byB0aGUgTmMgaW50ZXJmYWNlIHRvIHRyYW5zcG9ydCBCSUND
IG1lc3NhZ2VzCj4gPj4gIEFwcGx5aW5nIHRvIHRoZSBNYyBpbnRlcmZhY2UgdG8gdHJhbnNwb3J0
IEguMjQ4IG1lc3NhZ2VzCj4gPj4gIEFwcGx5aW5nIHRvIHRoZSBpbnRlcmZhY2UgYmV0d2VlbiBN
U0MgU2VydmVyIGFuZCB0aGUgZW1iZWRkZWQgU0cgdG8KPiA+PiAgdHJhbnNwb3J0IGFjY2VzcyBu
ZXR3b3JrIHNpZ25hbGxpbmcKPiA+PiAgQXBwbHlpbmcgdG8gc2lnbmFsbGluZyBuZXR3b3JrCj4g
Pj4gIHRoZSBpbnRlcmZhY2UgYmV0d2VlbiBJUFNFUHMKPiA+PiAgdGhlIGludGVyZmFjZSBiZXR3
ZWVuIElQU1RQcwo+ID4+ICB0aGUgaW50ZXJmYWNlIGJldHdlZW4gSVBTRVAgYW5kIElQU1RQCj4g
Pj4KPiA+Pgo+ID4+IFByb2JsZW0gZGVzY3JpcHRpb24KPiA+Pgo+ID4+IENoaW5hIE1vYmlsZSBo
YXMgYSBsYXJnZSBudW1iZXIgb2Ygc3Vic2NyaWJlcnMgYW5kIGhhcyBidWlsdCB0aGUKPiA+PiAg
bGFyZ2VzdCBzb2Z0LXN3aXRjaCBuZXR3b3JrIGluIHRoZSB3b3JsZC4gVGhlIHNpZ25hbGluZyB0
cmFmZmljCj4gPj4gIGJldHdlZW4gdHdvIG5vZGVzIGlzIHZlcnkgbGFyZ2UuCj4gPj4gIENoaW5h
IE1vYmlsZSBpbXBvcnRzIG11bHRpLXZlbmRlcidzIHByb2R1Y3RzLiBUaGUgY29tcGF0aWJpbGl0
eQo+ID4+ICBiZXR3ZWVuIGRpZmZlcmVudCB2ZW5kZXIncyBwcm9kdWN0cyBpcyBpbXBvcnRhbnQu
Cj4gPj4gIFRoZSBpbGxlZ2liaWxpdHkgb2YgTXVsdGktaG9taW5nIG1lY2hhbmlzbSBpbiBTQ1RQ
IHByb3RvY29sIGJyaW5ncwo+ID4+ICBvbiBjb21wYXRpYmlsaXR5IHByb2JsZW1zCj4gPj4gIFND
VFAgZGlkIG5vdCBkZWZpbmUgdGhlIG1lY2hhbmlzbSBob3cgdGhlIFNBQ0sgaXMgc2VuZCBiYWNr
IHRvCj4gPj4gIGVuZHBvaW50IGJ5IG90aGVyIHBhdGggd2hlbiBvbmUgcGF0aCBmYWlscy4KPiA+
PiAgU0NUUCBkZWZpbmVzIG11bHRpLWhvbWluZywgYnV0IGl0IGRpZCBub3QgZGVmaW5lIGhvdyB0
aGUgcHJpbWFyeQo+ID4+ICBwYXRoIGNhbiBiZSB1bmlvbml6ZWQgYmV0d2VlbiB0d28gbm9kZXMu
Cj4gPj4gIFJlcXVpcmVtZW50IGZvciBTdXBwbGVtZW50IG9mIFJGQzQ0NjAKPiA+PiAgRGVmaW5l
IHRoZSBtZWNoYW5pc20gdGhhdCBTQUNLIGlzIHNlbmQgYmFjayB0byBlbmRwb2ludCBieSB0aGUK
PiA+PiAgc2Vjb25kYXJ5IHBhdGggaWYgdGhlIHByaW1hcnkgcGF0aCBmYWlscyAuCj4gPj4gIERl
ZmluZSAgdGhlIG1lY2hhbmlzbSBob3cgdGhlIHByaW1hcnkgcGF0aCBjYW4gYmUgdW5pb25pemVk
IGJldHdlZW4KPiA+PiAgdHdvIG5vZGVzLgo+ID4+Cj4gPj4KPiA+PiAgUHJvcG9zYWwgZm9yIFN1
cHBsZW1lbnQgb2YgUkZDNDQ2MAo+ID4+Cj4gPj4KPiA+PiAgMaOpQWRkIHRoZSBtZWNoYW5pc20g
aG93IHRoZSBwcmltYXJ5IHBhdGggY2FuIGJlIHVuaW9uaXplZCBiZXR3ZWVuCj4gPj4gIHR3byBu
b2RlcyBpbiBTZWN0aW9uIDUgICdBc3NvY2lhdGlvbiBJbml0aWFsaXphdGlvbiAnLgo+ID4+ICAy
o6kgQWRkIHRoZSBtZWNoYW5pc20gdGhhdCBTQUNLIGlzIHNlbmQgYmFjayB0byBlbmRwb2ludCBi
eSB0aGUKPiA+PiAgc2Vjb25kYXJ5IHBhdGggaWYgdGhlIHByaW1hcnkgcGF0aCBmYWlscyBpbiBT
ZWN0aW9uIDYuMgo+ID4+ICAnQWNrbm93bGVkZ2VtZW50IG9uIFJlY2VwdGlvbiBvZiBEQVRBIENo
dW5rcyAnLgo+ID4+Cj4gPj4gKFRoYXQncyBhbGwgZm9yIFNDVFApCj4gPj4KPiA+Pgo+ID4+ICA9
PT09PT09PT09PT09PT09PT09PT09PT09PT09PQo+ID4+ICBmb3IgTTNVQSBvZiBDaGluYSBNb2Jp
bGUucHB0Cj4gPj4gID09PT09PT09PT09PT09PT09PT09PT09PT09PT09Cj4gPj4KPiA+PiAgVGhl
IFJlcXVpcmVtZW50IGFuZCBQcm9wb3NhbAo+ID4+ICAgZm9yIE0zVUEgU3BlY2lmaWNhdGlvbiBF
eHRlbnNpb24KPiA+PiAgIG9mIENoaW5hIE1vYmlsZQo+ID4+Cj4gPj4gIENoZW4gWHUKPiA+PiAg
Q2hpbmEgTW9iaWxlCj4gPj4KPiA+Pgo+ID4+ICBDb250ZW50Cj4gPj4KPiA+PiBCYWNrZ3JvdW5k
Cj4gPj4gIFByb2JsZW0gRGVzY3JpcHRpb24KPiA+PiAgUmVxdWlyZW1lbnQgZm9yIEV4dGVuc2lv
biBvZiBSRkM0NjY2Cj4gPj4gIFByb3Bvc2FsIGZvciBFeHRlbnNpb24gb2YgUkZDNDY2Ngo+ID4+
Cj4gPj4KPiA+Pgo+ID4+ICBCYWNrZ3JvdW5kCj4gPj4KPiA+PiAgVGhlIGFwcGxpY2F0aW9uIG9m
IFNJR1RSQU4gc3RhbmRhcmQgZm9yIFNHIGhhcyBldmVyIHNvbHZlZCB0aGUKPiA+PiAgcHJvYmxl
bXMgb2YgIE5vLjcgU2lnbmFsbGluZyBTeXN0ZW0gSW50ZXJ3b3JraW5nIElQIGFuZAo+ID4+ICB0
cmFuc21pc3Npb24gb2YgIGFjY2VzcyBuZXR3b3JrIHNpZ25hbGxpbmcgIGluICBSNCBDUyBjb3Jl
IG5ldHdvcmsuCj4gPj4gIFRoZSB3b3JsZCB0cmVuZCBvZiBJUCBiZWFyZXIgZm9yIHNpZ25hbGxp
bmcgd2lsbCBtYWtlIFNJR1RSQU4KPiA+PiAgc3RhbmRhcmQgd2lkZWx5IHVzZWQgaW4gc2lnbmFs
bGluZyBuZXR3b3JrLgo+ID4+ICBUcmFkaXRpb25hbCBhbmQgbmV3IFRlbGVjb20gY2FycmllcnMg
aW1wbGVtZW50IHNpZ25hbGxpbmcgb3ZlciBJUCB0bwo+ID4+ICBSZWR1Y2UgIGNvc3QgZm9yIGV4
dGVuZGVkIGNhcGFjaXR5Cj4gPj4gIFJlbW92ZXMgdGhlIGxpbmtzL2xpbmtzZXQgbGltaXRhdGlv
biBpbXBvc2VkIGJ5IHRyYWRpdGlvbmFsIFRETQo+ID4+ICBsaW5rc2V0cyBmb3IgdHJhZmZpYyBn
cm93dGgKPiA+PiAgQXZvaWQgbWFqb3IgbmV0d29yayByZS1lbmdpbmVlcmluZyBhcyB0cmFmZmlj
IGdyb3dzCj4gPj4KPiA+PiAgU0lHVFJBTiBpcyBhbHNvIGltcG9ydGFudCB0byBDaGluYSBNb2Jp
bGUKPiA+PiAgQXBwbHlpbmcgdG8gdGhlIE5jIGludGVyZmFjZSBvZiBCSUNDIG5ldHdvcmsgdG8g
dHJhbnNwb3J0IEJJQ0MKPiA+PiAgbWVzc2FnZXMKPiA+PiAgQXBwbHlpbmcgdG8gdGhlIGludGVy
ZmFjZSBiZXR3ZWVuIE1TQyBTZXJ2ZXIgYW5kIGVtYmVkZWQgU0cgdG8KPiA+PiAgdHJhbnNwb3J0
IGFjY2VzcyBuZXR3b3JrIHNpZ25hbGxpbmcKPiA+PiAgQXBwbHlpbmcgdG8gc2lnbmFsbGluZyBu
ZXR3b3JrCj4gPj4gIHRoZSBpbnRlcmZhY2UgYmV0d2VlbiBJUFNFUHOhqqGqTTNVQQo+ID4+ICB0
aGUgaW50ZXJmYWNlIGJldHdlZW4gSVBTVFBzoaqhqk0yUEEKPiA+PiAgdGhlIGludGVyZmFjZSBi
ZXR3ZWVuIElQU0VQIGFuZCBJUFNUUKGqoapNM1VBCj4gPj4KPiA+PiAgUHJvYmxlbSBkZXNjcmlw
dGlvbgo+ID4+Cj4gPj4gIE0zVUEgc3BlY2lmaWNhdGlvbiBkb2Vzbid0ICBkZWZpbmUgc2lnbmFs
aW5nIG5ldHdvcmsgIG1hbmFnZW1lbnQKPiA+PiAgZnVuY3Rpb24KPiA+PiAgTTNVQSBpcyBkZXNp
Z25lZCBmb3IgU0ctSVBTRVAgYW5kIElQU0VQLUlQU0VQIGFwcGxpY2F0aW9ucywKPiA+PiAgdGhl
cmVmb3JlIG5ldHdvcmsgbGV2ZWwgbWFuYWdlbWVudCBmdW5jdGlvbiBpc24ndCByZXF1aXJlZC4K
PiA+PiAgU1NOTSBtZXNzYWdlcyBkZWZpbmVkIGluIE0zVUEgYXJlIG9ubHkgdXNlZCBmb3IgaW50
ZXJ3b3JraW5nIHdpdGgKPiA+PiBTUzcuCj4gPj4gIENoaW5hIE1vYmlsZSBoYXMgYSBsYXJnZSBu
dW1iZXIgb2Ygc3Vic2NyaWJlcnMgYW5kIGhhcyBidWlsdCB0aGUKPiA+PiAgbGFyZ2VzdCBzb2Z0
LXN3aXRjaCBuZXR3b3JrIGluIHRoZSB3b3JsZCwgaXRzIHNpZ25hbGluZyBuZXR3b3JrCj4gPj4g
IHdpbGwgYmUgdGhlIG11bHRpLWxldmVsIGFuZCBtdWx0aS1hcmVhIG1vZGUuCj4gPj4gIEl0IHdp
bGwgaGFzIHR3byBzaWduYWxsaW5nIHJvdXRlaW5nICBzY2VuZTpJUFNFUC1JUFNUUC1JUFNUUC1J
UFNFUAo+ID4+ICBhbmQgSVBTRVAtSVBTVFAtSVBTRVAKPiA+PiAgVGhlIGludGVyd29ya2luZyAg
ZnVuY3Rpb24gd2l0aCBNVFAzIGluIE0zVUEgY2FuIHJlYWxpemUgdGhlCj4gPj4gIHNpZ25hbGlu
ZyBuZXR3b3JrICBtYW5hZ2VtZW50IGZvciAgSVBTRVAtSVBTVFAtSVBTVFAtSVBTRVAgc2NlbmU7
Cj4gPj4gIEN1cnJlbnQgTTNVQSAgY2FuIG5vdCAgcmVhbGl6ZSB0aGUgc2lnbmFsaW5nIG5ldHdv
cmsgIG1hbmFnZW1lbnQKPiA+PiAgZm9yICBJUFNFUC1JUFNUUC1JUFNFUCBzY2VuZS4KPiA+Pgo+
ID4+ICBSZXF1aXJlbWVudCBmb3IgRXh0ZW5zaW9uIG9mIFJGQzQ2NjYKPiA+Pgo+ID4+ICBEZWZp
bmUgdGhlIEFwcGxpY2F0aW9uIGZvciBJUFNUUC1JUFNFUCBpbnRlcmZhY2UuKFN0aWxsIHVzZXMg
U0dQLQo+ID4+ICBBU1AgcHJvY2VkdXJlcykKPiA+PiAgRGVmaW5lIHRoZSBzaWduYWxsaW5nIG5l
dHdvcmsgbWFuYWdlbWVudCBmdW5jdGlvbqOsbWVzc2FnZXMgLGFuZAo+ID4+ICBwcm9jZWR1cmVz
LihEZXNjcmliZSBob3cgdG8gdXNlIFNTTk0gbWVzc2FnZXMgdG8gc3VwcG9ydCBzaWduYWxpbmcK
PiA+PiAgbmV0d29yayBtYW5hZ2VtZW50IGZvciBJUFNFUC0oTTNVQSktSVBTVFAtKE0zVUEpLUlQ
U0VQIHNjZW5lLiApCj4gPj4KPiA+PiAgUHJvcG9zYWwgZm9yIEV4dGVuc2lvbiBvZiBSRkM0NjY2
Cj4gPj4KPiA+PiAgMaOpQWRkIGRpZmZlcmVudCBraW5kcyBvZiByb3V0aW5nIHNjZW5lcyBhcHBs
aWNhdGlvbnMgZm9yIElQU0VQLQo+ID4+ICBJUFNUUCBpbnRlcmZhY2UgaW4gU2VjdGlvbiAxLjUg
ICdTYW1wbGUgQ29uZmlndXJhdGlvbiAnLgo+ID4+ICAyo6lBZGQgdGhlIE0zVUEgc2lnbmFsbGlu
ZyBuZXR3b3JrIG1hbmFnZW1lbnQgZnVuY3Rpb24gaW4gU2VjdGlvbgo+ID4+ICAxLjQgICdGdW5j
dGlvbmFsIEFyZWFzJy4KPiA+PiAgM6OpIEFkZCB0aGUgQ2xpZW50L1NlcnZlciBNb2RlbCBmb3Ig
SVBTVFAtSVBTRVAgaW50ZXJmYWNlIGluCj4gPj4gIFNlY3Rpb24gMS40LjggLiAgJ1NDVFAgQ2xp
ZW50L1NlcnZlciBNb2RlbCcuCj4gPj4gIDSjqUV4dGVuZCB0aGUgRFVQVSBtZXNzYWdlIGNvZGUg
aW4gQ2hhcHRlciAzICdNM1VBIFByb3RvY29sCj4gPj4gIEVsZW1lbnRzJy4KPiA+PiAgNaOpQWRk
IHRoZSBzaWduYWxsaW5nIG5ldHdvcmsgbWFuYWdlbWVudCBwcm9jZWR1cmUgaW4gQ2hhcHRlcgo+
ID4+ICA0J3Byb2NlZHVyZScuCj4gPj4gIDYpIEFkZCB0aGUgcmVxdWlyZW1lbnQgb2YgTXVsdGkg
dXNlciBkYXRhIHN0cmVhbXMgZm9yIE0zVUEgb3Zlcgo+ID4+ICBTQ1RQIEFwcGxpY2F0aW9uIGlu
IFNlY3Rpb24gMS40LjcgJyBTQ1RQIFN0cmVhbSBNYXBwaW5nJy4KPiA+Pgo+ID4+IChUaGF0J3Mg
YWxsIGZvciBNM1VBKQo+ID4+Cj4gPj4KPiA+PiAgPT09PT09PT09PT09PT09PT09PT09PT09PT09
PT0KPiA+PiAgZm9yIE0yUEEgb2YgQ2hpbmEgTW9iaWxlLnBwdAo+ID4+ICA9PT09PT09PT09PT09
PT09PT09PT09PT09PT09PQo+ID4+Cj4gPj4gIFRoZSBSZXF1aXJlbWVudCBhbmQgUHJvcG9zYWwK
PiA+PiAgIGZvciBNMlBBIFNwZWNpZmljYXRpb24gUmV2aXNpb24KPiA+PiAgIG9mIENoaW5hIE1v
YmlsZQo+ID4+Cj4gPj4gIENoZW4gWHUKPiA+PiAgQ2hpbmEgTW9iaWxlCj4gPj4KPiA+PiAgQ29u
dGVudAo+ID4+Cj4gPj4gIEJhY2tncm91bmQKPiA+PiAgUHJvYmxlbSBEZXNjcmlwdGlvbgo+ID4+
ICBSZXF1aXJlbWVudCBmb3IgUmV2aXNpb24gb2YgUkZDNDE2NQo+ID4+ICBQcm9wb3NhbCBmb3Ig
UmV2aXNpb24gb2YgUkZDNDE2NQo+ID4+Cj4gPj4KPiA+PiAgQmFja2dyb3VuZAo+ID4+Cj4gPj4g
IE0yUEEgcHJvdG9jb2wgaXMgYSBwZWVyIHRvIHBlZXIgcHJvdG9jb2wsIGl0IG5vdCBvbmx5IHN1
cHBvcnRzCj4gPj4gIHNlYW1sZXNzIG1hbmFnZW1lbnQgb3BlcmF0aW9uIG9mIE1UUDMgcHJvdG9j
b2wgcGVlcnMgb3ZlciBhbiBJUAo+ID4+ICBuZXR3b3JrIGNvbm5lY3Rpb24sIGJ1dCBhbHNvIHJl
bW92ZXMgdGhlIGxpbmtzL2xpbmtzZXQgbGltaXRhdGlvbgo+ID4+ICBpbXBvc2VkIGJ5IHRyYWRp
dGlvbmFsIFRETSBsaW5rc2V0cyBmb3IgdHJhZmZpYyBncm93dGguCj4gPj4KPiA+PiAgVGhlIFN0
YW5kYXJkaXphdGlvbiBvZiBNMlBBIGlzIGJlaGluZCB0aGUgYXBwbGljYXRpb24gb2YgaXQuCj4g
Pj4gIEFsdGhvdWdoIHRoZSBSRkMgZWRpdGlvbiBpcyByZWxlYXNlZCBpbiAyMDA1LCBNMlBBIGlz
IHdpZGVseSB1c2VkCj4gPj4gIGluIHRoZSAgU2lnbmFsaW5nIG5ldHdvcmsgcmVidWlsZGluZyBv
dmVyIElQIGZvciB0cmFkaXRpb25hbAo+ID4+ICBvcGVyYXRvcnMgYW5kIGluIHRoZSBTaWduYWxp
bmcgbmV0d29yayBjb25zdHJ1Y3Rpb24gZm9yICBuZXcKPiA+PiAgb3BlcmF0b3JzICBzaW5jZSAy
MDAyLgo+ID4+Cj4gPj4gIFZhcmlvdXMgZHJhZnQgZWRpdGlvbnMgYW5kIHRoZSBtYWpvciBkaWZm
ZXJlbmNlcyBiZXR3ZWVuIHRoZW0gbWFrZQo+ID4+ICBwcm9ibGVtcyB3aGVuIG9uZSAgSVBTVFAg
cHJvdmlkZXIgaW50ZXJ3b3JraW5nIHdpdGggYW5vdGhlci4KPiA+Pgo+ID4+ICBQcm9ibGVtIERl
c2NyaXB0aW9uCj4gPj4KPiA+Pgo+ID4+ICBSRkM0MTY1IG5lZWRzIHRvIGJlIHN1cHBsZW1lbnRl
ZCBhbmQgcmV2aXNlZCCjugo+ID4+ICBTb21lICBwcm9jZWR1cmVzICBhcmUgIGRlc2NyaWJlZCBh
IGxpdHRsZSBiaXQgc2ltcGx5IGFuZCByZWZlcnJlZAo+ID4+ICB0byBNVFAyIGRpcmVjdGx5ICwg
IHdoaWNoICBtYWtlcyBJUFNUUCAgcHJvdmlkZXJzIHJlYWxpemluZyB0aGUKPiA+PiAgcHJvY2Vk
dXJlcyBpbiBkaWZmZXJlbnQgd2F5cyAsZm9yICB0aGVyZSdzIGRpZmZlcmVuY2UgYmV0d2VlbiBN
VFAyCj4gPj4gIGFuZCBNMlBBIGluIHNvbWUgYXNwZWN0cy4gICAgICAuCj4gPj4gIFNvbWUgSVBT
VFAgcHJvdmlkZXJzIHVzZSB0aGUgc2FtZSBpZGVhIGFzIE1UUDIKPiA+PiAgT3RoZXJzIHRha2Ug
dGhlIHJlbGF0aW9uIGJldHdlZW4gTTJQQSBhbmQgU0NUUCBpbnRvIGFjY291bnQuCj4gPj4KPiA+
PiAgVDcgaXNuJ3QgZGVmaW5lZCBhbmQgZ2l2ZW4gdGhlIHJhbmdlLCB3aGljaCBtYWtlcyBJUFNU
UCBwcm92aWRlcnMKPiA+PiAgcmVhbGl6aW5nIGl0IGluIGRpZmZlcmVudCB3YXlzLgo+ID4+Cj4g
Pj4gIEhvdyB0byBmaWxsIGluIGFuZCBwcm9jZXNzIEZTTiBhbmQgQlNOIGluIE0yUEEgSGVhZGVy
IGlzbid0Cj4gPj4gIGRlZmluZWQgY2xlYXJseS4KPiA+Pgo+ID4+Cj4gPj4gIFJlcXVpcmVtZW50
IGZvciBSZXZpc2lvbiBvZiBSRkM0MTY1Cj4gPj4KPiA+PiAgU3VwcGxlbWVudCB0aGUgZGVzY3Jp
cHRpb24gb2YgdGhlIHdob2xlIGlkZWEgZm9yIExpbmsgQWxpZ25tZW50Cj4gPj4gIHByb2NlZHVy
ZSBhbmQgUHJvY2Vzc29yIE91dGFnZSBwcm9jZWR1cmUuCj4gPj4gIFN1cHBsZW1lbnQgdGhlIGRl
ZmluaXRpb24gYW5kIHJhbmdlIG9mIE0yUEEgVGltZXJzLgo+ID4+ICBTdXBwbGVtZW50IHRoZSBy
dWxlcyBvZiB1c2FnZSBvZiBGU04gYW5kIEJTTiBpbiBNMlBBIEhlYWRlci4KPiA+Pgo+ID4+Cj4g
Pj4gIFByb3Bvc2FsIGZvciBSZXZpc2lvbiBvZiBSRkM0MTY1Cj4gPj4KPiA+PiAgMaOpU3VwcGxl
bWVudCB0aGUgd2hvbGUgaWRlYSAsIHRoZSBwaGFzZSBkaXZpc2lvbiAsIHRoZSBjb3JyZWxhdGVk
Cj4gPj4gIG1lc3NhZ2VzIGFuZCBUaW1lcnMgb2YgTGluayBBbGlnbm1lbnQgcHJvY2VkdXJlIGlu
IFNlY3Rpb24gNC4xLjMuCj4gPj4gIDKjqVN1cHBsZW1lbnQgdGhlIHdob2xlIGlkZWEgb2YgUHJv
Y2Vzc29yIE91dGFnZSBwcm9jZWR1cmUsIGFuZAo+ID4+ICBkZXNjcmliZSB0aGUgcnVsZXMgb2Yg
TFBPIGFuZCBSUE8gcHJvY2Vzc2luZyBzZXBhcmF0ZWx5IC4KPiA+PiAgM6OpU3VwcGxlbWVudCB0
aGUgcnVsZXMgb2YgdXNhZ2Ugb2YgRlNOIGFuZCBCU04gaW4gTTJQQSBIZWFkZXIgaW4KPiA+PiAg
U2VjdGlvbiA0LjIuMQo+ID4+ICA0o6lTdXBwbGVtZW50IHRoZSBkZWZpbml0aW9uIGFuZCByYW5n
ZSBvZiBNMlBBIFRpbWVycyBpbiBBcHBlbmRpeC4KPiA+Pgo+ID4+IChUaGF0J3MgYWxsIGZvciBN
MlBBKQo+ID4+Cj4gPj4gQ2hlbiBYdQo+ID4+IENoaW5hIE1vYmlsZQo+ID4+IGNoZW54dUBjaGlu
YW1vYmlsZS5jb20KPiA+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXwo+ID4+IFNpZ3RyYW4gbWFpbGluZyBsaXN0Cj4gPj4gU2lndHJhbkBpZXRmLm9yZwo+
ID4+IGh0dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NpZ3RyYW4KPgo+Cj4K
PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+IFNpZ3Ry
YW4gbWFpbGluZyBsaXN0Cj4gU2lndHJhbkBpZXRmLm9yZwo+IGh0dHBzOi8vd3d3MS5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL3NpZ3RyYW4KPgo+Cg==
------=_Part_5021_16154724.1185540694520
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: base64
Content-Disposition: inline

PHNwYW4gY2xhc3M9ImdtYWlsX3F1b3RlIj48L3NwYW4+Y2hlbnh1LDxicj48YnI+PGRpdj48c3Bh
biBjbGFzcz0icSI+PHNwYW4gY2xhc3M9ImdtYWlsX3F1b3RlIj5PbiA3LzI3LzA3LCA8YiBjbGFz
cz0iZ21haWxfc2VuZGVybmFtZSI+s8LQ8TwvYj4gJmx0OzxhIGhyZWY9Im1haWx0bzpjaGVueHVA
Y2hpbmFtb2JpbGUuY29tIiB0YXJnZXQ9Il9ibGFuayIgb25jbGljaz0icmV0dXJuIHRvcC5qcy5P
cGVuRXh0TGluayh3aW5kb3csZXZlbnQsdGhpcykiPgpjaGVueHVAY2hpbmFtb2JpbGUuY29tCjwv
YT4mZ3Q7IHdyb3RlOjwvc3Bhbj48YmxvY2txdW90ZSBjbGFzcz0iZ21haWxfcXVvdGUiIHN0eWxl
PSJib3JkZXItbGVmdDogMXB4IHNvbGlkIHJnYigyMDQsIDIwNCwgMjA0KTsgbWFyZ2luOiAwcHQg
MHB0IDBwdCAwLjhleDsgcGFkZGluZy1sZWZ0OiAxZXg7Ij4KRGVhciBNaWNoYWVsIFR1ZXhlbiw8
YnI+PGJyPjxicj4mZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7MS4gV2hhdCBkb2VzICZxdW90
O3VuaW9uaXplIG9mIHRoZSBwcmltYXJ5IHBhdGhzIGJldHdlZW4gbm9kZXMmcXVvdDsgbWVhbj88
YnI+Jm5ic3A7Jm5ic3A7Ckl0IG1lYW5zo6xmb3Igb25lIG11bHRpLWhvbWVkIFNDVFAgZW5kcG9p
bnQsdGhlIHByaW1hcnkgcGF0aKOoc291cmNlIElQCmFkZHJlc3M9SVAxLS0tZGVzdGluYXRpb24g
SVA9SVAyo6kgc2hhbGwgYmUgdGhlIHNhbWUgYXMgdGhlIHJlbW90ZQplbmRwb2ludCYjMzk7cyAo
IHNvdXJjZSBJUCBhZGRyZXNzPUlQMi0tLWRlc3RpbmF0aW9uIElQPUlQMSZuYnNwOyZuYnNwOyk8
YnI+PGJyPiZuYnNwOyZuYnNwOyBNYW55IHZlbmRlcnMgaW1wbGVtZW50IE11bHRpLWhvbWluZyBp
biB0aGUgZm9sbG93aW5nIHdheTo8YnI+PGJyPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO29uZQpt
dWx0aS1ob21lZCBTQ1RQIGVuZHBvaW50IGhhcyB0d28gbG9jYWwgSVAgYWRkcmVzc2VzKElQMS9J
UDIpIGFuZCB0d28KcmVtb3RlIElQIGFkZHJlc3MoSVAzL0lQNCkgd2l0aGluIGFuIGFzc29jaWF0
aW9uLjxicj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtUaGVyZSYjMzk7cyB0d28gcGF0aHMgd2l0
aGluIGFuIGFzc29jaWF0aW9uOklQMS1JUDMsYW5kIElQMi1JUDQubm90IDQgcGF0aHMuPGJyPjxi
cj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtGb3IKZXhhbXBsZSwgZW5kcG9pbnQxIGhhcyB0d28g
bG9jYWwgSVAgYWRkcmVzc2VzKElQMS9JUDIpo6wgYW5kIGVuZHBvaW50MgpoYXMgdHdvIGxvY2Fs
IElQIGFkZHJlc3NlcyhJUDMvSVA0KS48YnI+PGJyPmlmIHR3byBlbmRwb2ludHMmIzM5OyBwcmlt
YXJ5CnBhdGggaXNuJiMzOTt0IHRoZSBzYW1lLHRoYXQgaXMgZW5kcG9pbnQxIHVzZSBJUDEtSVAz
IGFzIHRoZSBwcmltYXJ5IHBhdGgsCnVzZSBJUDItSVA0IGFzIHRoZSBzZWNvbmQgcGF0aDsmbmJz
cDsmbmJzcDtlbmRwb2ludDIgdXNlIElQMy1JUDIgYXMgdGhlCnByaW1hcnkgcGF0aCwgdXNlIElQ
NC1JUDEgYXMgdGhlIHNlY29uZCBwYXRoLjxicj48YnI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
VGhlc2UgdHdvIGVuZHBvaW50cyBjYW4mIzM5O3QmbmJzcDsmbmJzcDtzZW5kIGRhdGEgdG8gZWFj
aCBvdGhlciBzdWNjZXNzZnVsbHkuPGJyPgo8L2Jsb2NrcXVvdGU+PGRpdj4mbmJzcDsmZ3Q7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IDIuIE5vdCBzdXJlIGFib3V0IHRoZSBTQUNLIGlzc3VlOiBZ
b3UgYXJlIGN1cnJlbnRseSBhbGxvd2VkIHRvPGJyPgo8L2Rpdj48YmxvY2txdW90ZSBjbGFzcz0i
Z21haWxfcXVvdGUiIHN0eWxlPSJib3JkZXItbGVmdDogMXB4IHNvbGlkIHJnYigyMDQsIDIwNCwg
MjA0KTsgbWFyZ2luOiAwcHQgMHB0IDBwdCAwLjhleDsgcGFkZGluZy1sZWZ0OiAxZXg7Ij4mZ3Q7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7c2VuZCB0aGUgU0FDSyBiYWNrIHRvIGFuIGFkZHJlc3Nl
cyBkaWZmZXJlbnQgZnJvbSB0aGUgc291cmNlCjxicj4mZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7YWRkcmVzcyBvZiB0aGUgY29ycmVzcG9uZGluZyBEQVRBIGNodW5rLiBBcyBmYXIgYXMgSSBr
bm93PGJyPiZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtpdCBpcyBvbmx5IGEgU0hPVUxEIGRl
c2NyaWJpbmcgdGhhdCB5b3Ugc2VuZCB0aGUgU0FDSyBiYWNrPGJyPiZndDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDt0byB0aGUgc291cmNlIGFkZHJlc3Mgb2YgdGhlIERBVEEgY2h1bmsuPGJyPjxi
cj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgWW91IGFyZSByaWdodCxpdCBpcyBvbmx5IGEgU0hP
VUxEIGRlc2NyaWJpbmcgdGhhdCB5b3Ugc2VuZCB0aGUgU0FDSyBiYWNrCjxicj4mbmJzcDsmbmJz
cDsgdG8gdGhlIHNvdXJjZSBhZGRyZXNzIG9mIHRoZSBEQVRBIGNodW5rIGluIFJGQzI5NjAuPGJy
PiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO1RoYXQmIzM5O3Mgd2h5IHdlIGdl
dCBpbiB0cm91YmxlIGluIG11bHRpLWhvbWluZyBzaXR1YXRpb24uPGJyPiZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwO0lmCnRoZSZuYnNwOyZuYnNwO3BhdGggdG8gdGhlIHNvdXJj
ZSBhZGRyZXNzIG9mIHRoZSBEQVRBIGNodW5rIGlzCnVucmVhY2hhYmxlo6x0aGUgc2FjayBjYW4m
IzM5O3Qgc2VuZCB0byB0aGUgcmVtb3RlIGVuZHBvaW50IGZvciBldmVyCmFsdGhvdWdoIHRoZSBv
dGhlciBwYXRoIGlzIGF2YWlsYWJsZS5Tb29uIHRoZSBvdGhlciBwYXRoIHdpbGwgYmUKZmFpbHVy
ZS48L2Jsb2NrcXVvdGU+PC9zcGFuPjxkaXY+PGJyPgpJIGRvbiYjMzk7dCBzZWUgYW55IHByb2Js
ZW0gaW4gU0NUUCBSRkMgZm9yIGFib3ZlIG1lbnRpb25lZCBzY2VuYXJpby48YnI+CkFzIHBlciBS
RkMgMjcxOSwgZm9sbG93aW5nIGlzIHRoZSBkZWZpbmF0aW9uIG9mICZxdW90O1NIT1VMRCZxdW90
Ozo8YnI+CjxwcmU+PGgyPjxhIG5hbWU9IjExNDA3YjdiODg0ZWNlYzZfMTE0MDc3OWQ1MTM4ZTNj
Ml9zMy4iPjMuIFNIT1VMRCAgIFRoaXMgd29yZCwgb3IgdGhlIGFkamVjdGl2ZSAmcXVvdDtSRUNP
TU1FTkRFRCZxdW90OywgbWVhbiB0aGF0IHRoZXJlPC9hPjwvaDI+ICAgbWF5IGV4aXN0IHZhbGlk
IHJlYXNvbnMgaW4gcGFydGljdWxhciBjaXJjdW1zdGFuY2VzIHRvIGlnbm9yZSBhPGJyPiAgIHBh
cnRpY3VsYXIgaXRlbSwgYnV0IHRoZSBmdWxsIGltcGxpY2F0aW9ucyBtdXN0IGJlIHVuZGVyc3Rv
b2QgYW5kCjxicj48YnI+PGJyPiAgIGNhcmVmdWxseSB3ZWlnaGVkIGJlZm9yZSBjaG9vc2luZyBh
IGRpZmZlcmVudCBjb3Vyc2UuPC9wcmU+Cjxicj4KPGJyPgpOb3cgcGxlYXNlIGxvb2sgYXQgZm9s
bG93aW5nIGV4Y2VycHQgZnJvbSBzZWN0aW9uIDYuNChNdWx0aS1ob21lZCBTQ1RQIEVuZHBvaW50
cykgb2YgU0NUUCBSRkM6PHNwYW4gY2xhc3M9InEiPjxicj4KJnF1b3Q7CjxwcmU+V2hlbiBhIHJl
Y2VpdmVyIG9mIGEgZHVwbGljYXRlIERBVEEgY2h1bmsgc2VuZHMgYSBTQUNLIHRvIGEgbXVsdGkt
PGJyPiAgIGhvbWVkIGVuZHBvaW50IGl0IE1BWSBiZSBiZW5lZmljaWFsIHRvIHZhcnkgdGhlIGRl
c3RpbmF0aW9uIGFkZHJlc3M8YnI+ICAgYW5kIG5vdCB1c2UgdGhlIHNvdXJjZSBhZGRyZXNzIG9m
IHRoZSBEQVRBIGNodW5rLiAgVGhlIHJlYXNvbiBiZWluZzxicj4KPGJyPjxicj4gICB0aGF0IHJl
Y2VpdmluZyBhIGR1cGxpY2F0ZSBmcm9tIGEgbXVsdGktaG9tZWQgZW5kcG9pbnQgbWlnaHQgaW5k
aWNhdGU8YnI+ICAgdGhhdCB0aGUgcmV0dXJuIHBhdGggKGFzIHNwZWNpZmllZCBpbiB0aGUgc291
cmNlIGFkZHJlc3Mgb2YgdGhlIERBVEE8YnI+ICAgY2h1bmspIGZvciB0aGUgU0FDSyBpcyBicm9r
ZW4uPGJyPiZxdW90Ozxicj48L3ByZT48L3NwYW4+CiA8L2Rpdj5TbyBhcyBwZXIgeW91ciBzY2Vu
YXJpbywgaWYgU09VUkNFIGFkZHJlc3Mgb2Ygc2VuZGVyIGlzIG5vdApyZWFjaGFibGUgdGhlbiBv
dXIgU0FDSyB3b3VsZCBiZSBsb3N0LiBBZnRlciBSVE8gZXhwaXJ5IGF0IHNlbmRlciwgc2VuZGVy
CndvdWxkIGFnYWluIHRyeSB0byBzZW5kIHRoZSBEQVRBIGNodW5rLiBOb3csIHJlY2VpdmVyIGNv
dWxkIGJlaGF2ZSBhcwpwZXIgYWJvdmUgbWVudGlvbmVkIGV4Y2VycHQuPGRpdj48c3BhbiBjbGFz
cz0iZSIgaWQ9InFfMTE0MDdiN2I4ODRlY2VjNl81Ij48YnI+Cjxicj48YmxvY2txdW90ZSBjbGFz
cz0iZ21haWxfcXVvdGUiIHN0eWxlPSJib3JkZXItbGVmdDogMXB4IHNvbGlkIHJnYigyMDQsIDIw
NCwgMjA0KTsgbWFyZ2luOiAwcHQgMHB0IDBwdCAwLjhleDsgcGFkZGluZy1sZWZ0OiAxZXg7Ij5C
ZXN0IFJlZ2FyZDxicj5DaGVuIFh1PGJyPkNoaW5hIE1vYmlsZTxicj48YSBocmVmPSJtYWlsdG86
Y2hlbnh1QGNoaW5hbW9iaWxlLmNvbSIgdGFyZ2V0PSJfYmxhbmsiIG9uY2xpY2s9InJldHVybiB0
b3AuanMuT3BlbkV4dExpbmsod2luZG93LGV2ZW50LHRoaXMpIj4KCmNoZW54dUBjaGluYW1vYmls
ZS5jb20KPC9hPjxicj48YnI+PGJyPjxicj48YnI+PGJyPjxicj48YnI+PT09PT09PSAyMDA3LTA3
LTI2IDIyOjIzOjIwIMT61NrAtNDF1tDQtLXAo7o9PT09PT09PGJyPjxicj4mZ3Q7RGVhciBhbGws
PGJyPiZndDs8YnI+Jmd0O0kmIzM5O20gc2VuZGluZyB0aGlzIGFsc28gdG8gVFNWV0csIHNpbmNl
IHRoZSBTQ1RQIGRpc2N1c3Npb24gaGFzIHRvIGJlPGJyPiZndDtkb25lIHRoZSB0aGF0IFdHLjxi
cj4mZ3Q7Cjxicj4KJmd0O0FkZHJlc3NpbmcgdGhlIFNDVFAgc3RhdGVtZW50Ojxicj4mZ3Q7PGJy
PiZndDsxLiBXaGF0IGRvZXMgJnF1b3Q7dW5pb25pemUgb2YgdGhlIHByaW1hcnkgcGF0aHMgYmV0
d2VlbiBub2RlcyZxdW90OyBtZWFuPzxicj4mZ3Q7Mi4gTm90IHN1cmUgYWJvdXQgdGhlIFNBQ0sg
aXNzdWU6IFlvdSBhcmUgY3VycmVudGx5IGFsbG93ZWQgdG88YnI+Jmd0OyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwO3NlbmQgdGhlIFNBQ0sgYmFjayB0byBhbiBhZGRyZXNzZXMgZGlmZmVyZW50IGZy
b20gdGhlIHNvdXJjZQo8YnI+Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO2FkZHJlc3Mgb2Yg
dGhlIGNvcnJlc3BvbmRpbmcgREFUQSBjaHVuay4gQXMgZmFyIGFzIEkga25vdzxicj4mZ3Q7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7aXQgaXMgb25seSBhIFNIT1VMRCBkZXNjcmliaW5nIHRoYXQg
eW91IHNlbmQgdGhlIFNBQ0sgYmFjazxicj4mZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7dG8g
dGhlIHNvdXJjZSBhZGRyZXNzIG9mIHRoZSBEQVRBIGNodW5rLjxicj4mZ3Q7PGJyPiZndDtCZXN0
IHJlZ2FyZHM8YnI+CgoKJmd0O01pY2hhZWw8YnI+Jmd0Ozxicj4mZ3Q7T24gSnVsIDI2LCAyMDA3
LCBhdCA0OjIyIEFNLCBjaGVueHUgd3JvdGU6PGJyPiZndDs8YnI+Jmd0OyZndDsgRGVhciBhbGws
PGJyPiZndDsmZ3Q7PGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7U29ycnkgdG8gc3VibWl0IHRoZSByYXIgZmlsZSEgQW5kIHRoYW5rcyBSdWkgR29tZXMhPGJy
PiZndDsmZ3Q7PGJyPiZndDsmZ3Q7IFRoZSBjb250ZW50cyBvZiB0aGUgYXR0YWNobWVudHMgYXJl
IGFzIGZvbGxvd3M6Cjxicj4mZ3Q7Jmd0Ozxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwOyA9PT09PT09
PT09PT09PT09PT09PT09PT09PT09PTxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwOyBmb3IgU0NUUCBv
ZiBDaGluYSBNb2JpbGUucHB0PGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT08YnI+Jmd0OyZndDs8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtUaGUgUmVx
dWlyZW1lbnQgYW5kIFByb3Bvc2FsPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7IGZvciBTQ1RQIFNw
ZWNpZmljYXRpb24gRXh0ZW5zaW9uCjxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwOyBvZiBDaGluYSBN
b2JpbGU8YnI+Jmd0OyZndDs8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtDaGVuIFh1ICwgWmhhbmcg
SGFvPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Q2hpbmEgTW9iaWxlPGJyPiZndDsmZ3Q7PGJyPiZn
dDsmZ3Q7Jm5ic3A7Jm5ic3A7Q29udGVudDxicj4mZ3Q7Jmd0Ozxicj4mZ3Q7Jmd0OyZuYnNwOyZu
YnNwO0JhY2tncm91bmQ8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtQcm9ibGVtIGRlc2NyaXB0aW9u
PGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7UmVxdWlyZW1lbnQgZm9yIFN1cHBsZW1lbnQgb2YgUkZD
NDQ2MAo8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtQcm9wb3NhbCBmb3IgU3VwcGxlbWVudCBvZiBS
RkM0NDYwPGJyPiZndDsmZ3Q7PGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7QmFja2dyb3VuZDxicj4m
Z3Q7Jmd0Ozxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO1RoZSB3b3JsZCB0cmVuZCBvZiBJUCBiZWFy
ZXIgZm9yIHNpZ25hbGxpbmcgd2lsbCBtYWtlIFNJR1RSQU48YnI+Jmd0OyZndDsmbmJzcDsmbmJz
cDtzdGFuZGFyZCB3aWRlbHkgdXNlZCBpbiBzaWduYWxsaW5nIG5ldHdvcmsuCjxicj4mZ3Q7Jmd0
OyZuYnNwOyZuYnNwO1RyYWRpdGlvbmFsIGFuZCBuZXcgVGVsZWNvbSBjYXJyaWVycyBpbXBsZW1l
bnQgc2lnbmFsbGluZyBvdmVyIElQIHRvPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7UmVkdWNlJm5i
c3A7Jm5ic3A7Y29zdCBmb3IgZXh0ZW5kZWQgY2FwYWNpdHk8YnI+Jmd0OyZndDsmbmJzcDsmbmJz
cDtSZW1vdmVzIHRoZSBsaW5rcy9saW5rc2V0IGxpbWl0YXRpb24gaW1wb3NlZCBieSB0cmFkaXRp
b25hbCBURE08YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtsaW5rc2V0cyBmb3IgdHJhZmZpYyBncm93
dGgKPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7QXZvaWQgbWFqb3IgbmV0d29yayByZS1lbmdpbmVl
cmluZyB3aGVuIHRyYWZmaWMgZ3Jvd3M8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtTQ1RQIGlzIHRo
ZSBiYXNpcyBvZiBzaWduYWxsaW5nIG92ZXIgSVA8YnI+Jmd0OyZndDs8YnI+Jmd0OyZndDsmbmJz
cDsmbmJzcDtTQ1RQIGlzIGFsc28gaW1wb3J0YW50IHRvIENoaW5hIE1vYmlsZTxicj4mZ3Q7Jmd0
OyZuYnNwOyZuYnNwO0FwcGx5aW5nIHRvIHRoZSBOYyBpbnRlcmZhY2UgdG8gdHJhbnNwb3J0IEJJ
Q0MgbWVzc2FnZXMKPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7QXBwbHlpbmcgdG8gdGhlIE1jIGlu
dGVyZmFjZSB0byB0cmFuc3BvcnQgSC4yNDggbWVzc2FnZXM8YnI+Jmd0OyZndDsmbmJzcDsmbmJz
cDtBcHBseWluZyB0byB0aGUgaW50ZXJmYWNlIGJldHdlZW4gTVNDIFNlcnZlciBhbmQgdGhlIGVt
YmVkZGVkIFNHIHRvPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7dHJhbnNwb3J0IGFjY2VzcyBuZXR3
b3JrIHNpZ25hbGxpbmc8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtBcHBseWluZyB0byBzaWduYWxs
aW5nIG5ldHdvcmsKPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7dGhlIGludGVyZmFjZSBiZXR3ZWVu
IElQU0VQczxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO3RoZSBpbnRlcmZhY2UgYmV0d2VlbiBJUFNU
UHM8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDt0aGUgaW50ZXJmYWNlIGJldHdlZW4gSVBTRVAgYW5k
IElQU1RQPGJyPiZndDsmZ3Q7PGJyPiZndDsmZ3Q7PGJyPiZndDsmZ3Q7IFByb2JsZW0gZGVzY3Jp
cHRpb248YnI+Jmd0OyZndDs8YnI+Jmd0OyZndDsgQ2hpbmEgTW9iaWxlIGhhcyBhIGxhcmdlIG51
bWJlciBvZiBzdWJzY3JpYmVycyBhbmQgaGFzIGJ1aWx0IHRoZQo8YnI+Jmd0OyZndDsmbmJzcDsm
bmJzcDtsYXJnZXN0IHNvZnQtc3dpdGNoIG5ldHdvcmsgaW4gdGhlIHdvcmxkLiBUaGUgc2lnbmFs
aW5nIHRyYWZmaWM8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtiZXR3ZWVuIHR3byBub2RlcyBpcyB2
ZXJ5IGxhcmdlLjxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO0NoaW5hIE1vYmlsZSBpbXBvcnRzIG11
bHRpLXZlbmRlciYjMzk7cyBwcm9kdWN0cy4gVGhlIGNvbXBhdGliaWxpdHk8YnI+Jmd0OyZndDsm
bmJzcDsmbmJzcDtiZXR3ZWVuIGRpZmZlcmVudCB2ZW5kZXImIzM5O3MgcHJvZHVjdHMgaXMgaW1w
b3J0YW50Lgo8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtUaGUgaWxsZWdpYmlsaXR5IG9mIE11bHRp
LWhvbWluZyBtZWNoYW5pc20gaW4gU0NUUCBwcm90b2NvbCBicmluZ3M8YnI+Jmd0OyZndDsmbmJz
cDsmbmJzcDtvbiBjb21wYXRpYmlsaXR5IHByb2JsZW1zPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7
U0NUUCBkaWQgbm90IGRlZmluZSB0aGUgbWVjaGFuaXNtIGhvdyB0aGUgU0FDSyBpcyBzZW5kIGJh
Y2sgdG88YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtlbmRwb2ludCBieSBvdGhlciBwYXRoIHdoZW4g
b25lIHBhdGggZmFpbHMuCjxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO1NDVFAgZGVmaW5lcyBtdWx0
aS1ob21pbmcsIGJ1dCBpdCBkaWQgbm90IGRlZmluZSBob3cgdGhlIHByaW1hcnk8YnI+Jmd0OyZn
dDsmbmJzcDsmbmJzcDtwYXRoIGNhbiBiZSB1bmlvbml6ZWQgYmV0d2VlbiB0d28gbm9kZXMuPGJy
PiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7UmVxdWlyZW1lbnQgZm9yIFN1cHBsZW1lbnQgb2YgUkZDNDQ2
MDxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO0RlZmluZSB0aGUgbWVjaGFuaXNtIHRoYXQgU0FDSyBp
cyBzZW5kIGJhY2sgdG8gZW5kcG9pbnQgYnkgdGhlCjxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO3Nl
Y29uZGFyeSBwYXRoIGlmIHRoZSBwcmltYXJ5IHBhdGggZmFpbHMgLjxicj4mZ3Q7Jmd0OyZuYnNw
OyZuYnNwO0RlZmluZSZuYnNwOyZuYnNwO3RoZSBtZWNoYW5pc20gaG93IHRoZSBwcmltYXJ5IHBh
dGggY2FuIGJlIHVuaW9uaXplZCBiZXR3ZWVuPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7dHdvIG5v
ZGVzLjxicj4mZ3Q7Jmd0Ozxicj4mZ3Q7Jmd0Ozxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO1Byb3Bv
c2FsIGZvciBTdXBwbGVtZW50IG9mIFJGQzQ0NjAKPGJyPiZndDsmZ3Q7PGJyPiZndDsmZ3Q7PGJy
PiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7MaOpQWRkIHRoZSBtZWNoYW5pc20gaG93IHRoZSBwcmltYXJ5
IHBhdGggY2FuIGJlIHVuaW9uaXplZCBiZXR3ZWVuPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7dHdv
IG5vZGVzIGluIFNlY3Rpb24gNSZuYnNwOyZuYnNwOyYjMzk7QXNzb2NpYXRpb24gSW5pdGlhbGl6
YXRpb24gJiMzOTsuPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7MqOpIEFkZCB0aGUgbWVjaGFuaXNt
IHRoYXQgU0FDSyBpcyBzZW5kIGJhY2sgdG8gZW5kcG9pbnQgYnkgdGhlCjxicj4mZ3Q7Jmd0OyZu
YnNwOyZuYnNwO3NlY29uZGFyeSBwYXRoIGlmIHRoZSBwcmltYXJ5IHBhdGggZmFpbHMgaW4gU2Vj
dGlvbiA2LjI8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDsmIzM5O0Fja25vd2xlZGdlbWVudCBvbiBS
ZWNlcHRpb24gb2YgREFUQSBDaHVua3MgJiMzOTsuPGJyPiZndDsmZ3Q7PGJyPiZndDsmZ3Q7IChU
aGF0JiMzOTtzIGFsbCBmb3IgU0NUUCk8YnI+Jmd0OyZndDs8YnI+Jmd0OyZndDs8YnI+Jmd0OyZn
dDsmbmJzcDsmbmJzcDs9PT09PT09PT09PT09PT09PT09PT09PT09PT09PQo8YnI+Jmd0OyZndDsm
bmJzcDsmbmJzcDtmb3IgTTNVQSBvZiBDaGluYSBNb2JpbGUucHB0PGJyPiZndDsmZ3Q7Jm5ic3A7
Jm5ic3A7PT09PT09PT09PT09PT09PT09PT09PT09PT09PT08YnI+Jmd0OyZndDs8YnI+Jmd0OyZn
dDsmbmJzcDsmbmJzcDtUaGUgUmVxdWlyZW1lbnQgYW5kIFByb3Bvc2FsPGJyPiZndDsmZ3Q7Jm5i
c3A7Jm5ic3A7IGZvciBNM1VBIFNwZWNpZmljYXRpb24gRXh0ZW5zaW9uPGJyPiZndDsmZ3Q7Jm5i
c3A7Jm5ic3A7IG9mIENoaW5hIE1vYmlsZTxicj4KCiZndDsmZ3Q7Cjxicj4mZ3Q7Jmd0OyZuYnNw
OyZuYnNwO0NoZW4gWHU8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtDaGluYSBNb2JpbGU8YnI+Jmd0
OyZndDs8YnI+Jmd0OyZndDs8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtDb250ZW50PGJyPiZndDsm
Z3Q7PGJyPiZndDsmZ3Q7IEJhY2tncm91bmQ8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtQcm9ibGVt
IERlc2NyaXB0aW9uPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7UmVxdWlyZW1lbnQgZm9yIEV4dGVu
c2lvbiBvZiBSRkM0NjY2PGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7UHJvcG9zYWwgZm9yIEV4dGVu
c2lvbiBvZiBSRkM0NjY2Cjxicj4mZ3Q7Jmd0Ozxicj4mZ3Q7Jmd0Ozxicj4mZ3Q7Jmd0Ozxicj4m
Z3Q7Jmd0OyZuYnNwOyZuYnNwO0JhY2tncm91bmQ8YnI+Jmd0OyZndDs8YnI+Jmd0OyZndDsmbmJz
cDsmbmJzcDtUaGUgYXBwbGljYXRpb24gb2YgU0lHVFJBTiBzdGFuZGFyZCBmb3IgU0cgaGFzIGV2
ZXIgc29sdmVkIHRoZTxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO3Byb2JsZW1zIG9mJm5ic3A7Jm5i
c3A7Tm8uNyBTaWduYWxsaW5nIFN5c3RlbSBJbnRlcndvcmtpbmcgSVAgYW5kPGJyPgoKCiZndDsm
Z3Q7Jm5ic3A7Jm5ic3A7dHJhbnNtaXNzaW9uIG9mJm5ic3A7Jm5ic3A7YWNjZXNzIG5ldHdvcmsg
c2lnbmFsbGluZyZuYnNwOyZuYnNwO2luJm5ic3A7Jm5ic3A7UjQgQ1MgY29yZSBuZXR3b3JrLjxi
cj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO1RoZSB3b3JsZCB0cmVuZCBvZiBJUCBiZWFyZXIgZm9yIHNp
Z25hbGxpbmcgd2lsbCBtYWtlIFNJR1RSQU48YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtzdGFuZGFy
ZCB3aWRlbHkgdXNlZCBpbiBzaWduYWxsaW5nIG5ldHdvcmsuPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5i
c3A7VHJhZGl0aW9uYWwgYW5kIG5ldyBUZWxlY29tIGNhcnJpZXJzIGltcGxlbWVudCBzaWduYWxs
aW5nIG92ZXIgSVAgdG8KPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7UmVkdWNlJm5ic3A7Jm5ic3A7
Y29zdCBmb3IgZXh0ZW5kZWQgY2FwYWNpdHk8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtSZW1vdmVz
IHRoZSBsaW5rcy9saW5rc2V0IGxpbWl0YXRpb24gaW1wb3NlZCBieSB0cmFkaXRpb25hbCBURE08
YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtsaW5rc2V0cyBmb3IgdHJhZmZpYyBncm93dGg8YnI+Jmd0
OyZndDsmbmJzcDsmbmJzcDtBdm9pZCBtYWpvciBuZXR3b3JrIHJlLWVuZ2luZWVyaW5nIGFzIHRy
YWZmaWMgZ3Jvd3MKPGJyPiZndDsmZ3Q7PGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7U0lHVFJBTiBp
cyBhbHNvIGltcG9ydGFudCB0byBDaGluYSBNb2JpbGU8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtB
cHBseWluZyB0byB0aGUgTmMgaW50ZXJmYWNlIG9mIEJJQ0MgbmV0d29yayB0byB0cmFuc3BvcnQg
QklDQzxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO21lc3NhZ2VzPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5i
c3A7QXBwbHlpbmcgdG8gdGhlIGludGVyZmFjZSBiZXR3ZWVuIE1TQyBTZXJ2ZXIgYW5kIGVtYmVk
ZWQgU0cgdG8KPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7dHJhbnNwb3J0IGFjY2VzcyBuZXR3b3Jr
IHNpZ25hbGxpbmc8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtBcHBseWluZyB0byBzaWduYWxsaW5n
IG5ldHdvcms8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDt0aGUgaW50ZXJmYWNlIGJldHdlZW4gSVBT
RVBzoaqhqk0zVUE8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDt0aGUgaW50ZXJmYWNlIGJldHdlZW4g
SVBTVFBzoaqhqk0yUEE8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDt0aGUgaW50ZXJmYWNlIGJldHdl
ZW4gSVBTRVAgYW5kIElQU1RQoaqhqk0zVUEKPGJyPiZndDsmZ3Q7PGJyPiZndDsmZ3Q7Jm5ic3A7
Jm5ic3A7UHJvYmxlbSBkZXNjcmlwdGlvbjxicj4mZ3Q7Jmd0Ozxicj4mZ3Q7Jmd0OyZuYnNwOyZu
YnNwO00zVUEgc3BlY2lmaWNhdGlvbiBkb2VzbiYjMzk7dCZuYnNwOyZuYnNwO2RlZmluZSBzaWdu
YWxpbmcgbmV0d29yayZuYnNwOyZuYnNwO21hbmFnZW1lbnQ8YnI+Jmd0OyZndDsmbmJzcDsmbmJz
cDtmdW5jdGlvbjxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO00zVUEgaXMgZGVzaWduZWQgZm9yIFNH
LUlQU0VQIGFuZCBJUFNFUC1JUFNFUCBhcHBsaWNhdGlvbnMsCjxicj4mZ3Q7Jmd0OyZuYnNwOyZu
YnNwO3RoZXJlZm9yZSBuZXR3b3JrIGxldmVsIG1hbmFnZW1lbnQgZnVuY3Rpb24gaXNuJiMzOTt0
IHJlcXVpcmVkLjxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO1NTTk0gbWVzc2FnZXMgZGVmaW5lZCBp
biBNM1VBIGFyZSBvbmx5IHVzZWQgZm9yIGludGVyd29ya2luZyB3aXRoPGJyPiZndDsmZ3Q7IFNT
Ny48YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtDaGluYSBNb2JpbGUgaGFzIGEgbGFyZ2UgbnVtYmVy
IG9mIHN1YnNjcmliZXJzIGFuZCBoYXMgYnVpbHQgdGhlCjxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNw
O2xhcmdlc3Qgc29mdC1zd2l0Y2ggbmV0d29yayBpbiB0aGUgd29ybGQsIGl0cyBzaWduYWxpbmcg
bmV0d29yazxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO3dpbGwgYmUgdGhlIG11bHRpLWxldmVsIGFu
ZCBtdWx0aS1hcmVhIG1vZGUuPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7SXQgd2lsbCBoYXMgdHdv
IHNpZ25hbGxpbmcgcm91dGVpbmcmbmJzcDsmbmJzcDtzY2VuZTpJUFNFUC1JUFNUUC1JUFNUUC1J
UFNFUDxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO2FuZCBJUFNFUC1JUFNUUC1JUFNFUAo8YnI+Jmd0
OyZndDsmbmJzcDsmbmJzcDtUaGUgaW50ZXJ3b3JraW5nJm5ic3A7Jm5ic3A7ZnVuY3Rpb24gd2l0
aCBNVFAzIGluIE0zVUEgY2FuIHJlYWxpemUgdGhlPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7c2ln
bmFsaW5nIG5ldHdvcmsmbmJzcDsmbmJzcDttYW5hZ2VtZW50IGZvciZuYnNwOyZuYnNwO0lQU0VQ
LUlQU1RQLUlQU1RQLUlQU0VQIHNjZW5lOzxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO0N1cnJlbnQg
TTNVQSZuYnNwOyZuYnNwO2NhbiBub3QmbmJzcDsmbmJzcDtyZWFsaXplIHRoZSBzaWduYWxpbmcg
bmV0d29yayZuYnNwOyZuYnNwO21hbmFnZW1lbnQKPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Zm9y
Jm5ic3A7Jm5ic3A7SVBTRVAtSVBTVFAtSVBTRVAgc2NlbmUuPGJyPiZndDsmZ3Q7PGJyPiZndDsm
Z3Q7Jm5ic3A7Jm5ic3A7UmVxdWlyZW1lbnQgZm9yIEV4dGVuc2lvbiBvZiBSRkM0NjY2PGJyPiZn
dDsmZ3Q7PGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7RGVmaW5lIHRoZSBBcHBsaWNhdGlvbiBmb3Ig
SVBTVFAtSVBTRVAgaW50ZXJmYWNlLihTdGlsbCB1c2VzIFNHUC08YnI+Jmd0OyZndDsmbmJzcDsm
bmJzcDtBU1AgcHJvY2VkdXJlcykKPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7RGVmaW5lIHRoZSBz
aWduYWxsaW5nIG5ldHdvcmsgbWFuYWdlbWVudCBmdW5jdGlvbqOsbWVzc2FnZXMgLGFuZDxicj4m
Z3Q7Jmd0OyZuYnNwOyZuYnNwO3Byb2NlZHVyZXMuKERlc2NyaWJlIGhvdyB0byB1c2UgU1NOTSBt
ZXNzYWdlcyB0byBzdXBwb3J0IHNpZ25hbGluZzxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO25ldHdv
cmsgbWFuYWdlbWVudCBmb3IgSVBTRVAtKE0zVUEpLUlQU1RQLShNM1VBKS1JUFNFUCBzY2VuZS4g
KQo8YnI+Jmd0OyZndDs8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtQcm9wb3NhbCBmb3IgRXh0ZW5z
aW9uIG9mIFJGQzQ2NjY8YnI+Jmd0OyZndDs8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDsxo6lBZGQg
ZGlmZmVyZW50IGtpbmRzIG9mIHJvdXRpbmcgc2NlbmVzIGFwcGxpY2F0aW9ucyBmb3IgSVBTRVAt
PGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7SVBTVFAgaW50ZXJmYWNlIGluIFNlY3Rpb24gMS41Jm5i
c3A7Jm5ic3A7JiMzOTtTYW1wbGUgQ29uZmlndXJhdGlvbiAmIzM5Oy4KPGJyPgomZ3Q7Jmd0OyZu
YnNwOyZuYnNwOzKjqUFkZCB0aGUgTTNVQSBzaWduYWxsaW5nIG5ldHdvcmsgbWFuYWdlbWVudCBm
dW5jdGlvbiBpbiBTZWN0aW9uPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7MS40Jm5ic3A7Jm5ic3A7
JiMzOTtGdW5jdGlvbmFsIEFyZWFzJiMzOTsuPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7M6OpIEFk
ZCB0aGUgQ2xpZW50L1NlcnZlciBNb2RlbCBmb3IgSVBTVFAtSVBTRVAgaW50ZXJmYWNlIGluPGJy
PiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7U2VjdGlvbiAxLjQuOAoKLiZuYnNwOyZuYnNwOyYjMzk7U0NU
UCBDbGllbnQvU2VydmVyIE1vZGVsJiMzOTsuCjxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwOzSjqUV4
dGVuZCB0aGUgRFVQVSBtZXNzYWdlIGNvZGUgaW4gQ2hhcHRlciAzICYjMzk7TTNVQSBQcm90b2Nv
bDxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO0VsZW1lbnRzJiMzOTsuPGJyPiZndDsmZ3Q7Jm5ic3A7
Jm5ic3A7NaOpQWRkIHRoZSBzaWduYWxsaW5nIG5ldHdvcmsgbWFuYWdlbWVudCBwcm9jZWR1cmUg
aW4gQ2hhcHRlcjxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwOzQmIzM5O3Byb2NlZHVyZSYjMzk7Ljxi
cj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwOzYpIEFkZCB0aGUgcmVxdWlyZW1lbnQgb2YgTXVsdGkgdXNl
ciBkYXRhIHN0cmVhbXMgZm9yIE0zVUEgb3Zlcgo8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtTQ1RQ
IEFwcGxpY2F0aW9uIGluIFNlY3Rpb24gMS40LjcgJiMzOTsgU0NUUCBTdHJlYW0gTWFwcGluZyYj
Mzk7Ljxicj4mZ3Q7Jmd0Ozxicj4mZ3Q7Jmd0OyAoVGhhdCYjMzk7cyBhbGwgZm9yIE0zVUEpPGJy
PiZndDsmZ3Q7PGJyPiZndDsmZ3Q7PGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT08YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtmb3IgTTJQQSBvZiBDaGlu
YSAKTW9iaWxlLnBwdAo8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDs9PT09PT09PT09PT09PT09PT09
PT09PT09PT09PTxicj4mZ3Q7Jmd0Ozxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO1RoZSBSZXF1aXJl
bWVudCBhbmQgUHJvcG9zYWw8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDsgZm9yIE0yUEEgU3BlY2lm
aWNhdGlvbiBSZXZpc2lvbjxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwOyBvZiBDaGluYSBNb2JpbGU8
YnI+Jmd0OyZndDs8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtDaGVuIFh1PGJyPiZndDsmZ3Q7Jm5i
c3A7Jm5ic3A7Q2hpbmEgTW9iaWxlCjxicj4mZ3Q7Jmd0Ozxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNw
O0NvbnRlbnQ8YnI+Jmd0OyZndDs8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtCYWNrZ3JvdW5kPGJy
PiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7UHJvYmxlbSBEZXNjcmlwdGlvbjxicj4mZ3Q7Jmd0OyZuYnNw
OyZuYnNwO1JlcXVpcmVtZW50IGZvciBSZXZpc2lvbiBvZiBSRkM0MTY1PGJyPiZndDsmZ3Q7Jm5i
c3A7Jm5ic3A7UHJvcG9zYWwgZm9yIFJldmlzaW9uIG9mIFJGQzQxNjU8YnI+Jmd0OyZndDs8YnI+
Jmd0OyZndDsKPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7QmFja2dyb3VuZDxicj4mZ3Q7Jmd0Ozxi
cj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO00yUEEgcHJvdG9jb2wgaXMgYSBwZWVyIHRvIHBlZXIgcHJv
dG9jb2wsIGl0IG5vdCBvbmx5IHN1cHBvcnRzPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7c2VhbWxl
c3MgbWFuYWdlbWVudCBvcGVyYXRpb24gb2YgTVRQMyBwcm90b2NvbCBwZWVycyBvdmVyIGFuIElQ
PGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7bmV0d29yayBjb25uZWN0aW9uLCBidXQgYWxzbyByZW1v
dmVzIHRoZSBsaW5rcy9saW5rc2V0IGxpbWl0YXRpb24KPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7
aW1wb3NlZCBieSB0cmFkaXRpb25hbCBURE0gbGlua3NldHMgZm9yIHRyYWZmaWMgZ3Jvd3RoLjxi
cj4mZ3Q7Jmd0Ozxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO1RoZSBTdGFuZGFyZGl6YXRpb24gb2Yg
TTJQQSBpcyBiZWhpbmQgdGhlIGFwcGxpY2F0aW9uIG9mIGl0Ljxicj4mZ3Q7Jmd0OyZuYnNwOyZu
YnNwO0FsdGhvdWdoIHRoZSBSRkMgZWRpdGlvbiBpcyByZWxlYXNlZCBpbiAyMDA1LCBNMlBBIGlz
IHdpZGVseSB1c2VkCjxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO2luIHRoZSZuYnNwOyZuYnNwO1Np
Z25hbGluZyBuZXR3b3JrIHJlYnVpbGRpbmcgb3ZlciBJUCBmb3IgdHJhZGl0aW9uYWw8YnI+Jmd0
OyZndDsmbmJzcDsmbmJzcDtvcGVyYXRvcnMgYW5kIGluIHRoZSBTaWduYWxpbmcgbmV0d29yayBj
b25zdHJ1Y3Rpb24gZm9yJm5ic3A7Jm5ic3A7bmV3PGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7b3Bl
cmF0b3JzJm5ic3A7Jm5ic3A7c2luY2UgMjAwMi48YnI+Jmd0OyZndDs8YnI+Jmd0OyZndDsmbmJz
cDsmbmJzcDtWYXJpb3VzIGRyYWZ0IGVkaXRpb25zIGFuZCB0aGUgbWFqb3IgZGlmZmVyZW5jZXMg
YmV0d2VlbiB0aGVtIG1ha2UKPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7cHJvYmxlbXMgd2hlbiBv
bmUmbmJzcDsmbmJzcDtJUFNUUCBwcm92aWRlciBpbnRlcndvcmtpbmcgd2l0aCBhbm90aGVyLjxi
cj4mZ3Q7Jmd0Ozxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO1Byb2JsZW0gRGVzY3JpcHRpb248YnI+
Jmd0OyZndDs8YnI+Jmd0OyZndDs8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtSRkM0MTY1IG5lZWRz
IHRvIGJlIHN1cHBsZW1lbnRlZCBhbmQgcmV2aXNlZCCjujxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNw
O1NvbWUmbmJzcDsmbmJzcDtwcm9jZWR1cmVzJm5ic3A7Jm5ic3A7YXJlJm5ic3A7Jm5ic3A7ZGVz
Y3JpYmVkIGEgbGl0dGxlIGJpdCBzaW1wbHkgYW5kIHJlZmVycmVkCjxicj4mZ3Q7Jmd0OyZuYnNw
OyZuYnNwO3RvIE1UUDIgZGlyZWN0bHkgLCZuYnNwOyZuYnNwO3doaWNoJm5ic3A7Jm5ic3A7bWFr
ZXMgSVBTVFAmbmJzcDsmbmJzcDtwcm92aWRlcnMgcmVhbGl6aW5nIHRoZTxicj4mZ3Q7Jmd0OyZu
YnNwOyZuYnNwO3Byb2NlZHVyZXMgaW4gZGlmZmVyZW50IHdheXMgLGZvciZuYnNwOyZuYnNwO3Ro
ZXJlJiMzOTtzIGRpZmZlcmVuY2UgYmV0d2VlbiBNVFAyPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7
YW5kIE0yUEEgaW4gc29tZSBhc3BlY3RzLiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOy48YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtTb21lIElQU1RQIHByb3ZpZGVycyB1c2UgdGhl
IHNhbWUgaWRlYSBhcyBNVFAyCjxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO090aGVycyB0YWtlIHRo
ZSByZWxhdGlvbiBiZXR3ZWVuIE0yUEEgYW5kIFNDVFAgaW50byBhY2NvdW50Ljxicj4mZ3Q7Jmd0
Ozxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO1Q3IGlzbiYjMzk7dCBkZWZpbmVkIGFuZCBnaXZlbiB0
aGUgcmFuZ2UsIHdoaWNoIG1ha2VzIElQU1RQIHByb3ZpZGVyczxicj4mZ3Q7Jmd0OyZuYnNwOyZu
YnNwO3JlYWxpemluZyBpdCBpbiBkaWZmZXJlbnQgd2F5cy48YnI+Jmd0OyZndDsKPGJyPiZndDsm
Z3Q7Jm5ic3A7Jm5ic3A7SG93IHRvIGZpbGwgaW4gYW5kIHByb2Nlc3MgRlNOIGFuZCBCU04gaW4g
TTJQQSBIZWFkZXIgaXNuJiMzOTt0PGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7ZGVmaW5lZCBjbGVh
cmx5Ljxicj4mZ3Q7Jmd0Ozxicj4mZ3Q7Jmd0Ozxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO1JlcXVp
cmVtZW50IGZvciBSZXZpc2lvbiBvZiBSRkM0MTY1PGJyPiZndDsmZ3Q7PGJyPiZndDsmZ3Q7Jm5i
c3A7Jm5ic3A7U3VwcGxlbWVudCB0aGUgZGVzY3JpcHRpb24gb2YgdGhlIHdob2xlIGlkZWEgZm9y
IExpbmsgQWxpZ25tZW50Cjxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO3Byb2NlZHVyZSBhbmQgUHJv
Y2Vzc29yIE91dGFnZSBwcm9jZWR1cmUuPGJyPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7U3VwcGxlbWVu
dCB0aGUgZGVmaW5pdGlvbiBhbmQgcmFuZ2Ugb2YgTTJQQSBUaW1lcnMuPGJyPiZndDsmZ3Q7Jm5i
c3A7Jm5ic3A7U3VwcGxlbWVudCB0aGUgcnVsZXMgb2YgdXNhZ2Ugb2YgRlNOIGFuZCBCU04gaW4g
TTJQQSBIZWFkZXIuPGJyPiZndDsmZ3Q7PGJyPiZndDsmZ3Q7PGJyPgoKCiZndDsmZ3Q7Jm5ic3A7
Jm5ic3A7UHJvcG9zYWwgZm9yIFJldmlzaW9uIG9mIFJGQzQxNjU8YnI+Jmd0OyZndDs8YnI+Jmd0
OyZndDsmbmJzcDsmbmJzcDsxo6lTdXBwbGVtZW50IHRoZSB3aG9sZSBpZGVhICwgdGhlIHBoYXNl
IGRpdmlzaW9uICwgdGhlIGNvcnJlbGF0ZWQ8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDttZXNzYWdl
cyBhbmQgVGltZXJzIG9mIExpbmsgQWxpZ25tZW50IHByb2NlZHVyZSBpbiBTZWN0aW9uIDQuMS4z
Ljxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwOzKjqVN1cHBsZW1lbnQgdGhlIHdob2xlIGlkZWEgb2Yg
UHJvY2Vzc29yIE91dGFnZSBwcm9jZWR1cmUsIGFuZAo8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDtk
ZXNjcmliZSB0aGUgcnVsZXMgb2YgTFBPIGFuZCBSUE8gcHJvY2Vzc2luZyBzZXBhcmF0ZWx5IC48
YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDszo6lTdXBwbGVtZW50IHRoZSBydWxlcyBvZiB1c2FnZSBv
ZiBGU04gYW5kIEJTTiBpbiBNMlBBIEhlYWRlciBpbjxicj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwO1Nl
Y3Rpb24gNC4yLjE8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDs0o6lTdXBwbGVtZW50IHRoZSBkZWZp
bml0aW9uIGFuZCByYW5nZSBvZiBNMlBBIFRpbWVycyBpbiBBcHBlbmRpeC4KPGJyPiZndDsmZ3Q7
PGJyPiZndDsmZ3Q7IChUaGF0JiMzOTtzIGFsbCBmb3IgTTJQQSk8YnI+Jmd0OyZndDs8YnI+Jmd0
OyZndDsgQ2hlbiBYdTxicj4mZ3Q7Jmd0OyBDaGluYSBNb2JpbGU8YnI+Jmd0OyZndDsgPGEgaHJl
Zj0ibWFpbHRvOmNoZW54dUBjaGluYW1vYmlsZS5jb20iIHRhcmdldD0iX2JsYW5rIiBvbmNsaWNr
PSJyZXR1cm4gdG9wLmpzLk9wZW5FeHRMaW5rKHdpbmRvdyxldmVudCx0aGlzKSI+CgpjaGVueHVA
Y2hpbmFtb2JpbGUuY29tPC9hPjxicj4mZ3Q7Jmd0OyBfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXwo8YnI+Jmd0OyZndDsgU2lndHJhbiBtYWlsaW5nIGxpc3Q8
YnI+Jmd0OyZndDsgPGEgaHJlZj0ibWFpbHRvOlNpZ3RyYW5AaWV0Zi5vcmciIHRhcmdldD0iX2Js
YW5rIiBvbmNsaWNrPSJyZXR1cm4gdG9wLmpzLk9wZW5FeHRMaW5rKHdpbmRvdyxldmVudCx0aGlz
KSI+U2lndHJhbkBpZXRmLm9yZzwvYT48YnI+Jmd0OyZndDsgPGEgaHJlZj0iaHR0cHM6Ly93d3cx
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc2lndHJhbiIgdGFyZ2V0PSJfYmxhbmsiIG9uY2xp
Y2s9InJldHVybiB0b3AuanMuT3BlbkV4dExpbmsod2luZG93LGV2ZW50LHRoaXMpIj4KCmh0dHBz
Oi8vd3d3MS5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NpZ3RyYW48L2E+PGJyPgo8YnI+PGJy
Pjxicj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj5T
aWd0cmFuIG1haWxpbmcgbGlzdDxicj48YSBocmVmPSJtYWlsdG86U2lndHJhbkBpZXRmLm9yZyIg
dGFyZ2V0PSJfYmxhbmsiIG9uY2xpY2s9InJldHVybiB0b3AuanMuT3BlbkV4dExpbmsod2luZG93
LGV2ZW50LHRoaXMpIj5TaWd0cmFuQGlldGYub3JnPC9hPjxicj48YSBocmVmPSJodHRwczovL3d3
dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zaWd0cmFuIiB0YXJnZXQ9Il9ibGFuayIgb25j
bGljaz0icmV0dXJuIHRvcC5qcy5PcGVuRXh0TGluayh3aW5kb3csZXZlbnQsdGhpcykiPgoKaHR0
cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc2lndHJhbgo8L2E+PGJyPjxicj48
L2Jsb2NrcXVvdGU+PC9zcGFuPjwvZGl2PjwvZGl2Pjxicj4K
------=_Part_5021_16154724.1185540694520--





From tsvwg-bounces@ietf.org Fri Jul 27 08:51:35 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEPI2-00063K-In; Fri, 27 Jul 2007 08:51:30 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IELRy-0005Us-2D
	for tsvwg-confirm+ok@megatron.ietf.org; Fri, 27 Jul 2007 04:45:30 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IELRx-0005UO-N1; Fri, 27 Jul 2007 04:45:29 -0400
Received: from [221.130.253.133] (helo=cmccmta)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IELRu-0005q7-4O; Fri, 27 Jul 2007 04:45:27 -0400
Received: from 6f-chenxu ([10.1.5.152])
	by mail.chinamobile.com (Lotus Domino Release 6.5.5FP1)
	with SMTP id 2007072716452278-50842 ;
	Fri, 27 Jul 2007 16:45:22 +0800 
Date: Fri, 27 Jul 2007 16:45:12 +0800
From: "=?gb2312?B?s8LQ8Q==?=" <chenxu@chinamobile.com>
To: "Michael Tuexen" <Michael.Tuexen@lurchi.franken.de>
X-mailer: Foxmail 5.0 [cn]
Mime-Version: 1.0
X-MIMETrack: Itemize by SMTP Server on jtgsml01/servers/cmcc(Release 6.5.5FP1
	| April 14, 2006) at 2007-07-27 16:45:22,
	Serialize by Router on cmccmta/servers/cmcc(Release 6.5.5FP1 | April 14,
	2006) at 2007-07-27 16:45:26,
	Serialize complete at 2007-07-27 16:45:26
Message-ID: <OF24565732.6AADA0AB-ON48257325.00301996@chinamobile.com>
Content-Transfer-Encoding: base64
Content-Type: text/plain;
	charset="gb2312"
X-Spam-Score: 2.9 (++)
X-Scan-Signature: 88b11fc64c1bfdb4425294ef5374ca07
X-Mailman-Approved-At: Fri, 27 Jul 2007 08:51:29 -0400
Cc: zhanghao <zhanghao@chinamobile.com>, SIGTRAN <sigtran@ietf.org>,
	TSWG <tsvwg@ietf.org>
Subject: [Tsvwg] Re: Re: [Sigtran] The requiremnts and
	proposalsforM2PA/M3UA/SCTPExtension from China Mobile
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

RGVhciBNaWNoYWVsIFR1ZXhlbiwNCg0KCQ0KPiAgICAxLiBXaGF0IGRvZXMgInVuaW9uaXplIG9m
IHRoZSBwcmltYXJ5IHBhdGhzIGJldHdlZW4gbm9kZXMiIG1lYW4/DQogICBJdCBtZWFuc6OsZm9y
IG9uZSBtdWx0aS1ob21lZCBTQ1RQIGVuZHBvaW50LHRoZSBwcmltYXJ5IHBhdGijqHNvdXJjZSBJ
UCBhZGRyZXNzPUlQMS0tLWRlc3RpbmF0aW9uIElQPUlQMqOpIHNoYWxsIGJlIHRoZSBzYW1lIGFz
IHRoZSByZW1vdGUgZW5kcG9pbnQncyAoIHNvdXJjZSBJUCBhZGRyZXNzPUlQMi0tLWRlc3RpbmF0
aW9uIElQPUlQMSAgKSAgIA0KICAgDQogICBNYW55IHZlbmRlcnMgaW1wbGVtZW50IE11bHRpLWhv
bWluZyBpbiB0aGUgZm9sbG93aW5nIHdheToNCg0KICAgIG9uZSBtdWx0aS1ob21lZCBTQ1RQIGVu
ZHBvaW50IGhhcyB0d28gbG9jYWwgSVAgYWRkcmVzc2VzKElQMS9JUDIpIGFuZCB0d28gcmVtb3Rl
IElQIGFkZHJlc3MoSVAzL0lQNCkgd2l0aGluIGFuIGFzc29jaWF0aW9uLg0KICAgIFRoZXJlJ3Mg
dHdvIHBhdGhzIHdpdGhpbiBhbiBhc3NvY2lhdGlvbjpJUDEtSVAzLGFuZCBJUDItSVA0Lm5vdCA0
IHBhdGhzLiANCiAgIA0KICAgIEZvciBleGFtcGxlLCBlbmRwb2ludDEgaGFzIHR3byBsb2NhbCBJ
UCBhZGRyZXNzZXMoSVAxL0lQMimjrCBhbmQgZW5kcG9pbnQyIGhhcyB0d28gbG9jYWwgSVAgYWRk
cmVzc2VzKElQMy9JUDQpLg0KDQppZiB0d28gZW5kcG9pbnRzJyBwcmltYXJ5IHBhdGggaXNuJ3Qg
dGhlIHNhbWUsdGhhdCBpcyBlbmRwb2ludDEgdXNlIElQMS1JUDMgYXMgdGhlIHByaW1hcnkgcGF0
aCwgdXNlIElQMi1JUDQgYXMgdGhlIHNlY29uZCBwYXRoOyAgZW5kcG9pbnQyIHVzZSBJUDMtSVAy
IGFzIHRoZSBwcmltYXJ5IHBhdGgsIHVzZSBJUDQtSVAxIGFzIHRoZSBzZWNvbmQgcGF0aC4gDQoN
CiAgICBUaGVzZSB0d28gZW5kcG9pbnRzIGNhbid0ICBzZW5kIGRhdGEgdG8gZWFjaCBvdGhlciBz
dWNjZXNzZnVsbHkuICANCiAgICAgICAgDQoNCj4gICAgIDIuIE5vdCBzdXJlIGFib3V0IHRoZSBT
QUNLIGlzc3VlOiBZb3UgYXJlIGN1cnJlbnRseSBhbGxvd2VkIHRvDQo+ICAgIHNlbmQgdGhlIFNB
Q0sgYmFjayB0byBhbiBhZGRyZXNzZXMgZGlmZmVyZW50IGZyb20gdGhlIHNvdXJjZQ0KPiAgICBh
ZGRyZXNzIG9mIHRoZSBjb3JyZXNwb25kaW5nIERBVEEgY2h1bmsuIEFzIGZhciBhcyBJIGtub3cN
Cj4gICAgaXQgaXMgb25seSBhIFNIT1VMRCBkZXNjcmliaW5nIHRoYXQgeW91IHNlbmQgdGhlIFNB
Q0sgYmFjaw0KPiAgICB0byB0aGUgc291cmNlIGFkZHJlc3Mgb2YgdGhlIERBVEEgY2h1bmsuDQoN
CiAgICAgWW91IGFyZSByaWdodCxpdCBpcyBvbmx5IGEgU0hPVUxEIGRlc2NyaWJpbmcgdGhhdCB5
b3Ugc2VuZCB0aGUgU0FDSyBiYWNrDQogICB0byB0aGUgc291cmNlIGFkZHJlc3Mgb2YgdGhlIERB
VEEgY2h1bmsgaW4gUkZDMjk2MC4NCiAgICAgIFRoYXQncyB3aHkgd2UgZ2V0IGluIHRyb3VibGUg
aW4gbXVsdGktaG9taW5nIHNpdHVhdGlvbi4gDQogICAgICBJZiB0aGUgIHBhdGggdG8gdGhlIHNv
dXJjZSBhZGRyZXNzIG9mIHRoZSBEQVRBIGNodW5rIGlzIHVucmVhY2hhYmxlo6x0aGUgc2FjayBj
YW4ndCBzZW5kIHRvIHRoZSByZW1vdGUgZW5kcG9pbnQgZm9yIGV2ZXIgYWx0aG91Z2ggdGhlIG90
aGVyIHBhdGggaXMgYXZhaWxhYmxlLlNvb24gdGhlIG90aGVyIHBhdGggd2lsbCBiZSBmYWlsdXJl
Lg0KDQpCZXN0IFJlZ2FyZA0KQ2hlbiBYdQ0KQ2hpbmEgTW9iaWxlDQpjaGVueHVAY2hpbmFtb2Jp
bGUuY29tDQoNCg0KDQoNCg0KDQoNCj09PT09PT0gMjAwNy0wNy0yNiAyMjoyMzoyMCDE+tTawLTQ
xdbQ0LS1wKO6PT09PT09PQ0KDQo+RGVhciBhbGwsDQo+DQo+SSdtIHNlbmRpbmcgdGhpcyBhbHNv
IHRvIFRTVldHLCBzaW5jZSB0aGUgU0NUUCBkaXNjdXNzaW9uIGhhcyB0byBiZQ0KPmRvbmUgdGhl
IHRoYXQgV0cuDQo+DQo+QWRkcmVzc2luZyB0aGUgU0NUUCBzdGF0ZW1lbnQ6DQo+DQo+MS4gV2hh
dCBkb2VzICJ1bmlvbml6ZSBvZiB0aGUgcHJpbWFyeSBwYXRocyBiZXR3ZWVuIG5vZGVzIiBtZWFu
Pw0KPjIuIE5vdCBzdXJlIGFib3V0IHRoZSBTQUNLIGlzc3VlOiBZb3UgYXJlIGN1cnJlbnRseSBh
bGxvd2VkIHRvDQo+ICAgIHNlbmQgdGhlIFNBQ0sgYmFjayB0byBhbiBhZGRyZXNzZXMgZGlmZmVy
ZW50IGZyb20gdGhlIHNvdXJjZQ0KPiAgICBhZGRyZXNzIG9mIHRoZSBjb3JyZXNwb25kaW5nIERB
VEEgY2h1bmsuIEFzIGZhciBhcyBJIGtub3cNCj4gICAgaXQgaXMgb25seSBhIFNIT1VMRCBkZXNj
cmliaW5nIHRoYXQgeW91IHNlbmQgdGhlIFNBQ0sgYmFjaw0KPiAgICB0byB0aGUgc291cmNlIGFk
ZHJlc3Mgb2YgdGhlIERBVEEgY2h1bmsuDQo+DQo+QmVzdCByZWdhcmRzDQo+TWljaGFlbA0KPg0K
Pk9uIEp1bCAyNiwgMjAwNywgYXQgNDoyMiBBTSwgY2hlbnh1IHdyb3RlOg0KPg0KPj4gRGVhciBh
bGwsDQo+Pg0KPj4gICAgICBTb3JyeSB0byBzdWJtaXQgdGhlIHJhciBmaWxlISBBbmQgdGhhbmtz
IFJ1aSBHb21lcyENCj4+DQo+PiBUaGUgY29udGVudHMgb2YgdGhlIGF0dGFjaG1lbnRzIGFyZSBh
cyBmb2xsb3dzOg0KPj4NCj4+ICAgPT09PT09PT09PT09PT09PT09PT09PT09PT09PT0NCj4+ICAg
Zm9yIFNDVFAgb2YgQ2hpbmEgTW9iaWxlLnBwdA0KPj4gID09PT09PT09PT09PT09PT09PT09PT09
PT09PT09DQo+Pg0KPj4gIFRoZSBSZXF1aXJlbWVudCBhbmQgUHJvcG9zYWwNCj4+ICAgZm9yIFND
VFAgU3BlY2lmaWNhdGlvbiBFeHRlbnNpb24NCj4+ICAgb2YgQ2hpbmEgTW9iaWxlDQo+Pg0KPj4g
IENoZW4gWHUgLCBaaGFuZyBIYW8NCj4+ICBDaGluYSBNb2JpbGUNCj4+DQo+PiAgQ29udGVudA0K
Pj4NCj4+ICBCYWNrZ3JvdW5kDQo+PiAgUHJvYmxlbSBkZXNjcmlwdGlvbg0KPj4gIFJlcXVpcmVt
ZW50IGZvciBTdXBwbGVtZW50IG9mIFJGQzQ0NjANCj4+ICBQcm9wb3NhbCBmb3IgU3VwcGxlbWVu
dCBvZiBSRkM0NDYwDQo+Pg0KPj4gIEJhY2tncm91bmQNCj4+DQo+PiAgVGhlIHdvcmxkIHRyZW5k
IG9mIElQIGJlYXJlciBmb3Igc2lnbmFsbGluZyB3aWxsIG1ha2UgU0lHVFJBTg0KPj4gIHN0YW5k
YXJkIHdpZGVseSB1c2VkIGluIHNpZ25hbGxpbmcgbmV0d29yay4NCj4+ICBUcmFkaXRpb25hbCBh
bmQgbmV3IFRlbGVjb20gY2FycmllcnMgaW1wbGVtZW50IHNpZ25hbGxpbmcgb3ZlciBJUCB0bw0K
Pj4gIFJlZHVjZSAgY29zdCBmb3IgZXh0ZW5kZWQgY2FwYWNpdHkNCj4+ICBSZW1vdmVzIHRoZSBs
aW5rcy9saW5rc2V0IGxpbWl0YXRpb24gaW1wb3NlZCBieSB0cmFkaXRpb25hbCBURE0NCj4+ICBs
aW5rc2V0cyBmb3IgdHJhZmZpYyBncm93dGgNCj4+ICBBdm9pZCBtYWpvciBuZXR3b3JrIHJlLWVu
Z2luZWVyaW5nIHdoZW4gdHJhZmZpYyBncm93cw0KPj4gIFNDVFAgaXMgdGhlIGJhc2lzIG9mIHNp
Z25hbGxpbmcgb3ZlciBJUA0KPj4NCj4+ICBTQ1RQIGlzIGFsc28gaW1wb3J0YW50IHRvIENoaW5h
IE1vYmlsZQ0KPj4gIEFwcGx5aW5nIHRvIHRoZSBOYyBpbnRlcmZhY2UgdG8gdHJhbnNwb3J0IEJJ
Q0MgbWVzc2FnZXMNCj4+ICBBcHBseWluZyB0byB0aGUgTWMgaW50ZXJmYWNlIHRvIHRyYW5zcG9y
dCBILjI0OCBtZXNzYWdlcw0KPj4gIEFwcGx5aW5nIHRvIHRoZSBpbnRlcmZhY2UgYmV0d2VlbiBN
U0MgU2VydmVyIGFuZCB0aGUgZW1iZWRkZWQgU0cgdG8NCj4+ICB0cmFuc3BvcnQgYWNjZXNzIG5l
dHdvcmsgc2lnbmFsbGluZw0KPj4gIEFwcGx5aW5nIHRvIHNpZ25hbGxpbmcgbmV0d29yaw0KPj4g
IHRoZSBpbnRlcmZhY2UgYmV0d2VlbiBJUFNFUHMNCj4+ICB0aGUgaW50ZXJmYWNlIGJldHdlZW4g
SVBTVFBzDQo+PiAgdGhlIGludGVyZmFjZSBiZXR3ZWVuIElQU0VQIGFuZCBJUFNUUA0KPj4NCj4+
DQo+PiBQcm9ibGVtIGRlc2NyaXB0aW9uDQo+Pg0KPj4gQ2hpbmEgTW9iaWxlIGhhcyBhIGxhcmdl
IG51bWJlciBvZiBzdWJzY3JpYmVycyBhbmQgaGFzIGJ1aWx0IHRoZQ0KPj4gIGxhcmdlc3Qgc29m
dC1zd2l0Y2ggbmV0d29yayBpbiB0aGUgd29ybGQuIFRoZSBzaWduYWxpbmcgdHJhZmZpYw0KPj4g
IGJldHdlZW4gdHdvIG5vZGVzIGlzIHZlcnkgbGFyZ2UuDQo+PiAgQ2hpbmEgTW9iaWxlIGltcG9y
dHMgbXVsdGktdmVuZGVyoa9zIHByb2R1Y3RzLiBUaGUgY29tcGF0aWJpbGl0eQ0KPj4gIGJldHdl
ZW4gZGlmZmVyZW50IHZlbmRlcqGvcyBwcm9kdWN0cyBpcyBpbXBvcnRhbnQuDQo+PiAgVGhlIGls
bGVnaWJpbGl0eSBvZiBNdWx0aS1ob21pbmcgbWVjaGFuaXNtIGluIFNDVFAgcHJvdG9jb2wgYnJp
bmdzDQo+PiAgb24gY29tcGF0aWJpbGl0eSBwcm9ibGVtcw0KPj4gIFNDVFAgZGlkIG5vdCBkZWZp
bmUgdGhlIG1lY2hhbmlzbSBob3cgdGhlIFNBQ0sgaXMgc2VuZCBiYWNrIHRvDQo+PiAgZW5kcG9p
bnQgYnkgb3RoZXIgcGF0aCB3aGVuIG9uZSBwYXRoIGZhaWxzLg0KPj4gIFNDVFAgZGVmaW5lcyBt
dWx0aS1ob21pbmcsIGJ1dCBpdCBkaWQgbm90IGRlZmluZSBob3cgdGhlIHByaW1hcnkNCj4+ICBw
YXRoIGNhbiBiZSB1bmlvbml6ZWQgYmV0d2VlbiB0d28gbm9kZXMuDQo+PiAgUmVxdWlyZW1lbnQg
Zm9yIFN1cHBsZW1lbnQgb2YgUkZDNDQ2MA0KPj4gIERlZmluZSB0aGUgbWVjaGFuaXNtIHRoYXQg
U0FDSyBpcyBzZW5kIGJhY2sgdG8gZW5kcG9pbnQgYnkgdGhlDQo+PiAgc2Vjb25kYXJ5IHBhdGgg
aWYgdGhlIHByaW1hcnkgcGF0aCBmYWlscyAuDQo+PiAgRGVmaW5lICB0aGUgbWVjaGFuaXNtIGhv
dyB0aGUgcHJpbWFyeSBwYXRoIGNhbiBiZSB1bmlvbml6ZWQgYmV0d2Vlbg0KPj4gIHR3byBub2Rl
cy4NCj4+DQo+Pg0KPj4gIFByb3Bvc2FsIGZvciBTdXBwbGVtZW50IG9mIFJGQzQ0NjANCj4+DQo+
Pg0KPj4gIDGjqUFkZCB0aGUgbWVjaGFuaXNtIGhvdyB0aGUgcHJpbWFyeSBwYXRoIGNhbiBiZSB1
bmlvbml6ZWQgYmV0d2Vlbg0KPj4gIHR3byBub2RlcyBpbiBTZWN0aW9uIDUgIKGuQXNzb2NpYXRp
b24gSW5pdGlhbGl6YXRpb24goa8uDQo+PiAgMqOpIEFkZCB0aGUgbWVjaGFuaXNtIHRoYXQgU0FD
SyBpcyBzZW5kIGJhY2sgdG8gZW5kcG9pbnQgYnkgdGhlDQo+PiAgc2Vjb25kYXJ5IHBhdGggaWYg
dGhlIHByaW1hcnkgcGF0aCBmYWlscyBpbiBTZWN0aW9uIDYuMg0KPj4gIKGuQWNrbm93bGVkZ2Vt
ZW50IG9uIFJlY2VwdGlvbiBvZiBEQVRBIENodW5rcyChry4NCj4+DQo+PiAoVGhhdCdzIGFsbCBm
b3IgU0NUUCkNCj4+DQo+Pg0KPj4gID09PT09PT09PT09PT09PT09PT09PT09PT09PT09DQo+PiAg
Zm9yIE0zVUEgb2YgQ2hpbmEgTW9iaWxlLnBwdA0KPj4gID09PT09PT09PT09PT09PT09PT09PT09
PT09PT09DQo+Pg0KPj4gIFRoZSBSZXF1aXJlbWVudCBhbmQgUHJvcG9zYWwNCj4+ICAgZm9yIE0z
VUEgU3BlY2lmaWNhdGlvbiBFeHRlbnNpb24NCj4+ICAgb2YgQ2hpbmEgTW9iaWxlDQo+Pg0KPj4g
IENoZW4gWHUNCj4+ICBDaGluYSBNb2JpbGUNCj4+DQo+Pg0KPj4gIENvbnRlbnQNCj4+DQo+PiBC
YWNrZ3JvdW5kDQo+PiAgUHJvYmxlbSBEZXNjcmlwdGlvbg0KPj4gIFJlcXVpcmVtZW50IGZvciBF
eHRlbnNpb24gb2YgUkZDNDY2Ng0KPj4gIFByb3Bvc2FsIGZvciBFeHRlbnNpb24gb2YgUkZDNDY2
Ng0KPj4NCj4+DQo+Pg0KPj4gIEJhY2tncm91bmQNCj4+DQo+PiAgVGhlIGFwcGxpY2F0aW9uIG9m
IFNJR1RSQU4gc3RhbmRhcmQgZm9yIFNHIGhhcyBldmVyIHNvbHZlZCB0aGUNCj4+ICBwcm9ibGVt
cyBvZiAgTm8uNyBTaWduYWxsaW5nIFN5c3RlbSBJbnRlcndvcmtpbmcgSVAgYW5kDQo+PiAgdHJh
bnNtaXNzaW9uIG9mICBhY2Nlc3MgbmV0d29yayBzaWduYWxsaW5nICBpbiAgUjQgQ1MgY29yZSBu
ZXR3b3JrLg0KPj4gIFRoZSB3b3JsZCB0cmVuZCBvZiBJUCBiZWFyZXIgZm9yIHNpZ25hbGxpbmcg
d2lsbCBtYWtlIFNJR1RSQU4NCj4+ICBzdGFuZGFyZCB3aWRlbHkgdXNlZCBpbiBzaWduYWxsaW5n
IG5ldHdvcmsuDQo+PiAgVHJhZGl0aW9uYWwgYW5kIG5ldyBUZWxlY29tIGNhcnJpZXJzIGltcGxl
bWVudCBzaWduYWxsaW5nIG92ZXIgSVAgdG8NCj4+ICBSZWR1Y2UgIGNvc3QgZm9yIGV4dGVuZGVk
IGNhcGFjaXR5DQo+PiAgUmVtb3ZlcyB0aGUgbGlua3MvbGlua3NldCBsaW1pdGF0aW9uIGltcG9z
ZWQgYnkgdHJhZGl0aW9uYWwgVERNDQo+PiAgbGlua3NldHMgZm9yIHRyYWZmaWMgZ3Jvd3RoDQo+
PiAgQXZvaWQgbWFqb3IgbmV0d29yayByZS1lbmdpbmVlcmluZyBhcyB0cmFmZmljIGdyb3dzDQo+
Pg0KPj4gIFNJR1RSQU4gaXMgYWxzbyBpbXBvcnRhbnQgdG8gQ2hpbmEgTW9iaWxlDQo+PiAgQXBw
bHlpbmcgdG8gdGhlIE5jIGludGVyZmFjZSBvZiBCSUNDIG5ldHdvcmsgdG8gdHJhbnNwb3J0IEJJ
Q0MNCj4+ICBtZXNzYWdlcw0KPj4gIEFwcGx5aW5nIHRvIHRoZSBpbnRlcmZhY2UgYmV0d2VlbiBN
U0MgU2VydmVyIGFuZCBlbWJlZGVkIFNHIHRvDQo+PiAgdHJhbnNwb3J0IGFjY2VzcyBuZXR3b3Jr
IHNpZ25hbGxpbmcNCj4+ICBBcHBseWluZyB0byBzaWduYWxsaW5nIG5ldHdvcmsNCj4+ICB0aGUg
aW50ZXJmYWNlIGJldHdlZW4gSVBTRVBzoaqhqk0zVUENCj4+ICB0aGUgaW50ZXJmYWNlIGJldHdl
ZW4gSVBTVFBzoaqhqk0yUEENCj4+ICB0aGUgaW50ZXJmYWNlIGJldHdlZW4gSVBTRVAgYW5kIElQ
U1RQoaqhqk0zVUENCj4+DQo+PiAgUHJvYmxlbSBkZXNjcmlwdGlvbg0KPj4NCj4+ICBNM1VBIHNw
ZWNpZmljYXRpb24gZG9lc26hr3QgIGRlZmluZSBzaWduYWxpbmcgbmV0d29yayAgbWFuYWdlbWVu
dA0KPj4gIGZ1bmN0aW9uDQo+PiAgTTNVQSBpcyBkZXNpZ25lZCBmb3IgU0ctSVBTRVAgYW5kIElQ
U0VQLUlQU0VQIGFwcGxpY2F0aW9ucywNCj4+ICB0aGVyZWZvcmUgbmV0d29yayBsZXZlbCBtYW5h
Z2VtZW50IGZ1bmN0aW9uIGlzbqGvdCByZXF1aXJlZC4NCj4+ICBTU05NIG1lc3NhZ2VzIGRlZmlu
ZWQgaW4gTTNVQSBhcmUgb25seSB1c2VkIGZvciBpbnRlcndvcmtpbmcgd2l0aCAgDQo+PiBTUzcu
DQo+PiAgQ2hpbmEgTW9iaWxlIGhhcyBhIGxhcmdlIG51bWJlciBvZiBzdWJzY3JpYmVycyBhbmQg
aGFzIGJ1aWx0IHRoZQ0KPj4gIGxhcmdlc3Qgc29mdC1zd2l0Y2ggbmV0d29yayBpbiB0aGUgd29y
bGQsIGl0cyBzaWduYWxpbmcgbmV0d29yaw0KPj4gIHdpbGwgYmUgdGhlIG11bHRpLWxldmVsIGFu
ZCBtdWx0aS1hcmVhIG1vZGUuDQo+PiAgSXQgd2lsbCBoYXMgdHdvIHNpZ25hbGxpbmcgcm91dGVp
bmcgIHNjZW5lOklQU0VQLUlQU1RQLUlQU1RQLUlQU0VQDQo+PiAgYW5kIElQU0VQLUlQU1RQLUlQ
U0VQDQo+PiAgVGhlIGludGVyd29ya2luZyAgZnVuY3Rpb24gd2l0aCBNVFAzIGluIE0zVUEgY2Fu
IHJlYWxpemUgdGhlDQo+PiAgc2lnbmFsaW5nIG5ldHdvcmsgIG1hbmFnZW1lbnQgZm9yICBJUFNF
UC1JUFNUUC1JUFNUUC1JUFNFUCBzY2VuZTsNCj4+ICBDdXJyZW50IE0zVUEgIGNhbiBub3QgIHJl
YWxpemUgdGhlIHNpZ25hbGluZyBuZXR3b3JrICBtYW5hZ2VtZW50DQo+PiAgZm9yICBJUFNFUC1J
UFNUUC1JUFNFUCBzY2VuZS4NCj4+DQo+PiAgUmVxdWlyZW1lbnQgZm9yIEV4dGVuc2lvbiBvZiBS
RkM0NjY2DQo+Pg0KPj4gIERlZmluZSB0aGUgQXBwbGljYXRpb24gZm9yIElQU1RQLUlQU0VQIGlu
dGVyZmFjZS4oU3RpbGwgdXNlcyBTR1AtDQo+PiAgQVNQIHByb2NlZHVyZXMpDQo+PiAgRGVmaW5l
IHRoZSBzaWduYWxsaW5nIG5ldHdvcmsgbWFuYWdlbWVudCBmdW5jdGlvbqOsbWVzc2FnZXMgLGFu
ZA0KPj4gIHByb2NlZHVyZXMuKERlc2NyaWJlIGhvdyB0byB1c2UgU1NOTSBtZXNzYWdlcyB0byBz
dXBwb3J0IHNpZ25hbGluZw0KPj4gIG5ldHdvcmsgbWFuYWdlbWVudCBmb3IgSVBTRVAtKE0zVUEp
LUlQU1RQLShNM1VBKS1JUFNFUCBzY2VuZS4gKQ0KPj4NCj4+ICBQcm9wb3NhbCBmb3IgRXh0ZW5z
aW9uIG9mIFJGQzQ2NjYNCj4+DQo+PiAgMaOpQWRkIGRpZmZlcmVudCBraW5kcyBvZiByb3V0aW5n
IHNjZW5lcyBhcHBsaWNhdGlvbnMgZm9yIElQU0VQLQ0KPj4gIElQU1RQIGludGVyZmFjZSBpbiBT
ZWN0aW9uIDEuNSAgoa5TYW1wbGUgQ29uZmlndXJhdGlvbiChry4NCj4+ICAyo6lBZGQgdGhlIE0z
VUEgc2lnbmFsbGluZyBuZXR3b3JrIG1hbmFnZW1lbnQgZnVuY3Rpb24gaW4gU2VjdGlvbg0KPj4g
IDEuNCAgoa5GdW5jdGlvbmFsIEFyZWFzoa8uDQo+PiAgM6OpIEFkZCB0aGUgQ2xpZW50L1NlcnZl
ciBNb2RlbCBmb3IgSVBTVFAtSVBTRVAgaW50ZXJmYWNlIGluDQo+PiAgU2VjdGlvbiAxLjQuOC4g
IKGuU0NUUCBDbGllbnQvU2VydmVyIE1vZGVsoa8uDQo+PiAgNKOpRXh0ZW5kIHRoZSBEVVBVIG1l
c3NhZ2UgY29kZSBpbiBDaGFwdGVyIDMgoa5NM1VBIFByb3RvY29sDQo+PiAgRWxlbWVudHOhry4N
Cj4+ICA1o6lBZGQgdGhlIHNpZ25hbGxpbmcgbmV0d29yayBtYW5hZ2VtZW50IHByb2NlZHVyZSBp
biBDaGFwdGVyDQo+PiAgNKGvcHJvY2VkdXJloa8uDQo+PiAgNikgQWRkIHRoZSByZXF1aXJlbWVu
dCBvZiBNdWx0aSB1c2VyIGRhdGEgc3RyZWFtcyBmb3IgTTNVQSBvdmVyDQo+PiAgU0NUUCBBcHBs
aWNhdGlvbiBpbiBTZWN0aW9uIDEuNC43IKGuIFNDVFAgU3RyZWFtIE1hcHBpbmehry4NCj4+DQo+
PiAoVGhhdCdzIGFsbCBmb3IgTTNVQSkNCj4+DQo+Pg0KPj4gID09PT09PT09PT09PT09PT09PT09
PT09PT09PT09DQo+PiAgZm9yIE0yUEEgb2YgQ2hpbmEgTW9iaWxlLnBwdA0KPj4gID09PT09PT09
PT09PT09PT09PT09PT09PT09PT09DQo+Pg0KPj4gIFRoZSBSZXF1aXJlbWVudCBhbmQgUHJvcG9z
YWwNCj4+ICAgZm9yIE0yUEEgU3BlY2lmaWNhdGlvbiBSZXZpc2lvbg0KPj4gICBvZiBDaGluYSBN
b2JpbGUNCj4+DQo+PiAgQ2hlbiBYdQ0KPj4gIENoaW5hIE1vYmlsZQ0KPj4NCj4+ICBDb250ZW50
DQo+Pg0KPj4gIEJhY2tncm91bmQNCj4+ICBQcm9ibGVtIERlc2NyaXB0aW9uDQo+PiAgUmVxdWly
ZW1lbnQgZm9yIFJldmlzaW9uIG9mIFJGQzQxNjUNCj4+ICBQcm9wb3NhbCBmb3IgUmV2aXNpb24g
b2YgUkZDNDE2NQ0KPj4NCj4+DQo+PiAgQmFja2dyb3VuZA0KPj4NCj4+ICBNMlBBIHByb3RvY29s
IGlzIGEgcGVlciB0byBwZWVyIHByb3RvY29sLCBpdCBub3Qgb25seSBzdXBwb3J0cw0KPj4gIHNl
YW1sZXNzIG1hbmFnZW1lbnQgb3BlcmF0aW9uIG9mIE1UUDMgcHJvdG9jb2wgcGVlcnMgb3ZlciBh
biBJUA0KPj4gIG5ldHdvcmsgY29ubmVjdGlvbiwgYnV0IGFsc28gcmVtb3ZlcyB0aGUgbGlua3Mv
bGlua3NldCBsaW1pdGF0aW9uDQo+PiAgaW1wb3NlZCBieSB0cmFkaXRpb25hbCBURE0gbGlua3Nl
dHMgZm9yIHRyYWZmaWMgZ3Jvd3RoLg0KPj4NCj4+ICBUaGUgU3RhbmRhcmRpemF0aW9uIG9mIE0y
UEEgaXMgYmVoaW5kIHRoZSBhcHBsaWNhdGlvbiBvZiBpdC4NCj4+ICBBbHRob3VnaCB0aGUgUkZD
IGVkaXRpb24gaXMgcmVsZWFzZWQgaW4gMjAwNSwgTTJQQSBpcyB3aWRlbHkgdXNlZA0KPj4gIGlu
IHRoZSAgU2lnbmFsaW5nIG5ldHdvcmsgcmVidWlsZGluZyBvdmVyIElQIGZvciB0cmFkaXRpb25h
bA0KPj4gIG9wZXJhdG9ycyBhbmQgaW4gdGhlIFNpZ25hbGluZyBuZXR3b3JrIGNvbnN0cnVjdGlv
biBmb3IgIG5ldw0KPj4gIG9wZXJhdG9ycyAgc2luY2UgMjAwMi4NCj4+DQo+PiAgVmFyaW91cyBk
cmFmdCBlZGl0aW9ucyBhbmQgdGhlIG1ham9yIGRpZmZlcmVuY2VzIGJldHdlZW4gdGhlbSBtYWtl
DQo+PiAgcHJvYmxlbXMgd2hlbiBvbmUgIElQU1RQIHByb3ZpZGVyIGludGVyd29ya2luZyB3aXRo
IGFub3RoZXIuDQo+Pg0KPj4gIFByb2JsZW0gRGVzY3JpcHRpb24NCj4+DQo+Pg0KPj4gIFJGQzQx
NjUgbmVlZHMgdG8gYmUgc3VwcGxlbWVudGVkIGFuZCByZXZpc2VkIKO6DQo+PiAgU29tZSAgcHJv
Y2VkdXJlcyAgYXJlICBkZXNjcmliZWQgYSBsaXR0bGUgYml0IHNpbXBseSBhbmQgcmVmZXJyZWQN
Cj4+ICB0byBNVFAyIGRpcmVjdGx5ICwgIHdoaWNoICBtYWtlcyBJUFNUUCAgcHJvdmlkZXJzIHJl
YWxpemluZyB0aGUNCj4+ICBwcm9jZWR1cmVzIGluIGRpZmZlcmVudCB3YXlzICxmb3IgIHRoZXJl
oa9zIGRpZmZlcmVuY2UgYmV0d2VlbiBNVFAyDQo+PiAgYW5kIE0yUEEgaW4gc29tZSBhc3BlY3Rz
LiAgICAgIC4NCj4+ICBTb21lIElQU1RQIHByb3ZpZGVycyB1c2UgdGhlIHNhbWUgaWRlYSBhcyBN
VFAyDQo+PiAgT3RoZXJzIHRha2UgdGhlIHJlbGF0aW9uIGJldHdlZW4gTTJQQSBhbmQgU0NUUCBp
bnRvIGFjY291bnQuDQo+Pg0KPj4gIFQ3IGlzbqGvdCBkZWZpbmVkIGFuZCBnaXZlbiB0aGUgcmFu
Z2UsIHdoaWNoIG1ha2VzIElQU1RQIHByb3ZpZGVycw0KPj4gIHJlYWxpemluZyBpdCBpbiBkaWZm
ZXJlbnQgd2F5cy4NCj4+DQo+PiAgSG93IHRvIGZpbGwgaW4gYW5kIHByb2Nlc3MgRlNOIGFuZCBC
U04gaW4gTTJQQSBIZWFkZXIgaXNuoa90DQo+PiAgZGVmaW5lZCBjbGVhcmx5Lg0KPj4NCj4+DQo+
PiAgUmVxdWlyZW1lbnQgZm9yIFJldmlzaW9uIG9mIFJGQzQxNjUNCj4+DQo+PiAgU3VwcGxlbWVu
dCB0aGUgZGVzY3JpcHRpb24gb2YgdGhlIHdob2xlIGlkZWEgZm9yIExpbmsgQWxpZ25tZW50DQo+
PiAgcHJvY2VkdXJlIGFuZCBQcm9jZXNzb3IgT3V0YWdlIHByb2NlZHVyZS4NCj4+ICBTdXBwbGVt
ZW50IHRoZSBkZWZpbml0aW9uIGFuZCByYW5nZSBvZiBNMlBBIFRpbWVycy4NCj4+ICBTdXBwbGVt
ZW50IHRoZSBydWxlcyBvZiB1c2FnZSBvZiBGU04gYW5kIEJTTiBpbiBNMlBBIEhlYWRlci4NCj4+
DQo+Pg0KPj4gIFByb3Bvc2FsIGZvciBSZXZpc2lvbiBvZiBSRkM0MTY1DQo+Pg0KPj4gIDGjqVN1
cHBsZW1lbnQgdGhlIHdob2xlIGlkZWEgLCB0aGUgcGhhc2UgZGl2aXNpb24gLCB0aGUgY29ycmVs
YXRlZA0KPj4gIG1lc3NhZ2VzIGFuZCBUaW1lcnMgb2YgTGluayBBbGlnbm1lbnQgcHJvY2VkdXJl
IGluIFNlY3Rpb24gNC4xLjMuDQo+PiAgMqOpU3VwcGxlbWVudCB0aGUgd2hvbGUgaWRlYSBvZiBQ
cm9jZXNzb3IgT3V0YWdlIHByb2NlZHVyZSwgYW5kDQo+PiAgZGVzY3JpYmUgdGhlIHJ1bGVzIG9m
IExQTyBhbmQgUlBPIHByb2Nlc3Npbmcgc2VwYXJhdGVseSAuDQo+PiAgM6OpU3VwcGxlbWVudCB0
aGUgcnVsZXMgb2YgdXNhZ2Ugb2YgRlNOIGFuZCBCU04gaW4gTTJQQSBIZWFkZXIgaW4NCj4+ICBT
ZWN0aW9uIDQuMi4xDQo+PiAgNKOpU3VwcGxlbWVudCB0aGUgZGVmaW5pdGlvbiBhbmQgcmFuZ2Ug
b2YgTTJQQSBUaW1lcnMgaW4gQXBwZW5kaXguDQo+Pg0KPj4gKFRoYXQncyBhbGwgZm9yIE0yUEEp
DQo+Pg0KPj4gQ2hlbiBYdQ0KPj4gQ2hpbmEgTW9iaWxlDQo+PiBjaGVueHVAY2hpbmFtb2JpbGUu
Y29tDQo+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0K
Pj4gU2lndHJhbiBtYWlsaW5nIGxpc3QNCj4+IFNpZ3RyYW5AaWV0Zi5vcmcNCj4+IGh0dHBzOi8v
d3d3MS5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NpZ3RyYW4NCg0KDQo=







From tsvwg-bounces@ietf.org Fri Jul 27 10:19:10 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEQdv-0004P5-Fa; Fri, 27 Jul 2007 10:18:11 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IEQdt-0004Om-JY
	for tsvwg-confirm+ok@megatron.ietf.org; Fri, 27 Jul 2007 10:18:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEQdt-0004Od-9r
	for tsvwg@ietf.org; Fri, 27 Jul 2007 10:18:09 -0400
Received: from [2001:630:241:204:203:baff:fe9a:8c9b] (helo=erg.abdn.ac.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEQds-0005AV-Oj
	for tsvwg@ietf.org; Fri, 27 Jul 2007 10:18:09 -0400
Received: from [130.129.17.235] (dhcp-11eb.ietf69.org [130.129.17.235])
	(authenticated bits=0)
	by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id l6REG7C2021289
	(version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NOT)
	for <tsvwg@ietf.org>; Fri, 27 Jul 2007 15:16:09 +0100 (BST)
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Fri, 27 Jul 2007 08:41:37 -0500
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
To: tsvwg WG <tsvwg@ietf.org>
Message-ID: <C2CF6041.7927%gorry@erg.abdn.ac.uk>
Thread-Topic: ECN with Tunnels - to copy or change the ECN in the outer header
Thread-Index: AcfQU9p/GOLCfDxHEdyEBQAKlc/qXg==
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: gorry@erg.abdn.ac.uk
X-Spam-Status: No
X-Spam-Score: -1.4 (-)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Subject: [Tsvwg] ECN with Tunnels - to copy or change the ECN in the outer
	header
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org


I have a query about the draft on ECN use with Tunnels, relating to the ECN
codepoint copying that I raised in the TSV meeting yesterday.

As I understand, the adjustment to IPsec related only to copying the 2 SCN
bits (plus DS codepoints) from the outer to the inner on ingress and back
again at egress. I agree we SHOULD also do a similar recommendation for
Tunnels in general, and I'd like to see this STD-Track for use in the
General Internet.

However, I am concerned that this draft does not only address these problems
(which could be a PS), but it also adds new concepts as well.

In the ECN architecture, my understanding is that HOSTs choose to set the
ECN field to ECT(0) and ECT(1), depending upon the policy at the sender. ECN
Nonce ( RFC3540) implies a specific semantic to this. The IETF has a BCP
that also says how other alternative semantics may be applied with specific
DS codepoints (RFC4774).

There seem to be two new ideas here. While this may be being considered in
other places, I do not recall it as a part of the original design for ECN:

* The idea that packets from an end host that do not use an ECN-capable
transport can be mapped to an ECT codepoint over a congestion-controlled
tunnel. The current scope of this work in the IETF seems to be scoped only
for use within a PCN domain.

* The idea that packets marked with an ECN codepoint may be remarked to a
different ECN codepoint by some tunnel endpoints, including mapping CE to an
ECT value, and mapping ECT(1) to ECT(0).

  "If the tunnel
   ingress is also a Load Regulator, it MUST instead reset the outer
   header to ECT(0)."

Section 7:
  "The rule that a tunnel ingress MUST copy any ECN field into the outer
   header is a change to RFC3168 (unless it is a Load Regulator as well,
   in which case there is no change)."


The draft describes permitting a mid-box/router to choose to reset the code
point to ECT(0) when it was originally set to some other value.

- So my view on this varies depending on the original value:
N-ECT  -> ECT(0) ... I think this was the goal,
                    but is this safe in the general internet?
ECT(0) -> ECT(0) ... No change
ECT(1) -> ECT(0) ... This contradicts  RFC3540 and RFC4774, and seems
                    like we are limiting options for using schemes
                    currently permitted and options for the future.
CE     -> ECT(0) ... What are the implications of this when transiting
                    a network using ECN or alt. ECN semantics?


Best wishes,

Gorry







From tsvwg-bounces@ietf.org Fri Jul 27 15:12:13 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEVEL-00033i-Q1; Fri, 27 Jul 2007 15:12:05 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IEVEK-0002yj-Dx
	for tsvwg-confirm+ok@megatron.ietf.org; Fri, 27 Jul 2007 15:12:04 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEVEK-0002wn-2Z; Fri, 27 Jul 2007 15:12:04 -0400
Received: from mail119.messagelabs.com ([216.82.241.179])
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1IEVEJ-0004lp-Kj; Fri, 27 Jul 2007 15:12:03 -0400
X-VirusChecked: Checked
X-Env-Sender: Qiaobing.Xie@motorola.com
X-Msg-Ref: server-3.tower-119.messagelabs.com!1185563521!24837791!1
X-StarScan-Version: 5.5.12.11; banners=-,-,-
X-Originating-IP: [144.189.100.105]
Received: (qmail 16471 invoked from network); 27 Jul 2007 19:12:01 -0000
Received: from motgate5.mot.com (HELO motgate5.mot.com) (144.189.100.105)
	by server-3.tower-119.messagelabs.com with SMTP;
	27 Jul 2007 19:12:01 -0000
Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232])
	by motgate5.mot.com (8.12.11/Motorola) with ESMTP id l6RJC0r0018784;
	Fri, 27 Jul 2007 12:12:00 -0700 (MST)
Received: from [192.168.15.2] (mvp-10-31-8-50.am.mot.com [10.31.8.50])
	by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id l6RJ7vaQ010632;
	Fri, 27 Jul 2007 14:07:58 -0500 (CDT)
Message-ID: <46AA4259.9050503@motorola.com>
Date: Fri, 27 Jul 2007 14:07:05 -0500
From: Qiaobing Xie <Qiaobing.Xie@motorola.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: =?GB2312?B?s8LQ8Q==?= <chenxu@chinamobile.com>
References: <OF24565732.6AADA0AB-ON48257325.00301996@chinamobile.com>
In-Reply-To: <OF24565732.6AADA0AB-ON48257325.00301996@chinamobile.com>
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: 8bit
X-Spam-Score: 1.7 (+)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
	SIGTRAN <sigtran@ietf.org>, TSWG <tsvwg@ietf.org>
Subject: [Tsvwg] Re: [Sigtran] The requiremnts
 and	proposalsforM2PA/M3UA/SCTPExtension from China Mobile
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=GB2312" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Dear ³ÂÐñ,<br>
<blockquote
 cite="midOF24565732.6AADA0AB-ON48257325.00301996@chinamobile.com"
 type="cite">
  <pre wrap="">Dear Michael Tuexen,

  </pre>
  <blockquote type="cite">
    <pre wrap="">   1. What does "unionize of the primary paths between nodes" mean?
    </pre>
  </blockquote>
  <pre wrap=""><!---->   It means£¬for one multi-homed SCTP endpoint,the primary path£¨source IP address=IP1---destination IP=IP2£© shall be the same as the remote endpoint's ( source IP address=IP2---destination IP=IP1  )   
  </pre>
</blockquote>
You can easily do your "unionize" by using ASCONF to set the primary
destination at both endpoints. In other words, this extension is
already provided by draft-ietf-tsvwg-addip-sctp-22.txt (which is in RFC
editor's queue).<br>
<blockquote
 cite="midOF24565732.6AADA0AB-ON48257325.00301996@chinamobile.com"
 type="cite">
  <pre wrap="">   
   Many venders implement Multi-homing in the following way:

    one multi-homed SCTP endpoint has two local IP addresses(IP1/IP2) and two remote IP address(IP3/IP4) within an association.
    There's two paths within an association:IP1-IP3,and IP2-IP4.not 4 paths. 
   
    For example, endpoint1 has two local IP addresses(IP1/IP2)£¬ and endpoint2 has two local IP addresses(IP3/IP4).

if two endpoints' primary path isn't the same,that is endpoint1 use IP1-IP3 as the primary path, use IP2-IP4 as the second path;  endpoint2 use IP3-IP2 as the primary path, use IP4-IP1 as the second path. 

    These two endpoints can't  send data to each other successfully.  
  </pre>
  <blockquote type="cite">
    <pre wrap="">    2. Not sure about the SACK issue: You are currently allowed to
   send the SACK back to an addresses different from the source
   address of the corresponding DATA chunk. As far as I know
   it is only a SHOULD describing that you send the SACK back
   to the source address of the DATA chunk.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
     You are right,it is only a SHOULD describing that you send the SACK back
   to the source address of the DATA chunk in RFC2960.
      That's why we get in trouble in multi-homing situation. 
      If the  path to the source address of the DATA chunk is unreachable£¬the sack can't send to the remote endpoint for ever although the other path is available.Soon the other path will be failure.
  </pre>
</blockquote>
<br>
The "SHOULD" is meant to say that when possible (meaning your path is
healthy), you always send the SACK back to the source address of the
DATA chunk. When the path to the source address of the DATA chunk is
unreachable, you are of cause allowed to send the SACK back to other
address(es). In other words, what you want to do is already perfectly
allowed in SCTP.<br>
<br>
regards,<br>
-Qiaobing<br>
<br>
</body>
</html>






From tsvwg-bounces@ietf.org Sat Jul 28 06:42:36 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEjkf-0007OJ-O8; Sat, 28 Jul 2007 06:42:25 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IEjke-0007O3-KZ
	for tsvwg-confirm+ok@megatron.ietf.org; Sat, 28 Jul 2007 06:42:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEjkd-0007Nq-Jm; Sat, 28 Jul 2007 06:42:24 -0400
Received: from [2001:240:585:2:203:6dff:fe1a:4ddc] (helo=lakerest.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IEjkb-0002HS-Ie; Sat, 28 Jul 2007 06:42:23 -0400
Received: from [172.28.168.224] ([67.97.210.2]) (authenticated bits=0)
	by lakerest.net (8.14.1/8.14.1) with ESMTP id l6SAfgQk074855
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Sat, 28 Jul 2007 06:41:52 -0400 (EDT)
	(envelope-from randall@lakerest.net)
DKIM-Signature: a=rsa-sha1; c=simple/simple; d=lakerest.net; s=lakerest;
	t=1185619318; h=Message-ID:Date:From:User-Agent:X-Accept-Language:
	MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:
	Content-Transfer-Encoding; b=TdSiLL3b42r/GjjlG4gi+eEemiFTvC5vu8iDHO
	6BtXSZLuAbj1vmXrPf/cZMsLTKcrJcQ5ixhZFmWdnM8Bm4tQ==
Message-ID: <46AB1D7B.6040404@lakerest.net>
Date: Sat, 28 Jul 2007 06:42:03 -0400
From: Randall Stewart <randall@lakerest.net>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.13) Gecko/20070601
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: =?ISO-8859-1?Q?=B3=C2=D0=F1?= <chenxu@chinamobile.com>
Subject: Re: [Tsvwg] Re: [Sigtran] The requiremnts
	and	proposalsforM2PA/M3UA/SCTPExtension from China Mobile
References: <OF24565732.6AADA0AB-ON48257325.00301996@chinamobile.com>
	<20070727063705.A13093@openss7.org>
In-Reply-To: <20070727063705.A13093@openss7.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by lakerest.net id
	l6SAfgQk074855
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, bidulock@openss7.org,
	SIGTRAN <sigtran@ietf.org>, TSWG <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Chen:

I pretty much agree with Brian here..

Most implementations will follow the steps that
Brian lists for source address selection. Yes its completely
possible to setup routing tables that will not work... but
this is a configuration error.. not a deficency in the protocol.

As to sacks, I think most all implementations that I know of attempt
to switch sacks to an alternate destination when they start
seeing duplicate data. I will discuss this item with all the developers
going to Kyoto for the SCTP-Interop (in 2 weeks)... and I will see if
anyone does not do this.. I would be quite surprised to see anyone not
using the duplicate data (as Brian mentions below) as an indication
to move to an alternate address to send the SACK back to.

R

Brian F. G. Bidulock wrote:
> Chen,
>=20
> =B3=C2=D0=F1 wrote:                                  (Fri, 27 Jul 2007 =
16:45:12)
>=20
>>Dear Michael Tuexen,
>>
>>=09
>>
>>>   1. What does "unionize of the primary paths between nodes" mean?
>>
>>It means=A3=ACfor one multi-homed SCTP endpoint,the primary path=A3=A8s=
ource
>>IP address=3DIP1---destination IP=3DIP2=A3=A9 shall be the same as the =
remote
>>endpoint's ( source IP address=3DIP2---destination IP=3DIP1  )  =20
>>  =20
>>Many venders implement Multi-homing in the following way:
>>
>>one multi-homed SCTP endpoint has two local IP addresses(IP1/IP2) and
>>two remote IP address(IP3/IP4) within an association.  There's two
>>paths within an association:IP1-IP3,and IP2-IP4.not 4 paths.=20
>=20
>=20
> That sounds rather foolish.  What I do is as follows:
>=20
>   When sending to IP3, choose the best route (metric) to IP3.
>   If no route to IP3 exists, don't send to IP3, send to another
>     destination for the association.
>   If a route to IP3 exists, and the source address of the outbound
>     interface of this route includes a local address for the
>     association, use that as the source address when using the route.
>     Otherwise, use the first source address of the association.
>=20
>   When sending to IP4, choose the best route (metric) to IP4.
>   If no route to IP4 exists, don't send to IP4, send to another
>     destination for the association.
>   If a route to IP4 exists, and the source address of the outbound
>     interface of this route includes a local address for the
>     association, use that as the source address when using the route.
>     Otherwise, use the first source address of the association.
>=20
> This only results in IP1-IP3 and IP2-IP4 if the only route to IP3 is
> from an interface with IP1 and the only route to IP4 is from an
> interface with IP2.
>=20
>=20
>>  =20
>>For example, endpoint1 has two local IP addresses(IP1/IP2)=A3=AC and
>>endpoint2 has two local IP addresses(IP3/IP4).
>>
>>if two endpoints' primary path isn't the same,that is endpoint1 use
>>IP1-IP3 as the primary path, use IP2-IP4 as the second path;
>>endpoint2 use IP3-IP2 as the primary path, use IP4-IP1 as the second
>>path.=20
>>
>>These two endpoints can't  send data to each other successfully. =20
>=20
>=20
> Yes, it is possible to set up your routing tables on two host so that
> the cannot communicate.  This is even possible with TCP.
>=20
> If the problem is not merely routing table, I suggest you choose anothe=
r
> vendor or work with your existing vendor to correct the deficiencies in
> their implementation.
>=20
>=20
>>       =20
>>
>>
>>>    2. Not sure about the SACK issue: You are currently allowed to
>>>   send the SACK back to an addresses different from the source
>>>   address of the corresponding DATA chunk. As far as I know
>>>   it is only a SHOULD describing that you send the SACK back
>>>   to the source address of the DATA chunk.
>>
>>You are right,it is only a SHOULD describing that you send the SACK
>>back to the source address of the DATA chunk in RFC2960.  That's why
>>we get in trouble in multi-homing situation.  If the  path to the
>>source address of the DATA chunk is unreachable=A3=ACthe sack can't sen=
d
>>to the remote endpoint for ever although the other path is
>>available.Soon the other path will be failure.
>=20
>=20
> Well, no, not in the reasonable implementation.  When SACKs are being
> sent to a destination and are not reaching the peer endpoint, a
> retransmission timeout will result in duplicate TSNs being sent.  The
> peer receiving duplicate TSNs should realized that their SACKs are
> likely being sent into a black hole and begin sending SACKs to a
> different destination.  This is already in RFC 2960:
>=20
> 6.4 Multi-homed SCTP Endpoints
>=20
>    ...
>=20
>    When a receiver of a duplicate DATA chunk sends a SACK to a multi-
>    homed endpoint it MAY be beneficial to vary the destination address
>    and not use the source address of the DATA chunk.  The reason being
>    that receiving a duplicate from a multi-homed endpoint might indicat=
e
>    that the return path (as specified in the source address of the DATA
>    chunk) for the SACK is broken.
>=20
>    ...
>=20
> If your current vendor does not implement this, I suggest that you
> request them to do so.
>=20
> --brian
>=20


--=20
Randall Stewart
803-345-0369 <or> 815-342-5222(cell)





From tsvwg-bounces@ietf.org Sun Jul 29 22:43:29 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFLDS-000299-17; Sun, 29 Jul 2007 22:42:38 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IFLDR-000278-6V
	for tsvwg-confirm+ok@megatron.ietf.org; Sun, 29 Jul 2007 22:42:37 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFLDQ-00023L-Qu
	for tsvwg@ietf.org; Sun, 29 Jul 2007 22:42:36 -0400
Received: from mexforward.lss.emc.com ([128.222.32.20])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IFLDP-0004Lh-SA
	for tsvwg@ietf.org; Sun, 29 Jul 2007 22:42:36 -0400
Received: from mailhub.lss.emc.com (uraeus.lss.emc.com [10.254.144.14])
	by mexforward.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id
	l6U2gQdR012522; Sun, 29 Jul 2007 22:42:26 -0400 (EDT)
Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com
	[10.254.64.53])
	by mailhub.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id
	l6U2g7TH013765; Sun, 29 Jul 2007 22:42:23 -0400 (EDT)
From: Black_David@emc.com
Received: from CORPUSMX20A.corp.emc.com ([128.221.62.12]) by
	corpussmtp3.corp.emc.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 29 Jul 2007 22:42:19 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Tsvwg] ECN with Tunnels - to copy or change the ECN in the
	outerheader
Date: Sun, 29 Jul 2007 22:42:18 -0400
Message-ID: <F222151D3323874393F83102D614E0550A4D23F5@CORPUSMX20A.corp.emc.com>
In-Reply-To: <C2CF6041.7927%gorry@erg.abdn.ac.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Tsvwg] ECN with Tunnels - to copy or change the ECN in the
	outerheader
Thread-Index: AcfQU9p/GOLCfDxHEdyEBQAKlc/qXgB+8qYg
References: <C2CF6041.7927%gorry@erg.abdn.ac.uk>
To: <gorry@erg.abdn.ac.uk>, <tsvwg@ietf.org>
X-OriginalArrivalTime: 30 Jul 2007 02:42:19.0472 (UTC)
	FILETIME=[3F9CFD00:01C7D253]
X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.5.1.298604,
	Antispam-Data: 2007.7.6.21134
X-PerlMx-Spam: Gauge=, SPAM=0%, Reason='EMC_BODY_1+ -3, EMC_FROM_0+ -3,
	NO_REAL_NAME 0, __C230066_P5 0, __CT 0, __CTE 0,
	__CT_TEXT_PLAIN 0, __HAS_MSGID 0, __IMS_MSGID 0,
	__MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0'
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
Cc: 
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Gorry,

> I have a query about the draft on ECN use with Tunnels, relating to
the ECN
> codepoint copying that I raised in the TSV meeting yesterday.
>=20
> As I understand, the adjustment to IPsec related only to copying the 2
ECN
> bits (plus DS codepoints) from the outer to the inner on ingress and
back
> again at egress. I agree we SHOULD also do a similar recommendation
for
> Tunnels in general, and I'd like to see this STD-Track for use in the
> General Internet.

IPsec (RFC 4301) does something slightly different on egress - it only
copies a CE codepoint from outer to inner. =20

> However, I am concerned that this draft does not only address these
problems
> (which could be a PS), but it also adds new concepts as well.=20
>=20
> In the ECN architecture, my understanding is that HOSTs choose to set
the
> ECN field to ECT(0) and ECT(1), depending upon the policy at the
sender. ECN
> Nonce ( RFC3540) implies a specific semantic to this. The IETF has a
BCP
> that also says how other alternative semantics may be applied with
specific
> DS codepoints (RFC4774).
>=20
> There seem to be two new ideas here. While this may be being
considered in
> other places, I do not recall it as a part of the original design for
ECN:
>=20
> * The idea that packets from an end host that do not use an
ECN-capable
> transport can be mapped to an ECT codepoint over a
congestion-controlled
> tunnel. The current scope of this work in the IETF seems to be scoped
only
> for use within a PCN domain.

I tend to agree.  Absent something like PCN that invokes alternate
semantics
for the ECN field, the congestion control for the tunnel would have to
be
TCP-like (reaction to congestion-marked packet is equivalent to reaction
to dropped packet) in order to comply with RFC 3168.
=20
> * The idea that packets marked with an ECN codepoint may be remarked
to a
> different ECN codepoint by some tunnel endpoints, including mapping CE
to an
> ECT value, and mapping ECT(1) to ECT(0).
>=20
>   "If the tunnel
>    ingress is also a Load Regulator, it MUST instead reset the outer
>    header to ECT(0)."
>=20
> Section 7:
>   "The rule that a tunnel ingress MUST copy any ECN field into the
outer
>    header is a change to RFC3168 (unless it is a Load Regulator as
well,
>    in which case there is no change)."

Bob and I have had some serious private discussions about this.
IMHO, the charitable conclusion is that the Load Regulator
concept in the draft has not been completely thought through
(after all, it is a "draft"), and I believe Bob is considering
just dropping it from the next version of this draft.

> The draft describes permitting a mid-box/router to choose to reset the
code
> point to ECT(0) when it was originally set to some other value.=20
>=20
> - So my view on this varies depending on the original value:
> N-ECT  -> ECT(0) ... I think this was the goal,
>                     but is this safe in the general internet?

Provided that the tunnel ingress *knows* that the tunnel egress
will do the "right thing" (e.g., drop if outer is marked with CE,
else forward with N-ECT from inner header) this should be ok, but
*knows* can't just be *assumes*.  This is headed in the interesting
direction of running a congestion control feedback loop from tunnel
ingress to egress in a fashion transparent to the end-to-end
congestion control.  There are some details to watch out for, as
a drop could activate both ingress-to-egress and end-to-end
congestion control.

> ECT(0) -> ECT(0) ... No change
> ECT(1) -> ECT(0) ... This contradicts  RFC3540 and RFC4774, and seems
>                     like we are limiting options for using schemes
>                     currently permitted and options for the future.

Hmm ... I have the impression that non-support for 3540 (experimental)
is "in play" as a potential part of PCN.  FWIW, 4301 (IPsec) tunneled
the 3540 nonce rather than propagating it through the outer header.
Beyond this, I can't agree with the "contradicts ... RFC 4774"
statement without a much longer discussion ;-).

> CE     -> ECT(0) ... What are the implications of this when transiting
>                     a network using ECN or alt. ECN semantics?

As long as CE is tunneled through the inner header and not overwritten
at tunnel egress (i.e., end receiver gets CE, not ECT(0) in received
packet), this should be ok, as a router that would otherwise set CE
doesn't do anything different with a packet that is already marked
with CE vs. just marked with ECT.  Dropping a CE-packet doesn't change
the reaction of a correct end-system and is not helpful to a correct
end-system.

Thanks,
--David
----------------------------------------------------
David L. Black, Senior Technologist
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953             FAX: +1 (508) 293-7786
black_david@emc.com        Mobile: +1 (978) 394-7754
----------------------------------------------------





From tsvwg-bounces@ietf.org Mon Jul 30 05:02:47 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFR9G-0000uV-2c; Mon, 30 Jul 2007 05:02:42 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IFR9E-0000sc-SA
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 30 Jul 2007 05:02:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFR9E-0000sJ-Hw; Mon, 30 Jul 2007 05:02:40 -0400
Received: from exprod7og60.obsmtp.com ([64.18.2.175])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IFR9D-000643-G7; Mon, 30 Jul 2007 05:02:40 -0400
Received: from source ([67.96.16.11]) (using TLSv1) by exprod7ob60.obsmtp.com
	([64.18.6.12]) with SMTP; Mon, 30 Jul 2007 02:02:29 PDT
Received: from ETSMSG-CINAV02.etsmsg.org ([65.90.82.49]) by
	naout-cinexs01.nasmtpout.emrsn.com with Microsoft
	SMTPSVC(6.0.3790.3959); Mon, 30 Jul 2007 05:14:14 -0400
Received: from etsmsg-cinexs03.etsmsg.org ([65.90.82.49]) by
	ETSMSG-CINAV02.etsmsg.org with InterScan Message Security Suite;
	Mon, 30 Jul 2007 05:02:28 -0400
Received: from ETSMSG-CINEXR03.etsmsg.org ([65.90.82.76]) by
	etsmsg-cinexs03.etsmsg.org with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 30 Jul 2007 05:02:28 -0400
Received: from USACG-MSNEXM01.astec.com ([10.206.84.182]) by
	ETSMSG-CINEXR03.etsmsg.org with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 30 Jul 2007 05:02:28 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Tsvwg] Re: [Sigtran] The
	requiremntsand	proposalsforM2PA/M3UA/SCTPExtension from China Mobile
Date: Mon, 30 Jul 2007 04:02:25 -0500
Message-ID: <DB255B459C0A1C458EB2D2353F1269CB03000D7E@USACG-MSNEXM01.astec.com>
In-Reply-To: <46AB1D7B.6040404@lakerest.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Tsvwg] Re: [Sigtran] The
	requiremntsand	proposalsforM2PA/M3UA/SCTPExtension from China
	Mobile
Thread-Index: AcfRBAmIA9Qb1NgMSeW3bepHEIxqAQBgmTaw
From: <ronnie@artesyncp.com>
To: <randall@lakerest.net>,
	<chenxu@chinamobile.com>
X-OriginalArrivalTime: 30 Jul 2007 09:02:28.0323 (UTC)
	FILETIME=[5ABF7330:01C7D288]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 93df555cbdbcdae9621e5b95d44b301e
Cc: Michael.Tuexen@lurchi.franken.de, bidulock@openss7.org, sigtran@ietf.org,
	tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi,

Won't this association have a serious problem with Heartbeats if you =
cannot send a Heartbeat Ack to the address the Heartbeat came from?

>From RFC 2960bis
	3.3.6. Heartbeat Acknowledgement (HEARTBEAT ACK) (5):=20

	An endpoint should send this chunk to its peer endpoint as a response =
to a 	HEARTBEAT chunk (see Section 8.3). A HEARTBEAT ACK is always sent =
to the source IP 	address of the IP datagram containing the HEARTBEAT =
chunk to which this ack is 	responding.

We also need to take into account that the source address of duplicate =
data may NOT be the source address used for the original data if the =
sending end has changed paths when the data wasn't acked.

If this is a routing problem which has been in place since the =
association was started then the sender should never send data to an =
unconfirmed address.  If the Heartbeat mechanism is broken the address =
will never be confirmed.

Ronnie
---
Ronnie Sellar			Emerson Network Power, Embedded Computing
Tel: +44 131 475 7015		Suite 4, 2 Anderson Place
Fax: +44 131 475 7001		Edinburgh EH6 5NP
mailto:ronnie@artesyncp.com	http://www.emersonembeddedcomputing.com
=20

> -----Original Message-----
> From: Randall Stewart [mailto:randall@lakerest.net]=20
> Sent: 28 July 2007 11:42
> To: =B3=C2=D0=F1
> Cc: Michael Tuexen; bidulock@openss7.org; SIGTRAN; TSWG
> Subject: Re: [Tsvwg] Re: [Sigtran] The requiremntsand=20
> proposalsforM2PA/M3UA/SCTPExtension from China Mobile
>=20
> Chen:
>=20
> I pretty much agree with Brian here..
>=20
> Most implementations will follow the steps that Brian lists=20
> for source address selection. Yes its completely possible to=20
> setup routing tables that will not work... but this is a=20
> configuration error.. not a deficency in the protocol.
>=20
> As to sacks, I think most all implementations that I know of=20
> attempt to switch sacks to an alternate destination when they=20
> start seeing duplicate data. I will discuss this item with=20
> all the developers going to Kyoto for the SCTP-Interop (in 2=20
> weeks)... and I will see if anyone does not do this.. I would=20
> be quite surprised to see anyone not using the duplicate data=20
> (as Brian mentions below) as an indication to move to an=20
> alternate address to send the SACK back to.
>=20
> R
>=20
> Brian F. G. Bidulock wrote:
> > Chen,
> >=20
> > =B3=C2=D0=F1 wrote:                                  (Fri, 27 Jul=20
> 2007 16:45:12)
> >=20
> >>Dear Michael Tuexen,
> >>
> >>=09
> >>
> >>>   1. What does "unionize of the primary paths between nodes" mean?
> >>
> >>It means=A3=ACfor one multi-homed SCTP endpoint,the primary=20
> path=A3=A8source=20
> >>IP address=3DIP1---destination IP=3DIP2=A3=A9 shall be the same as=20
> the remote
> >>endpoint's ( source IP address=3DIP2---destination IP=3DIP1  )  =20
> >>  =20
> >>Many venders implement Multi-homing in the following way:
> >>
> >>one multi-homed SCTP endpoint has two local IP=20
> addresses(IP1/IP2) and=20
> >>two remote IP address(IP3/IP4) within an association.  There's two=20
> >>paths within an association:IP1-IP3,and IP2-IP4.not 4 paths.
> >=20
> >=20
> > That sounds rather foolish.  What I do is as follows:
> >=20
> >   When sending to IP3, choose the best route (metric) to IP3.
> >   If no route to IP3 exists, don't send to IP3, send to another
> >     destination for the association.
> >   If a route to IP3 exists, and the source address of the outbound
> >     interface of this route includes a local address for the
> >     association, use that as the source address when using=20
> the route.
> >     Otherwise, use the first source address of the association.
> >=20
> >   When sending to IP4, choose the best route (metric) to IP4.
> >   If no route to IP4 exists, don't send to IP4, send to another
> >     destination for the association.
> >   If a route to IP4 exists, and the source address of the outbound
> >     interface of this route includes a local address for the
> >     association, use that as the source address when using=20
> the route.
> >     Otherwise, use the first source address of the association.
> >=20
> > This only results in IP1-IP3 and IP2-IP4 if the only route=20
> to IP3 is=20
> > from an interface with IP1 and the only route to IP4 is from an=20
> > interface with IP2.
> >=20
> >=20
> >>  =20
> >>For example, endpoint1 has two local IP addresses(IP1/IP2)=A3=AC and
> >>endpoint2 has two local IP addresses(IP3/IP4).
> >>
> >>if two endpoints' primary path isn't the same,that is endpoint1 use
> >>IP1-IP3 as the primary path, use IP2-IP4 as the second path;
> >>endpoint2 use IP3-IP2 as the primary path, use IP4-IP1 as=20
> the second=20
> >>path.
> >>
> >>These two endpoints can't  send data to each other successfully. =20
> >=20
> >=20
> > Yes, it is possible to set up your routing tables on two=20
> host so that=20
> > the cannot communicate.  This is even possible with TCP.
> >=20
> > If the problem is not merely routing table, I suggest you choose=20
> > another vendor or work with your existing vendor to correct the=20
> > deficiencies in their implementation.
> >=20
> >=20
> >>       =20
> >>
> >>
> >>>    2. Not sure about the SACK issue: You are currently allowed to
> >>>   send the SACK back to an addresses different from the source
> >>>   address of the corresponding DATA chunk. As far as I know
> >>>   it is only a SHOULD describing that you send the SACK back
> >>>   to the source address of the DATA chunk.
> >>
> >>You are right,it is only a SHOULD describing that you send the SACK=20
> >>back to the source address of the DATA chunk in RFC2960. =20
> That's why=20
> >>we get in trouble in multi-homing situation.  If the  path to the=20
> >>source address of the DATA chunk is unreachable=A3=ACthe sack=20
> can't send=20
> >>to the remote endpoint for ever although the other path is=20
> >>available.Soon the other path will be failure.
> >=20
> >=20
> > Well, no, not in the reasonable implementation.  When SACKs=20
> are being=20
> > sent to a destination and are not reaching the peer endpoint, a=20
> > retransmission timeout will result in duplicate TSNs being=20
> sent.  The=20
> > peer receiving duplicate TSNs should realized that their SACKs are=20
> > likely being sent into a black hole and begin sending SACKs to a=20
> > different destination.  This is already in RFC 2960:
> >=20
> > 6.4 Multi-homed SCTP Endpoints
> >=20
> >    ...
> >=20
> >    When a receiver of a duplicate DATA chunk sends a SACK=20
> to a multi-
> >    homed endpoint it MAY be beneficial to vary the=20
> destination address
> >    and not use the source address of the DATA chunk.  The=20
> reason being
> >    that receiving a duplicate from a multi-homed endpoint=20
> might indicate
> >    that the return path (as specified in the source address=20
> of the DATA
> >    chunk) for the SACK is broken.
> >=20
> >    ...
> >=20
> > If your current vendor does not implement this, I suggest that you=20
> > request them to do so.
> >=20
> > --brian
> >=20
>=20
>=20
> --
> Randall Stewart
> 803-345-0369 <or> 815-342-5222(cell)
>=20
>=20
>=20





From tsvwg-bounces@ietf.org Mon Jul 30 05:05:54 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFRCK-0002Vg-Qf; Mon, 30 Jul 2007 05:05:52 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IFRCI-0002VB-Np
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 30 Jul 2007 05:05:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFRCI-0002Uz-Ct
	for tsvwg@ietf.org; Mon, 30 Jul 2007 05:05:50 -0400
Received: from rv-out-0910.google.com ([209.85.198.187])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFRCI-00069L-0i
	for tsvwg@ietf.org; Mon, 30 Jul 2007 05:05:50 -0400
Received: by rv-out-0910.google.com with SMTP id f1so330732rvb
	for <tsvwg@ietf.org>; Mon, 30 Jul 2007 02:05:49 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type;
	b=nhqfTeLMlCh7AigB6SngRkWG3imZTTrlNbHNREqBJAIRi7lSphHqLZ303ZgStxRzemgL3PhJqQyiZv/2ONuLvOjuOR/YSumyjcIoJbCgH42RQ30lIle8+8bTjZ2Wxv6MUDxPPtzIUD3LGC9OGWZAKO8csPM/FrdfMaj2k/vhr8E=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:mime-version:content-type;
	b=A5/0N3NoGEPWwdwSn640FXqFMWOuAGPcm+sV6k3v6ZgHHstId0uh+hnj8vPCYgsubZfkjw3X77Oq23zCaZDyHkS2cOoFDgyxaqh+kTgr/+F65qAWQr7Dk4cyt+1Zki6tnD+UWKmxTFjkWTOl5b0uI82/9evDDwFcBuyYlhDf7nk=
Received: by 10.141.146.11 with SMTP id y11mr1768510rvn.1185786349119;
	Mon, 30 Jul 2007 02:05:49 -0700 (PDT)
Received: by 10.141.53.12 with HTTP; Mon, 30 Jul 2007 02:05:49 -0700 (PDT)
Message-ID: <296afac70707300205m152b4d15haa17ab5522a479c0@mail.gmail.com>
Date: Mon, 30 Jul 2007 13:05:49 +0400
From: "Andrey Konstantinov" <avkonst@gmail.com>
To: tsvwg@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_6221_24231701.1185786349084"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Subject: [Tsvwg] SCTP reaction on wrong behaviour from remote side.
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

------=_Part_6221_24231701.1185786349084
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

 Hi,

I have a question, because I can not find the answer in RFC 2960.

SCTP have installed association with remote side.
Reported Initiation Tag is 657476287 (in INIT ACK chunk),
First incoming DATA chunk from remote side has Transmission Sequence Number
657476287 and Stream Sequence Number: 4 (HAVE TO be equal to 0).
It is a fault from remote side, but how SCTP should respond on this on local
side?

We have applied (while) solution when SCTP sends ABORT chunk (reason:
protocol violation), but it is required much CPU time to detect this
situation. Should SCTP detect and check this situation/condition?
Without solution SCTP collects incoming data (does not provide this to SCTP
user) unless receiveSpace is null (after that zero probe state (arwnd =
0) reported to remote side according to RFC).

Could you explain right solution?

Best regards,
Andrey Konstantinov

------=_Part_6221_24231701.1185786349084
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>
<div>
<div>Hi,</div>
<div>&nbsp;</div>
<div>I have a question, because I can not find the answer&nbsp;in RFC 2960.</div>
<div>&nbsp;</div>
<div>SCTP have installed association with remote side.</div>
<div>Reported&nbsp;Initiation Tag is 657476287 (in INIT ACK chunk),</div>
<div>First incoming DATA chunk from remote side has Transmission Sequence Number 657476287 and&nbsp;Stream Sequence Number: 4 (HAVE TO be equal to 0).</div>
<div>It&nbsp;is a fault from remote side, but how SCTP should respond on this on local side?</div>
<div>&nbsp;</div>
<div>We have applied&nbsp;(while) solution when SCTP sends ABORT chunk (reason: protocol violation), but it is required much CPU time to detect this situation. Should SCTP detect and check this situation/condition?</div>
<div>Without solution SCTP collects incoming data (does not provide this to SCTP user)&nbsp;unless receiveSpace is null (after that zero probe state (arwnd = 0)&nbsp;reported to remote side&nbsp;according to RFC).</div>
<div>&nbsp;</div>
<div>Could you explain right solution?</div>
<div>&nbsp;</div>
<div>Best regards,</div><span>
<div>Andrey Konstantinov</div></span></div></div>

------=_Part_6221_24231701.1185786349084--





From tsvwg-bounces@ietf.org Mon Jul 30 05:40:06 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFRjQ-0003fx-4K; Mon, 30 Jul 2007 05:40:04 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IFRjN-0003fo-JN
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 30 Jul 2007 05:40:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFRjN-0003fg-9q
	for tsvwg@ietf.org; Mon, 30 Jul 2007 05:40:01 -0400
Received: from drew.ipv6.franken.de ([2001:638:a02:a001:20e:cff:fe4a:feaa]
	helo=mail-n.franken.de) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IFRjM-00070P-Pt
	for tsvwg@ietf.org; Mon, 30 Jul 2007 05:40:01 -0400
Received: from [192.168.1.5] (p508FD457.dip.t-dialin.net [80.143.212.87])
	by mail-n.franken.de (Postfix) with ESMTP id 666A28006DB5;
	Mon, 30 Jul 2007 11:39:57 +0200 (CEST)
	(KNF-authenticated sender: lurchi)
In-Reply-To: <296afac70707300205m152b4d15haa17ab5522a479c0@mail.gmail.com>
References: <296afac70707300205m152b4d15haa17ab5522a479c0@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <B8279FE2-E862-4E06-A7BC-F2EA905F09AF@lurchi.franken.de>
Content-Transfer-Encoding: 7bit
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Tsvwg] SCTP reaction on wrong behaviour from remote side.
Date: Mon, 30 Jul 2007 11:39:54 +0200
To: "Andrey Konstantinov" <avkonst@gmail.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 2.2 (++)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi Andrey,

I think an SCTP implementation should check for this and send
an ABORT with error cause 'Protocol Violation'. It may take some
CPU time to handle this, but your other solution would take
memory on your side for an indefinite amount of time...

Best regards
Michael

On Jul 30, 2007, at 11:05 AM, Andrey Konstantinov wrote:

> Hi,
>
> I have a question, because I can not find the answer in RFC 2960.
>
> SCTP have installed association with remote side.
> Reported Initiation Tag is 657476287 (in INIT ACK chunk),
> First incoming DATA chunk from remote side has Transmission  
> Sequence Number 657476287 and Stream Sequence Number: 4 (HAVE TO be  
> equal to 0).
> It is a fault from remote side, but how SCTP should respond on this  
> on local side?
>
> We have applied (while) solution when SCTP sends ABORT chunk  
> (reason: protocol violation), but it is required much CPU time to  
> detect this situation. Should SCTP detect and check this situation/ 
> condition?
> Without solution SCTP collects incoming data (does not provide this  
> to SCTP user) unless receiveSpace is null (after that zero probe  
> state (arwnd = 0) reported to remote side according to RFC).
>
> Could you explain right solution?
>
> Best regards,
> Andrey Konstantinov






From tsvwg-bounces@ietf.org Mon Jul 30 05:57:33 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFRzu-0004H7-Aw; Mon, 30 Jul 2007 05:57:06 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IFRzs-0004Gm-3j
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 30 Jul 2007 05:57:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFRzr-0004GP-QF
	for tsvwg@ietf.org; Mon, 30 Jul 2007 05:57:03 -0400
Received: from exprod7og51.obsmtp.com ([64.18.2.157])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFRzr-0007m9-Ak
	for tsvwg@ietf.org; Mon, 30 Jul 2007 05:57:03 -0400
Received: from source ([67.96.16.11]) (using TLSv1) by exprod7ob51.obsmtp.com
	([64.18.6.12]) with SMTP; Mon, 30 Jul 2007 02:56:54 PDT
Received: from ETSMSG-CINAV06.etsmsg.org ([65.90.82.49]) by
	naout-cinexs01.nasmtpout.emrsn.com with Microsoft
	SMTPSVC(6.0.3790.3959); Mon, 30 Jul 2007 06:08:38 -0400
Received: from etsmsg-cinexs03.etsmsg.org ([65.90.82.49]) by
	ETSMSG-CINAV06.etsmsg.org with InterScan Message Security Suite;
	Mon, 30 Jul 2007 05:56:53 -0400
Received: from ETSMSG-CINEXS01.etsmsg.org ([65.90.82.81]) by
	etsmsg-cinexs03.etsmsg.org with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 30 Jul 2007 05:56:53 -0400
Received: from ant.artesyncp.com ([65.90.82.49]) by ETSMSG-CINEXS01.etsmsg.org
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 30 Jul 2007 05:56:52 -0400
Received: from stephane by ant.artesyncp.com with local (Exim 4.67)
	(envelope-from <stephane@artesyncp.com>)
	id 1IFRzf-0006Qd-Om; Mon, 30 Jul 2007 10:56:51 +0100
Date: Mon, 30 Jul 2007 10:56:51 +0100
From: Stephane Chazelas <stephane@artesyncp.com>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Tsvwg] SCTP reaction on wrong behaviour from remote side.
Message-ID: <20070730095651.GN27950@artesyncp.com>
References: <296afac70707300205m152b4d15haa17ab5522a479c0@mail.gmail.com>
	<B8279FE2-E862-4E06-A7BC-F2EA905F09AF@lurchi.franken.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <B8279FE2-E862-4E06-A7BC-F2EA905F09AF@lurchi.franken.de>
User-Agent: mutt-ng/devel-r562 (Linux)
X-OriginalArrivalTime: 30 Jul 2007 09:56:53.0158 (UTC)
	FILETIME=[F4BDBC60:01C7D28F]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: Andrey Konstantinov <avkonst@gmail.com>, tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

On Mon, Jul 30, 2007 at 11:39:54AM +0200, Michael Tuexen wrote:
> Hi Andrey,
> 
> I think an SCTP implementation should check for this and send
> an ABORT with error cause 'Protocol Violation'. It may take some
> CPU time to handle this, but your other solution would take
> memory on your side for an indefinite amount of time...

Hi Andrey, Michael,

why is it so bad and why should a stack care that the ssn
doesn't start with 0. I thought that to insure in sequence
delivery, looking at TSNs (and B,E,U bits) should be enough. Why
would you wait for SSNs 0, 1, 2, 3 here? Is a stack allowed to
send ssn 4 before ssn 3 (that is with a lower TSN in the chunks
of ssn 4 than in ssn 3)?

> >I have a question, because I can not find the answer in RFC 2960.
> >
> >SCTP have installed association with remote side.
> >Reported Initiation Tag is 657476287 (in INIT ACK chunk),
> >First incoming DATA chunk from remote side has Transmission Sequence Number 657476287 and Stream Sequence Number: 4 (HAVE TO be equal to 0).
> >It is a fault from remote side, but how SCTP should respond on this on local side?
> >
> >We have applied (while) solution when SCTP sends ABORT chunk (reason: protocol violation), but it is required much CPU time to detect this situation. Should SCTP detect and check 
> >this situation/condition?
> >Without solution SCTP collects incoming data (does not provide this to SCTP user) unless receiveSpace is null (after that zero probe state (arwnd = 0) reported to remote side 
> >according to RFC).

Cheers,
Stephane





From tsvwg-bounces@ietf.org Mon Jul 30 10:40:33 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFWPj-0006zk-EP; Mon, 30 Jul 2007 10:40:04 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IFWPh-0006zb-UP
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 30 Jul 2007 10:40:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFWPh-0006zT-Kn; Mon, 30 Jul 2007 10:40:01 -0400
Received: from gw.openss7.com ([142.179.199.224])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IFWPg-00085x-1y; Mon, 30 Jul 2007 10:40:01 -0400
Received: from ns.pigworks.openss7.net
	(IDENT:C4UctZnQOkh407xRrR4aJZ+5QBaGQ9Va@ns1.evil.openss7.net
	[192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id l6UEdwM27862;
	Mon, 30 Jul 2007 08:39:58 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id l6UEdum23866;
	Mon, 30 Jul 2007 08:39:56 -0600
Date: Mon, 30 Jul 2007 08:39:56 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ronnie@artesyncp.com
Subject: Re: [Tsvwg] Re: [Sigtran] The
	requiremntsand	proposalsforM2PA/M3UA/SCTPExtension from China Mobile
Message-ID: <20070730083956.A21182@openss7.org>
Mail-Followup-To: ronnie@artesyncp.com, randall@lakerest.net,
	chenxu@chinamobile.com, Michael.Tuexen@lurchi.franken.de,
	sigtran@ietf.org, tsvwg@ietf.org
References: <46AB1D7B.6040404@lakerest.net>
	<DB255B459C0A1C458EB2D2353F1269CB03000D7E@USACG-MSNEXM01.astec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <DB255B459C0A1C458EB2D2353F1269CB03000D7E@USACG-MSNEXM01.astec.com>;
	from ronnie@artesyncp.com on Mon, Jul 30, 2007 at 04:02:25AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: chenxu@chinamobile.com, sigtran@ietf.org, tsvwg@ietf.org,
	randall@lakerest.net, Michael.Tuexen@lurchi.franken.de
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bidulock@openss7.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Ronnie,

That's interesting.  I don't actually do that.  I send the HEARTBEAT-ACK
to the Source IP in the HEARTBEAT, provided that I have a usable route to
that address, I have no retransmissions that were originally sent to
that address outstanding, and I have not received duplicate TSNs when
SACKs were sent to that destination.  Otherwise, I send them to the
current primary.

--brian

ronnie@artesyncp.com wrote:                    (Mon, 30 Jul 2007 04:02:25)
> Hi,
> 
> Won't this association have a serious problem with Heartbeats if you
> cannot send a Heartbeat Ack to the address the Heartbeat came from?
> 
> >From RFC 2960bis
> 	3.3.6. Heartbeat Acknowledgement (HEARTBEAT ACK) (5): 
> 
> 	An endpoint should send this chunk to its peer endpoint as a
> response to a 	HEARTBEAT chunk (see Section 8.3). A HEARTBEAT
> ACK is always sent to the source IP 	address of the IP datagram
> containing the HEARTBEAT chunk to which this ack is responding.
> 
> We also need to take into account that the source address of duplicate
> data may NOT be the source address used for the original data if the
> sending end has changed paths when the data wasn't acked.
> 
> If this is a routing problem which has been in place since the
> association was started then the sender should never send data to an
> unconfirmed address.  If the Heartbeat mechanism is broken the address
> will never be confirmed.
> 
> Ronnie
> ---
> Ronnie Sellar			Emerson Network Power, Embedded Computing
> Tel: +44 131 475 7015		Suite 4, 2 Anderson Place
> Fax: +44 131 475 7001		Edinburgh EH6 5NP
> mailto:ronnie@artesyncp.com	http://www.emersonembeddedcomputing.com
>  

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/





From tsvwg-bounces@ietf.org Mon Jul 30 10:48:23 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFWXm-0003IO-SQ; Mon, 30 Jul 2007 10:48:22 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IFWXl-0003IC-90
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 30 Jul 2007 10:48:21 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFWXk-0003I4-VB
	for tsvwg@ietf.org; Mon, 30 Jul 2007 10:48:20 -0400
Received: from gw.openss7.com ([142.179.199.224])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IFWXk-00077w-Di
	for tsvwg@ietf.org; Mon, 30 Jul 2007 10:48:20 -0400
Received: from ns.pigworks.openss7.net
	(IDENT:SmljAx7q1OG7HQmFJsyxqIIPlgostPpR@ns1.evil.openss7.net
	[192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id l6UEmHM28167;
	Mon, 30 Jul 2007 08:48:17 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id l6UEmHG24009;
	Mon, 30 Jul 2007 08:48:17 -0600
Date: Mon, 30 Jul 2007 08:48:17 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Stephane Chazelas <stephane@artesyncp.com>
Subject: Re: [Tsvwg] SCTP reaction on wrong behaviour from remote side.
Message-ID: <20070730084817.B21182@openss7.org>
Mail-Followup-To: Stephane Chazelas <stephane@artesyncp.com>,
	Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
	Andrey Konstantinov <avkonst@gmail.com>, tsvwg@ietf.org
References: <296afac70707300205m152b4d15haa17ab5522a479c0@mail.gmail.com>
	<B8279FE2-E862-4E06-A7BC-F2EA905F09AF@lurchi.franken.de>
	<20070730095651.GN27950@artesyncp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20070730095651.GN27950@artesyncp.com>;
	from stephane@artesyncp.com on Mon, Jul 30, 2007 at 10:56:51AM
	+0100
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,
	Andrey Konstantinov <avkonst@gmail.com>, tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bidulock@openss7.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Stephane,

Stephane Chazelas wrote:                                          (Mon, 30 Jul 2007 10:56:51)
> On Mon, Jul 30, 2007 at 11:39:54AM +0200, Michael Tuexen wrote:
> > Hi Andrey,
> > 
> > I think an SCTP implementation should check for this and send
> > an ABORT with error cause 'Protocol Violation'. It may take some
> > CPU time to handle this, but your other solution would take
> > memory on your side for an indefinite amount of time...
> 
> Hi Andrey, Michael,
> 
> why is it so bad and why should a stack care that the ssn
> doesn't start with 0. I thought that to insure in sequence
> delivery, looking at TSNs (and B,E,U bits) should be enough. Why
> would you wait for SSNs 0, 1, 2, 3 here? Is a stack allowed to
> send ssn 4 before ssn 3 (that is with a lower TSN in the chunks
> of ssn 4 than in ssn 3)?

It does not make sense to do so in the first TSN sent.

--brian

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/





From tsvwg-bounces@ietf.org Mon Jul 30 11:39:44 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFXLQ-00052Y-FC; Mon, 30 Jul 2007 11:39:40 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IFXLP-00052G-Gb
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 30 Jul 2007 11:39:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFXLP-000527-74
	for tsvwg@ietf.org; Mon, 30 Jul 2007 11:39:39 -0400
Received: from drew.ipv6.franken.de ([2001:638:a02:a001:20e:cff:fe4a:feaa]
	helo=mail-n.franken.de) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IFXLN-0000v0-SH
	for tsvwg@ietf.org; Mon, 30 Jul 2007 11:39:39 -0400
Received: from [192.168.1.17] (p508FD457.dip.t-dialin.net [80.143.212.87])
	by mail-n.franken.de (Postfix) with ESMTP id 65CEF8006DB8;
	Mon, 30 Jul 2007 17:39:36 +0200 (CEST)
	(KNF-authenticated sender: macmic)
In-Reply-To: <20070730095651.GN27950@artesyncp.com>
References: <296afac70707300205m152b4d15haa17ab5522a479c0@mail.gmail.com>
	<B8279FE2-E862-4E06-A7BC-F2EA905F09AF@lurchi.franken.de>
	<20070730095651.GN27950@artesyncp.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <AA8090A4-4E6A-4611-8351-D37A03BAA265@lurchi.franken.de>
Content-Transfer-Encoding: 7bit
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Tsvwg] SCTP reaction on wrong behaviour from remote side.
Date: Mon, 30 Jul 2007 17:39:34 +0200
To: Stephane Chazelas <stephane@artesyncp.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 2.2 (++)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: Andrey Konstantinov <avkonst@gmail.com>, tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi Stephane,

you must know where your sequence numbers start to identify
the first message.

Assume that you do not know where the SSN starts, and you
are missing the first TSN, then you are not able to deliver
any message on any stream, because you do not know for
which message you have to waiting.

The initial value for the TSNs is negotiated during the
association setup, the initial value for the SSN is
defined by the protocol specification as 0.

Best regards
Michael


On Jul 30, 2007, at 11:56 AM, Stephane Chazelas wrote:

> On Mon, Jul 30, 2007 at 11:39:54AM +0200, Michael Tuexen wrote:
>> Hi Andrey,
>>
>> I think an SCTP implementation should check for this and send
>> an ABORT with error cause 'Protocol Violation'. It may take some
>> CPU time to handle this, but your other solution would take
>> memory on your side for an indefinite amount of time...
>
> Hi Andrey, Michael,
>
> why is it so bad and why should a stack care that the ssn
> doesn't start with 0. I thought that to insure in sequence
> delivery, looking at TSNs (and B,E,U bits) should be enough. Why
> would you wait for SSNs 0, 1, 2, 3 here? Is a stack allowed to
> send ssn 4 before ssn 3 (that is with a lower TSN in the chunks
> of ssn 4 than in ssn 3)?
>
>>> I have a question, because I can not find the answer in RFC 2960.
>>>
>>> SCTP have installed association with remote side.
>>> Reported Initiation Tag is 657476287 (in INIT ACK chunk),
>>> First incoming DATA chunk from remote side has Transmission  
>>> Sequence Number 657476287 and Stream Sequence Number: 4 (HAVE TO  
>>> be equal to 0).
>>> It is a fault from remote side, but how SCTP should respond on  
>>> this on local side?
>>>
>>> We have applied (while) solution when SCTP sends ABORT chunk  
>>> (reason: protocol violation), but it is required much CPU time to  
>>> detect this situation. Should SCTP detect and check
>>> this situation/condition?
>>> Without solution SCTP collects incoming data (does not provide  
>>> this to SCTP user) unless receiveSpace is null (after that zero  
>>> probe state (arwnd = 0) reported to remote side
>>> according to RFC).
>
> Cheers,
> Stephane
>
>
>






From tsvwg-bounces@ietf.org Mon Jul 30 11:56:10 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFXaq-0004Uz-Ab; Mon, 30 Jul 2007 11:55:36 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IFXap-0004TY-7m
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 30 Jul 2007 11:55:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFXao-0004Sx-S7
	for tsvwg@ietf.org; Mon, 30 Jul 2007 11:55:34 -0400
Received: from exprod7og54.obsmtp.com ([64.18.2.163])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFXan-0001Ed-Ij
	for tsvwg@ietf.org; Mon, 30 Jul 2007 11:55:34 -0400
Received: from source ([67.96.16.12]) (using TLSv1) by exprod7ob54.obsmtp.com
	([64.18.6.12]) with SMTP; Mon, 30 Jul 2007 08:55:24 PDT
Received: from ETSMSG-CINAV01.etsmsg.org ([65.90.82.49]) by
	naout-cinexs02.nasmtpout.emrsn.com with Microsoft
	SMTPSVC(6.0.3790.3959); Mon, 30 Jul 2007 12:07:08 -0400
Received: from etsmsg-cinexs03.etsmsg.org ([65.90.82.49]) by
	ETSMSG-CINAV01.etsmsg.org with InterScan Message Security Suite;
	Mon, 30 Jul 2007 11:55:24 -0400
Received: from ETSMSG-CINEXS01.etsmsg.org ([65.90.82.81]) by
	etsmsg-cinexs03.etsmsg.org with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 30 Jul 2007 11:55:22 -0400
Received: from ant.artesyncp.com ([65.90.82.49]) by ETSMSG-CINEXS01.etsmsg.org
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 30 Jul 2007 11:55:19 -0400
Received: from stephane by ant.artesyncp.com with local (Exim 4.67)
	(envelope-from <stephane@artesyncp.com>)
	id 1IFXaY-00084z-M4; Mon, 30 Jul 2007 16:55:18 +0100
Date: Mon, 30 Jul 2007 16:55:18 +0100
From: Stephane Chazelas <stephane@artesyncp.com>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Tsvwg] SCTP reaction on wrong behaviour from remote side.
Message-ID: <20070730155518.GT27950@artesyncp.com>
References: <296afac70707300205m152b4d15haa17ab5522a479c0@mail.gmail.com>
	<B8279FE2-E862-4E06-A7BC-F2EA905F09AF@lurchi.franken.de>
	<20070730095651.GN27950@artesyncp.com>
	<AA8090A4-4E6A-4611-8351-D37A03BAA265@lurchi.franken.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <AA8090A4-4E6A-4611-8351-D37A03BAA265@lurchi.franken.de>
User-Agent: mutt-ng/devel-r562 (Linux)
X-OriginalArrivalTime: 30 Jul 2007 15:55:19.0853 (UTC)
	FILETIME=[07BAF5D0:01C7D2C2]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: Andrey Konstantinov <avkonst@gmail.com>, tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

On Mon, Jul 30, 2007 at 05:39:34PM +0200, Michael Tuexen wrote:
[...]
> you must know where your sequence numbers start to identify
> the first message.
> 
> Assume that you do not know where the SSN starts, and you
> are missing the first TSN, then you are not able to deliver
> any message on any stream, because you do not know for
> which message you have to waiting.
[...]

Thanks, yes, of course, that makes sense.

However, if one sends its first tsn with a non-zero ssn, then
it's broken, same if one sends tsn x with ssn y and tsn x+1 with
ssn y+2, I don't think there's a point in checking that as that
won't happen in real life, and if it does happen, aborting the
association is yes smarter than hanging it with a full window
but the end result will be the same: the peer stack needs to be
fixed.

And if one wants to fill up a receive window in some DOS
attempt, then there are plenty of other ways to do it, so why
bother avoiding this one?

Cheers,
Stephane





From tsvwg-bounces@ietf.org Mon Jul 30 12:26:10 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFY4H-00050j-So; Mon, 30 Jul 2007 12:26:01 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IFY4G-0004yn-Fz
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 30 Jul 2007 12:26:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFY4G-0004yf-6X
	for tsvwg@ietf.org; Mon, 30 Jul 2007 12:26:00 -0400
Received: from drew.ipv6.franken.de ([2001:638:a02:a001:20e:cff:fe4a:feaa]
	helo=mail-n.franken.de) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IFY4E-0001un-Sl
	for tsvwg@ietf.org; Mon, 30 Jul 2007 12:26:00 -0400
Received: from [192.168.1.17] (p508FD457.dip.t-dialin.net [80.143.212.87])
	by mail-n.franken.de (Postfix) with ESMTP id CF6448006DB5;
	Mon, 30 Jul 2007 18:25:57 +0200 (CEST)
	(KNF-authenticated sender: macmic)
In-Reply-To: <20070730155518.GT27950@artesyncp.com>
References: <296afac70707300205m152b4d15haa17ab5522a479c0@mail.gmail.com>
	<B8279FE2-E862-4E06-A7BC-F2EA905F09AF@lurchi.franken.de>
	<20070730095651.GN27950@artesyncp.com>
	<AA8090A4-4E6A-4611-8351-D37A03BAA265@lurchi.franken.de>
	<20070730155518.GT27950@artesyncp.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <E18FA029-DF62-4235-9692-90427526D80E@lurchi.franken.de>
Content-Transfer-Encoding: 7bit
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Tsvwg] SCTP reaction on wrong behaviour from remote side.
Date: Mon, 30 Jul 2007 18:25:55 +0200
To: Stephane Chazelas <stephane@artesyncp.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 2.2 (++)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: Andrey Konstantinov <avkonst@gmail.com>, tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi Stephane,

comments in-line.

Best regards
Michael

On Jul 30, 2007, at 5:55 PM, Stephane Chazelas wrote:

> On Mon, Jul 30, 2007 at 05:39:34PM +0200, Michael Tuexen wrote:
> [...]
>> you must know where your sequence numbers start to identify
>> the first message.
>>
>> Assume that you do not know where the SSN starts, and you
>> are missing the first TSN, then you are not able to deliver
>> any message on any stream, because you do not know for
>> which message you have to waiting.
> [...]
>
> Thanks, yes, of course, that makes sense.
>
> However, if one sends its first tsn with a non-zero ssn, then
> it's broken, same if one sends tsn x with ssn y and tsn x+1 with
> ssn y+2, I don't think there's a point in checking that as that
> won't happen in real life, and if it does happen, aborting the
> association is yes smarter than hanging it with a full window
> but the end result will be the same: the peer stack needs to be
> fixed.
I agree, the peer stack needs to be fixed.
>
> And if one wants to fill up a receive window in some DOS
> attempt, then there are plenty of other ways to do it, so why
> bother avoiding this one?
There are two points here:
1. I guess that the peer stack will not figure out that
    it has a problem. The local stack can figure that out.
    So I think the best behaviour is to abort the association.
    The only alternative would be to let the association
    stay forever, if the the application layer does not
    resolve it or to wait until the application layer aborts
    the association.
2. Yes there are plenty of ways for a malicious attacker
    but I think the best way to handle this is to abort
    the association as soon as you figured out that you
    peer is an attacker.
>
> Cheers,
> Stephane
>
>
>






From tsvwg-bounces@ietf.org Mon Jul 30 13:31:43 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFZ5m-00065j-Tj; Mon, 30 Jul 2007 13:31:38 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IFZ5l-00065Y-4G
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 30 Jul 2007 13:31:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFZ5k-00065P-Qp
	for tsvwg@ietf.org; Mon, 30 Jul 2007 13:31:36 -0400
Received: from smtp4.smtp.bt.com ([217.32.164.151])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFZ5j-0003xg-73
	for tsvwg@ietf.org; Mon, 30 Jul 2007 13:31:36 -0400
Received: from i2kc08-ukbr.domain1.systemhost.net ([193.113.197.71]) by
	smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 30 Jul 2007 18:31:34 +0100
Received: from cbibipnt08.iuser.iroot.adidom.com ([147.149.100.81]) by
	i2kc08-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(6.0.3790.1830); Mon, 30 Jul 2007 18:31:34 +0100
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by
	cbibipnt08.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a
	P0803.399); id 1185816692701; Mon, 30 Jul 2007 18:31:32 +0100
Received: from mut.jungle.bt.co.uk ([10.215.130.87])
	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id
	l6UHVQhg031497; Mon, 30 Jul 2007 18:31:32 +0100
Message-Id: <5.2.1.1.2.20070730181738.04a1c4b8@pop3.jungle.bt.co.uk>
X-Sender: rbriscoe@pop3.jungle.bt.co.uk
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Mon, 30 Jul 2007 18:31:43 +0100
To: dpapadimitriou@psg.com, dimitri.papadimitriou@alcatel-lucent.be
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
Subject: Re: [Tsvwg] Re: terminology issues in
	draft-floyd-tsvwg-besteffort - flat monthly pricing
In-Reply-To: <46A96502.1070901@psg.com>
References: <5.2.1.1.2.20070726141117.04e7a828@pop3.jungle.bt.co.uk>
	<5.2.1.1.2.20070726141117.04e7a828@pop3.jungle.bt.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: -1.36 () ALL_TRUSTED
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 30 Jul 2007 17:31:34.0082 (UTC)
	FILETIME=[79706220:01C7D2CF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593
Cc: tsvwg IETF list <tsvwg@ietf.org>, Mark Allman <mallman@icir.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Dimitri,

At 04:22 27/07/2007, dimitri papadimitriou wrote:
>bob
>
>you wrote:
>
>"so there won't be sufficient incentives for anyone to invest in more 
>capacity for those of us who want to use the Internet responsibly."
>
>this might be indeed a concern
>
>but as shorter life socialist ;-) i do also strongly believe that before 
>discussing the solution space we should first within the IETF community at 
>large come with a good, clear, and common understanding whether this is a 
>concern or not, if this is the case how important & urgent it might be, 
>have better understanding about of some of the root causes, etc.

I've been working in non-IETF fora where that issue has been debated for 
some years. That would be difficult for the IETF to do. It's difficult for 
economists to come to any conclusion on that issue. Partly because it gets 
convolved with monopoly issues in access networks.

But in my view, the problem is a lot more basic - in the current Internet 
architecture there isn't even the basics of a mechanism to support resource 
allocation: accountability. That sounds like billing, but that's not what I 
mean. I mean being able to attribute a cost to a user or network 
(irrespective of what you do with the information).

It would be equivalent to a supermarket not being able to tell who had 
taken stuff off the shelves. I think most economists would agree that lack 
of accountability removes most incentives to invest if demand doesn't 
easily satiate (e.g. a provider has the incentive to keep investing in 
supplying all-you-can-eat buffet to people with limited stomach capacity, 
but if faced with a range of customers with huge stomachs, they tend to 
find other ways to limit demand - e.g. one plate each).


Bob


>-d.
>
>Bob Briscoe wrote:
>>Sally,
>>I just realised that I should have added a very important point about 
>>"who controls the choice" to the rather philosophical response below.
>>I'm trying to make sure we at the IETF don't have to decide whether the 
>>Internet more favours rich people, malicious people or selfish people. 
>>I'm trying to make it so what you think or what I think about this 
>>doesn't matter (at least any more than what everyone else in the world thinks).
>>Firstly, what I'm proposing would sit alongside the current Internet 
>>(re-ECN packets are distinguishable from non-re-ECN packets, so they 
>>effectively partition all traffic orthogonally to Diffserv).
>>Secondly, one partition would be the current Internet, with all its 
>>vulnerabilites to selfish and malicious users as well as all its 
>>strengths. The other partition would be this new proposal where the 
>>market and social governance can control the way the Internet shares out 
>>resources.
>>At a grander level, the choice of how much resource each of the two 
>>partitions gets would be under the direct control of ISPs, but in turn 
>>their choices are also affected by the market and perhaps by social 
>>control through government regulation.
>>I know this fits your preferred model of how new resource allocation 
>>strategies should be added to the Internet. The question is whether it is 
>>sufficiently important to use IP header space to provide this choice. We 
>>don't need to decide that now, but we do need to debate it widely - more 
>>widely than tsvwg.
>>
>>Bob
>>At 18:16 24/07/2007, Sally Floyd wrote:
>>>>3/ User pricing: Flat monthly (in our simplest effective proposal).
>>>>
>>>>Please don't imply we're advocating user congestion pricing, given the 
>>>>whole reason we brought re-ECN to the IETF back in 2005 was because we 
>>>>found a way to limit congestion without constraining how operators 
>>>>price their services to their customers. Specifically, re-ECN is 
>>>>designed to work with flat monthly pricing.
>>>
>>>This draft is not about re-ECN.  It is about the usefulness of
>>>"simple best-effort traffic", and the usefulness of flow-rate fairness
>>>for simple best-effort traffic.
>>>
>>>This draft is not about the presence or absence of flat monthly
>>>pricing for users.  One could have flat monthly pricing with no
>>>other limitations, one could have flat monthly pricing with volume
>>>limits, or one could have flat monthly pricing with some form of
>>>"you get what you pay for".  The first two forms don't result in
>>>"rich" users getting all of the bandwidth in times of high congestion
>>>(e.g., after the earthquake).  The third form easily could.  E.g.,
>>>if all of the traffic was "you get what you pay for", even with
>>>flat monthly fees, then it could be really expensive to send packets
>>>in the time interval after the earthquake, or some other highly-congested
>>>period, and only the rich would be able to send packets.  I would
>>>be opposed to setting such a "you get what you pay for" goal as the
>>>overriding goal for the global Internet, with or without flat monthly
>>>fees.
>>I know. It's distasteful to me to (I am a life-long socialist). But the 
>>alternatives are worse. I have thought about this long and hard.
>>On the demand side: If the rich don't get to be able to buy the right to 
>>use capacity, the alternative is that the malicious and selfish get to 
>>drive out those trying to be sociable in their use of the Internet. And 
>>that's for always, not just during earthquakes. Also, the lack of any 
>>resource sharing arbitration will lead to a vacuum that will be filled by 
>>the rich and powerful (which is what deep packet inspection represents - 
>>those with power and influence controlling what can and can't be done on 
>>the Internet).
>>On the supply side: The malicious and selfish will use the Internet 
>>excessively, but not pay their share, so there won't be sufficient 
>>incentives for anyone to invest in more capacity for those of us who want 
>>to use the Internet responsibly.
>>In summary, a knee-jerk reaction against a market mechanism needs to be 
>>tempered by the thought of what will otherwise fill the vacuum - the 
>>lesson of the Soviet Union?
>>However, you will notice in my draft on fairness (and in my design of 
>>re-ECN) that I have been careful to enable more equitable resource 
>>allocation schemes locally. This can give _true_ equality, whereas flow 
>>rate equality is just a license for the selfish and malicious to take 
>>what they want.
>>Overall, I put my hands up and admit it: we don't have a better system 
>>for allocating resources on planet scale than a market. I wish we did. We 
>>do have better resource sharing capabilities locally though, and I want 
>>to enable them.
>>
>>Bob
>>
>>>- Sally
>>>http://www.icir.org/floyd/
>>____________________________________________________________________________
>>Notice: This contribution is the personal view of the author and does not 
>>necessarily reflect the technical nor commercial direction of BT plc.
>>____________________________________________________________________________
>>Bob Briscoe,                           Networks Research Centre, BT Research
>>B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 645196
>>
>>.
>
>____________________________________________________________________________
>Bob Briscoe, <bob.briscoe@bt.com>      Networks Research Centre, BT Research
>B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 645196 







From tsvwg-bounces@ietf.org Mon Jul 30 17:27:54 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFcmI-0003o8-Is; Mon, 30 Jul 2007 17:27:46 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IFcmH-0003jK-4I
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 30 Jul 2007 17:27:45 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFcmG-0003hW-Ka
	for tsvwg@ietf.org; Mon, 30 Jul 2007 17:27:44 -0400
Received: from smtp1.xmundo.net ([201.216.232.80])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IFcmG-00026i-5n
	for tsvwg@ietf.org; Mon, 30 Jul 2007 17:27:44 -0400
Received: from venus.xmundo.net (venus.xmundo.net [201.216.232.56])
	by smtp1.xmundo.net (Postfix) with ESMTP id 45668F0C461;
	Mon, 30 Jul 2007 18:27:13 -0300 (ART)
Received: from fgont.gont.com.ar (200.61.43.18.static.telmex.net.ar
	[200.61.43.18] (may be forged)) (authenticated bits=0)
	by venus.xmundo.net (8.13.8/8.13.8) with ESMTP id l6ULQopi029773;
	Mon, 30 Jul 2007 18:27:05 -0300
Message-Id: <7.0.1.0.0.20070730031659.077fe0c0@gont.com.ar>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Mon, 30 Jul 2007 03:19:53 -0300
To: "Anantha Ramaiah \(ananth\)" <ananth@cisco.com>,
	"Caitlin Bestler" <cait@asomi.com>
From: Fernando Gont <fernando@gont.com.ar>
Subject: RE: [Tsvwg] Re: [tcpm] Revision
	ofdraft-larsen-tsvwg-port-randomization
In-Reply-To: <0C53DCFB700D144284A584F54711EC5803B6C65A@xmb-sjc-21c.amer.
	cisco.com>
References: <13DAF96D-70E1-411E-9408-130A33987671@asomi.com>
	<0C53DCFB700D144284A584F54711EC5803B6C65A@xmb-sjc-21c.amer.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by
	milter-greylist-2.0.2 (venus.xmundo.net [201.216.232.56]);
	Mon, 30 Jul 2007 18:27:13 -0300 (ART)
X-Spam-Score: 1.8 (+)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: Murari Sridharan <muraris@microsoft.com>, tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

At 12:37 26/07/2007, Anantha Ramaiah \(ananth\) wrote:

>OTOH, adding more TCP option space should not be treated as a radical
>change to TCP. Also the original email and the draft reference was more
>about doing some things (like port randomization) which would help
>increase the robustness of a some protocols, including TCP.

Exactly. What we propose is a local policy for selecting ephemeral 
ports. We do not propose any change to the syntax or semantics of any 
TCP field.

The policies we propose can be deployed incrementally, and aome of 
them already ship with a number of operating systems (including 
Linux, FreeBSD, and OpenBSD).

Kindest regards,

--
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1








From tsvwg-bounces@ietf.org Mon Jul 30 17:27:54 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFcmL-0003rG-6F; Mon, 30 Jul 2007 17:27:49 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IFcmJ-0003q6-6L
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 30 Jul 2007 17:27:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFcmI-0003pu-Qq
	for tsvwg@ietf.org; Mon, 30 Jul 2007 17:27:46 -0400
Received: from smtp1.xmundo.net ([201.216.232.80])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFcmH-0001kh-Gf
	for tsvwg@ietf.org; Mon, 30 Jul 2007 17:27:46 -0400
Received: from venus.xmundo.net (venus.xmundo.net [201.216.232.56])
	by smtp1.xmundo.net (Postfix) with ESMTP id F0AF7F0C478;
	Mon, 30 Jul 2007 18:27:21 -0300 (ART)
Received: from fgont.gont.com.ar (200.61.43.18.static.telmex.net.ar
	[200.61.43.18] (may be forged)) (authenticated bits=0)
	by venus.xmundo.net (8.13.8/8.13.8) with ESMTP id l6ULQopk029773;
	Mon, 30 Jul 2007 18:27:14 -0300
Message-Id: <7.0.1.0.0.20070730032039.07729738@gont.com.ar>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Mon, 30 Jul 2007 03:25:41 -0300
To: Murari Sridharan <muraris@microsoft.com>,
	Lars Eggert <lars.eggert@nokia.com>,
	"ext Anantha Ramaiah (ananth)" <ananth@cisco.com>
From: Fernando Gont <fernando@gont.com.ar>
Subject: RE: [Tsvwg] Re: [tcpm] Revision
	ofdraft-larsen-tsvwg-port-randomization
In-Reply-To: <FCA794787FDE0D4DBE9FFA11053ECEB60C26A16230@NA-EXMSG-C110.r
	edmond.corp.microsoft.com>
References: <0C53DCFB700D144284A584F54711EC5803B6C65A@xmb-sjc-21c.amer.cisco.com>
	<EE1A9283-BF50-43C9-8308-37ECF1B60363@nokia.com>
	<FCA794787FDE0D4DBE9FFA11053ECEB60C26A16230@NA-EXMSG-C110.redmond.corp.microsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by
	milter-greylist-2.0.2 (venus.xmundo.net [201.216.232.56]);
	Mon, 30 Jul 2007 18:27:21 -0300 (ART)
X-Spam-Score: 1.8 (+)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: Caitlin Bestler <cait@asomi.com>, tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

At 13:03 26/07/2007, Murari Sridharan wrote:

>Aren't these directly related? Port randomization in general is good 
>and agreed not all scenarios exhaust ports but attacks typically are 
>on loaded servers and proxies, and if ports get exhausted in these 
>key scenarios where such a draft makes most sense, what's the point 
>of randomization?

Not necessarily. The RST attacks (and others) on which we are still 
working at tcpm wg typically target BGP routers, for which port 
numbers are usually *not* exhausted.

Port randomization is a general (and proactive) mitigation technique 
for off-path (blind attacks). It is cheap, and can be deployed incrementally.

Yes, there may be scenarios in which port numbers may have been 
exhausted, and thus port randomization might not be of much help. For 
those scenarios, you may need something else (probably not as cheap, 
and probably not as easy to deploy).

Kind regards,

--
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1












From tsvwg-bounces@ietf.org Mon Jul 30 17:27:54 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFcmI-0003o8-Is; Mon, 30 Jul 2007 17:27:46 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IFcmH-0003jK-4I
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 30 Jul 2007 17:27:45 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFcmG-0003hW-Ka
	for tsvwg@ietf.org; Mon, 30 Jul 2007 17:27:44 -0400
Received: from smtp1.xmundo.net ([201.216.232.80])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IFcmG-00026i-5n
	for tsvwg@ietf.org; Mon, 30 Jul 2007 17:27:44 -0400
Received: from venus.xmundo.net (venus.xmundo.net [201.216.232.56])
	by smtp1.xmundo.net (Postfix) with ESMTP id 45668F0C461;
	Mon, 30 Jul 2007 18:27:13 -0300 (ART)
Received: from fgont.gont.com.ar (200.61.43.18.static.telmex.net.ar
	[200.61.43.18] (may be forged)) (authenticated bits=0)
	by venus.xmundo.net (8.13.8/8.13.8) with ESMTP id l6ULQopi029773;
	Mon, 30 Jul 2007 18:27:05 -0300
Message-Id: <7.0.1.0.0.20070730031659.077fe0c0@gont.com.ar>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Mon, 30 Jul 2007 03:19:53 -0300
To: "Anantha Ramaiah \(ananth\)" <ananth@cisco.com>,
	"Caitlin Bestler" <cait@asomi.com>
From: Fernando Gont <fernando@gont.com.ar>
Subject: RE: [Tsvwg] Re: [tcpm] Revision
	ofdraft-larsen-tsvwg-port-randomization
In-Reply-To: <0C53DCFB700D144284A584F54711EC5803B6C65A@xmb-sjc-21c.amer.
	cisco.com>
References: <13DAF96D-70E1-411E-9408-130A33987671@asomi.com>
	<0C53DCFB700D144284A584F54711EC5803B6C65A@xmb-sjc-21c.amer.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by
	milter-greylist-2.0.2 (venus.xmundo.net [201.216.232.56]);
	Mon, 30 Jul 2007 18:27:13 -0300 (ART)
X-Spam-Score: 1.8 (+)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: Murari Sridharan <muraris@microsoft.com>, tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

At 12:37 26/07/2007, Anantha Ramaiah \(ananth\) wrote:

>OTOH, adding more TCP option space should not be treated as a radical
>change to TCP. Also the original email and the draft reference was more
>about doing some things (like port randomization) which would help
>increase the robustness of a some protocols, including TCP.

Exactly. What we propose is a local policy for selecting ephemeral 
ports. We do not propose any change to the syntax or semantics of any 
TCP field.

The policies we propose can be deployed incrementally, and aome of 
them already ship with a number of operating systems (including 
Linux, FreeBSD, and OpenBSD).

Kindest regards,

--
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1








From tsvwg-bounces@ietf.org Mon Jul 30 17:27:54 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFcmL-0003rG-6F; Mon, 30 Jul 2007 17:27:49 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IFcmJ-0003q6-6L
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 30 Jul 2007 17:27:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFcmI-0003pu-Qq
	for tsvwg@ietf.org; Mon, 30 Jul 2007 17:27:46 -0400
Received: from smtp1.xmundo.net ([201.216.232.80])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFcmH-0001kh-Gf
	for tsvwg@ietf.org; Mon, 30 Jul 2007 17:27:46 -0400
Received: from venus.xmundo.net (venus.xmundo.net [201.216.232.56])
	by smtp1.xmundo.net (Postfix) with ESMTP id F0AF7F0C478;
	Mon, 30 Jul 2007 18:27:21 -0300 (ART)
Received: from fgont.gont.com.ar (200.61.43.18.static.telmex.net.ar
	[200.61.43.18] (may be forged)) (authenticated bits=0)
	by venus.xmundo.net (8.13.8/8.13.8) with ESMTP id l6ULQopk029773;
	Mon, 30 Jul 2007 18:27:14 -0300
Message-Id: <7.0.1.0.0.20070730032039.07729738@gont.com.ar>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Mon, 30 Jul 2007 03:25:41 -0300
To: Murari Sridharan <muraris@microsoft.com>,
	Lars Eggert <lars.eggert@nokia.com>,
	"ext Anantha Ramaiah (ananth)" <ananth@cisco.com>
From: Fernando Gont <fernando@gont.com.ar>
Subject: RE: [Tsvwg] Re: [tcpm] Revision
	ofdraft-larsen-tsvwg-port-randomization
In-Reply-To: <FCA794787FDE0D4DBE9FFA11053ECEB60C26A16230@NA-EXMSG-C110.r
	edmond.corp.microsoft.com>
References: <0C53DCFB700D144284A584F54711EC5803B6C65A@xmb-sjc-21c.amer.cisco.com>
	<EE1A9283-BF50-43C9-8308-37ECF1B60363@nokia.com>
	<FCA794787FDE0D4DBE9FFA11053ECEB60C26A16230@NA-EXMSG-C110.redmond.corp.microsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by
	milter-greylist-2.0.2 (venus.xmundo.net [201.216.232.56]);
	Mon, 30 Jul 2007 18:27:21 -0300 (ART)
X-Spam-Score: 1.8 (+)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: Caitlin Bestler <cait@asomi.com>, tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

At 13:03 26/07/2007, Murari Sridharan wrote:

>Aren't these directly related? Port randomization in general is good 
>and agreed not all scenarios exhaust ports but attacks typically are 
>on loaded servers and proxies, and if ports get exhausted in these 
>key scenarios where such a draft makes most sense, what's the point 
>of randomization?

Not necessarily. The RST attacks (and others) on which we are still 
working at tcpm wg typically target BGP routers, for which port 
numbers are usually *not* exhausted.

Port randomization is a general (and proactive) mitigation technique 
for off-path (blind attacks). It is cheap, and can be deployed incrementally.

Yes, there may be scenarios in which port numbers may have been 
exhausted, and thus port randomization might not be of much help. For 
those scenarios, you may need something else (probably not as cheap, 
and probably not as easy to deploy).

Kind regards,

--
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1












From tsvwg-bounces@ietf.org Mon Jul 30 17:27:59 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFcmD-0003VT-0K; Mon, 30 Jul 2007 17:27:41 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IFcmC-0003VJ-3Y
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 30 Jul 2007 17:27:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFcmB-0003VA-Pc; Mon, 30 Jul 2007 17:27:39 -0400
Received: from smtp1.xmundo.net ([201.216.232.80])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IFcm9-0001kK-FQ; Mon, 30 Jul 2007 17:27:39 -0400
Received: from venus.xmundo.net (venus.xmundo.net [201.216.232.56])
	by smtp1.xmundo.net (Postfix) with ESMTP id 27D7CF0C46E;
	Mon, 30 Jul 2007 18:27:07 -0300 (ART)
Received: from fgont.gont.com.ar (200.61.43.18.static.telmex.net.ar
	[200.61.43.18] (may be forged)) (authenticated bits=0)
	by venus.xmundo.net (8.13.8/8.13.8) with ESMTP id l6ULQopg029773;
	Mon, 30 Jul 2007 18:27:00 -0300
Message-Id: <7.0.1.0.0.20070730030538.076fd2a8@gont.com.ar>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Mon, 30 Jul 2007 03:14:54 -0300
To: Murari Sridharan <muraris@microsoft.com>, tsvwg WG <tsvwg@ietf.org>
From: Fernando Gont <fernando@gont.com.ar>
Subject: RE: [Tsvwg] Re: [tcpm] Revision of
	draft-larsen-tsvwg-port-randomization
In-Reply-To: <FCA794787FDE0D4DBE9FFA11053ECEB60C26A1618E@NA-EXMSG-C110.r
	edmond.corp.microsoft.com>
References: <200702111621.l1BGL6mw029875@venus.xmundo.net>
	<0E46EBE9-1C13-44B6-9C04-476D418F5A6D@nokia.com>
	<A6CE6259-646E-4C35-9DA3-8911A8CB2B54@nokia.com>
	<FCA794787FDE0D4DBE9FFA11053ECEB60C26A1618E@NA-EXMSG-C110.redmond.corp.microsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by
	milter-greylist-2.0.2 (venus.xmundo.net [201.216.232.56]);
	Mon, 30 Jul 2007 18:27:06 -0300 (ART)
X-Spam-Score: 1.8 (+)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: "tcpm@ietf.org" <tcpm@ietf.org>, DCCP mailing list <dccp@ietf.org>,
	TSV Dir <tsv-dir@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

At 11:42 26/07/2007, Murari Sridharan wrote:

>In this context I wanted to bring up a related issue that might also 
>strengthen this sort of a port randomization proposal.
>
>Today the 64k port limitation is starting to become a huge problem 
>and most often admins add ip addresses to increase the scalability. 
>Given that most often the destination port (and sometimes the 
>destination address) is well known, the only scalability left is the 
>source address. Increasing ip addresses to improve scalability seems 
>a fairly round about approach and frankly doesn't scale well. Given 
>that the 64k limit is not fundamental why not provide a scaling 
>factor similar to the receive window to scale the number of usable 
>ports. This also makes randomization much more meaningful because in 
>certain proxy scenarios the number of connections quickly exhausts 
>the available ports and at that point the attacker can simply use 
>any port assuming he can guess the source address.

While I may agree with increasing the range of port numbers, I think 
this is out of the scope of the port randomization draft we have authored.

There are a few things that may be worth noting:

* The port randomization approaches discussed in the port 
randomization draft are independent of the range of ephemeral ports. 
That is, even if at some point we decide to scale the port numbers 
(or whatever), the approaches discussed in the port randomization 
draft would still apply.

* Most TCP implementations use for the ephemeral ports a very small 
subspace eg, ports 1024-4999) of the available port number space. 
That is, you may be using 1/10th of the range you have available. In 
this respect, our port randomization draft advises to increase the 
port number range used for ephemeral ports. This may help a bit in 
the scenarios you are describing.

Kind regards,

--
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1










From tsvwg-bounces@ietf.org Tue Jul 31 04:46:47 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFnNJ-0007dt-Hl; Tue, 31 Jul 2007 04:46:41 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IFnNI-0007do-9m
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 31 Jul 2007 04:46:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFnNI-0007dg-0A
	for tsvwg@ietf.org; Tue, 31 Jul 2007 04:46:40 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFnNG-0005u9-QM
	for tsvwg@ietf.org; Tue, 31 Jul 2007 04:46:39 -0400
Received: from localhost ([127.0.0.1])
	by psg.com with esmtp (Exim 4.67 (FreeBSD))
	(envelope-from <dpapadimitriou@psg.com>)
	id 1IFnN8-0007Ir-A0; Tue, 31 Jul 2007 08:46:36 +0000
Message-ID: <46AEF6DC.2080104@psg.com>
Date: Tue, 31 Jul 2007 10:46:20 +0200
From: dimitri papadimitriou <dpapadimitriou@psg.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
Subject: Re: [Tsvwg] Re: terminology issues in  draft-floyd-tsvwg-besteffort
	- flat monthly pricing
References: <5.2.1.1.2.20070726141117.04e7a828@pop3.jungle.bt.co.uk>
	<5.2.1.1.2.20070726141117.04e7a828@pop3.jungle.bt.co.uk>
	<5.2.1.1.2.20070730181738.04a1c4b8@pop3.jungle.bt.co.uk>
In-Reply-To: <5.2.1.1.2.20070730181738.04a1c4b8@pop3.jungle.bt.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -104.4 (---------------------------------------------------)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31b28e25e9d13a22020d8b7aedc9832c
Cc: tsvwg IETF list <tsvwg@ietf.org>, Mark Allman <mallman@icir.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dpapadimitriou@psg.com, dimitri.papadimitriou@alcatel-lucent.be
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

bob,

see in-line

>> you wrote:
>>
>> "so there won't be sufficient incentives for anyone to invest in more 
>> capacity for those of us who want to use the Internet responsibly."
>>
>> this might be indeed a concern
>>
>> but as shorter life socialist ;-) i do also strongly believe that 
>> before discussing the solution space we should first within the IETF 
>> community at large come with a good, clear, and common understanding 
>> whether this is a concern or not, if this is the case how important & 
>> urgent it might be, have better understanding about of some of the 
>> root causes, etc.
> 
> I've been working in non-IETF fora where that issue has been debated for 
> some years. That would be difficult for the IETF to do. It's difficult 
> for economists to come to any conclusion on that issue. Partly because 
> it gets convolved with monopoly issues in access networks.

since you are trying to address a non technical problem with a technical 
solution, there is a need for:
- determining whether this is a concern that the ietf is willing to
   address
- understanding root causes and effects and how penalizing they are
- the impact of the various mechanisms that could be put in place to
   solve the issue(s)
- whether the proposed solution really solves the problem for which they
   have been defined (reliability) and whether the cure is not worse
   than the disease itself (side effects)

all these point deserve imho a much better documentation that what's 
available and necessary in order to progress such effort

> But in my view, the problem is a lot more basic - in the current 
> Internet architecture there isn't even the basics of a mechanism to 
> support resource allocation: accountability. That sounds like billing, 
> but that's not what I mean. I mean being able to attribute a cost to a 
> user or network (irrespective of what you do with the information).

per rfc 2828, accountability is the property of a system or a service
(including all of its system resources) that ensures that the actions of
a system entity may be traced uniquely to that entity, so that it can be
held responsible for its actions.

in the present case, i think you are referring to the process where
users would be accountable for the openly accessible internet resources
they are making use of

the main technical point is fairness rules & enforcement on responsible 
internet's resources usage (outside of any market,business or economical 
pressure)

> It would be equivalent to a supermarket not being able to tell who had 
> taken stuff off the shelves. I think most economists would agree that 
> lack of accountability removes most incentives to invest if demand 
> doesn't easily satiate (e.g. a provider has the incentive to keep 
> investing in supplying all-you-can-eat buffet to people with limited 
> stomach capacity, but if faced with a range of customers with huge 
> stomachs, they tend to find other ways to limit demand - e.g. one plate 
> each).

hence, your concern is to limit the demand for economical reasons

mine, is to avoid starvation that could result if too big stomachs are 
present at the same time for societal reasons

hence, you see that one may have multitude of causes, different 
motivations, multiple approaches to the problem and a set of resulting 
solutions, all these points deserve much better analysis in my opinion

-d.

> Bob
> 
> 
>> -d.
>>
>> Bob Briscoe wrote:
>>> Sally,
>>> I just realised that I should have added a very important point about 
>>> "who controls the choice" to the rather philosophical response below.
>>> I'm trying to make sure we at the IETF don't have to decide whether 
>>> the Internet more favours rich people, malicious people or selfish 
>>> people. I'm trying to make it so what you think or what I think about 
>>> this doesn't matter (at least any more than what everyone else in the 
>>> world thinks).
>>> Firstly, what I'm proposing would sit alongside the current Internet 
>>> (re-ECN packets are distinguishable from non-re-ECN packets, so they 
>>> effectively partition all traffic orthogonally to Diffserv).
>>> Secondly, one partition would be the current Internet, with all its 
>>> vulnerabilites to selfish and malicious users as well as all its 
>>> strengths. The other partition would be this new proposal where the 
>>> market and social governance can control the way the Internet shares 
>>> out resources.
>>> At a grander level, the choice of how much resource each of the two 
>>> partitions gets would be under the direct control of ISPs, but in 
>>> turn their choices are also affected by the market and perhaps by 
>>> social control through government regulation.
>>> I know this fits your preferred model of how new resource allocation 
>>> strategies should be added to the Internet. The question is whether 
>>> it is sufficiently important to use IP header space to provide this 
>>> choice. We don't need to decide that now, but we do need to debate it 
>>> widely - more widely than tsvwg.
>>>
>>> Bob
>>> At 18:16 24/07/2007, Sally Floyd wrote:
>>>>> 3/ User pricing: Flat monthly (in our simplest effective proposal).
>>>>>
>>>>> Please don't imply we're advocating user congestion pricing, given 
>>>>> the whole reason we brought re-ECN to the IETF back in 2005 was 
>>>>> because we found a way to limit congestion without constraining how 
>>>>> operators price their services to their customers. Specifically, 
>>>>> re-ECN is designed to work with flat monthly pricing.
>>>>
>>>> This draft is not about re-ECN.  It is about the usefulness of
>>>> "simple best-effort traffic", and the usefulness of flow-rate fairness
>>>> for simple best-effort traffic.
>>>>
>>>> This draft is not about the presence or absence of flat monthly
>>>> pricing for users.  One could have flat monthly pricing with no
>>>> other limitations, one could have flat monthly pricing with volume
>>>> limits, or one could have flat monthly pricing with some form of
>>>> "you get what you pay for".  The first two forms don't result in
>>>> "rich" users getting all of the bandwidth in times of high congestion
>>>> (e.g., after the earthquake).  The third form easily could.  E.g.,
>>>> if all of the traffic was "you get what you pay for", even with
>>>> flat monthly fees, then it could be really expensive to send packets
>>>> in the time interval after the earthquake, or some other 
>>>> highly-congested
>>>> period, and only the rich would be able to send packets.  I would
>>>> be opposed to setting such a "you get what you pay for" goal as the
>>>> overriding goal for the global Internet, with or without flat monthly
>>>> fees.
>>> I know. It's distasteful to me to (I am a life-long socialist). But 
>>> the alternatives are worse. I have thought about this long and hard.
>>> On the demand side: If the rich don't get to be able to buy the right 
>>> to use capacity, the alternative is that the malicious and selfish 
>>> get to drive out those trying to be sociable in their use of the 
>>> Internet. And that's for always, not just during earthquakes. Also, 
>>> the lack of any resource sharing arbitration will lead to a vacuum 
>>> that will be filled by the rich and powerful (which is what deep 
>>> packet inspection represents - those with power and influence 
>>> controlling what can and can't be done on the Internet).
>>> On the supply side: The malicious and selfish will use the Internet 
>>> excessively, but not pay their share, so there won't be sufficient 
>>> incentives for anyone to invest in more capacity for those of us who 
>>> want to use the Internet responsibly.
>>> In summary, a knee-jerk reaction against a market mechanism needs to 
>>> be tempered by the thought of what will otherwise fill the vacuum - 
>>> the lesson of the Soviet Union?
>>> However, you will notice in my draft on fairness (and in my design of 
>>> re-ECN) that I have been careful to enable more equitable resource 
>>> allocation schemes locally. This can give _true_ equality, whereas 
>>> flow rate equality is just a license for the selfish and malicious to 
>>> take what they want.
>>> Overall, I put my hands up and admit it: we don't have a better 
>>> system for allocating resources on planet scale than a market. I wish 
>>> we did. We do have better resource sharing capabilities locally 
>>> though, and I want to enable them.
>>>
>>> Bob
>>>
>>>> - Sally
>>>> http://www.icir.org/floyd/
>>> ____________________________________________________________________________ 
>>>
>>> Notice: This contribution is the personal view of the author and does 
>>> not necessarily reflect the technical nor commercial direction of BT 
>>> plc.
>>> ____________________________________________________________________________ 
>>>
>>> Bob Briscoe,                           Networks Research Centre, BT 
>>> Research
>>> B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 
>>> 645196
>>>
>>> .
>>
>> ____________________________________________________________________________ 
>>
>> Bob Briscoe, <bob.briscoe@bt.com>      Networks Research Centre, BT 
>> Research
>> B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 
>> 645196 
> 
> 
> 
> .
> 






From tsvwg-bounces@ietf.org Tue Jul 31 10:52:01 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFt4o-00066X-I7; Tue, 31 Jul 2007 10:51:58 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IFt4n-00065J-CA
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 31 Jul 2007 10:51:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFt4n-000655-2X
	for tsvwg@ietf.org; Tue, 31 Jul 2007 10:51:57 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFt4l-0002c1-O5
	for tsvwg@ietf.org; Tue, 31 Jul 2007 10:51:57 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	B65F22115F; Tue, 31 Jul 2007 16:51:54 +0200 (CEST)
X-AuditID: c1b4fb3e-af032bb0000007e1-ca-46af4c8aaff6
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	8CF14200DB; Tue, 31 Jul 2007 16:51:54 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Jul 2007 16:51:54 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Jul 2007 16:51:53 +0200
Message-ID: <46AF4C89.1030500@ericsson.com>
Date: Tue, 31 Jul 2007 16:51:53 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: tsvwg <tsvwg@ietf.org>,  swallow@cisco.com, 
	Adrian Farrel <adrian@olddog.co.uk>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 31 Jul 2007 14:51:53.0802 (UTC)
	FILETIME=[558F6AA0:01C7D382]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: 
Subject: [Tsvwg] Comments on draft-ietf-tsvwg-user-error-spec-01
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi,

I did reveiw the draft before the meeting. Sorry to be slow in sending 
out the comments.

1. Is it really the best use of User_ERROR_SPEC object to only allow it 
on the new Error Code? I can understand the desire to allow error 
reporting in case previously not possible. But is there not a benefit in 
allowing the USER_ERROR_SPEC object to be present also for other error 
codes? Thus allowing implementations to provide additional information 
when existing error codes is the correct ones to be used?

2. I think you need to clarify which numbers from IANA that needs to go 
where. I would recommend that you use different identifiers for numbers 
to be assigned in the text and then are clear in the IANA section which 
number that comes from which place.

3. Section 3.1: Length definition:
"The Length contains the total length of the subobject in bytes,
         including the L, Type and Length fields."

What is the "L" in the subobject?

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------





From tsvwg-bounces@ietf.org Tue Jul 31 10:57:01 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFt9f-0000LY-QF; Tue, 31 Jul 2007 10:56:59 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IFt9c-0000L9-Ic
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 31 Jul 2007 10:56:56 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFt9c-0000L0-8O; Tue, 31 Jul 2007 10:56:56 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IFt9b-0004Sa-Qp; Tue, 31 Jul 2007 10:56:56 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	350512068B; Tue, 31 Jul 2007 16:56:55 +0200 (CEST)
X-AuditID: c1b4fb3c-af67dbb0000007e1-10-46af4db78ea6
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	26C612056D; Tue, 31 Jul 2007 16:56:55 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Jul 2007 16:56:55 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Jul 2007 16:56:54 +0200
Message-ID: <46AF4DB6.6000304@ericsson.com>
Date: Tue, 31 Jul 2007 16:56:54 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: tsvwg <tsvwg@ietf.org>,  mpls@ietf.org
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 31 Jul 2007 14:56:54.0341 (UTC)
	FILETIME=[08B20750:01C7D383]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: 
Subject: [Tsvwg] WG last call: draft-ietf-tsvwg-ecn-mpls-01
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

This announces the WG last call on "Explicit Congestion Marking in MPLS" 
with the intended status of Proposed Standard. Due to vacation times the 
WG last call will run for 3 weeks. The WG last call ends the 21st of 
August.

http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-ecn-mpls-01.txt


Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------





From tsvwg-bounces@ietf.org Tue Jul 31 10:59:16 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFtBq-0002Bc-Li; Tue, 31 Jul 2007 10:59:14 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IFtBp-0002BQ-5T
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 31 Jul 2007 10:59:13 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFtBo-0002BI-Rd
	for tsvwg@ietf.org; Tue, 31 Jul 2007 10:59:12 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IFtBo-0004VX-Dk
	for tsvwg@ietf.org; Tue, 31 Jul 2007 10:59:12 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	CBAC2207D5
	for <tsvwg@ietf.org>; Tue, 31 Jul 2007 16:59:11 +0200 (CEST)
X-AuditID: c1b4fb3c-b0e80bb0000007e1-94-46af4e3f6a0f
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	B9C5720006
	for <tsvwg@ietf.org>; Tue, 31 Jul 2007 16:59:11 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Jul 2007 16:59:11 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Jul 2007 16:59:11 +0200
Message-ID: <46AF4E3F.7080100@ericsson.com>
Date: Tue, 31 Jul 2007 16:59:11 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: tsvwg <tsvwg@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 31 Jul 2007 14:59:11.0244 (UTC)
	FILETIME=[5A4BC4C0:01C7D383]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Subject: [Tsvwg] WG last call: draft-ietf-tsvwg-udplite-mib-00
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

This announces the WG last call on "MIB for the UDP-Lite protocol" with 
the intended status of Proposed Standard. Due to vacation times the WG 
last call will run for 3 weeks. The WG last call ends the 21st of August.

http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-udplite-mib-00.txt


Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------





From tsvwg-bounces@ietf.org Tue Jul 31 11:21:27 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFtXJ-0001hV-3T; Tue, 31 Jul 2007 11:21:25 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IFtXI-0001gv-6S
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 31 Jul 2007 11:21:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFtXH-0001gk-Sk; Tue, 31 Jul 2007 11:21:23 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IFtXG-0003rm-8U; Tue, 31 Jul 2007 11:21:23 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	A5EBB548021; Tue, 31 Jul 2007 17:21:21 +0200 (CEST)
X-AuditID: c1b4fb3c-afe7ebb0000007e1-a7-46af53713e29
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	4277920474; Tue, 31 Jul 2007 17:21:21 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Jul 2007 17:21:20 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Jul 2007 17:21:20 +0200
Message-ID: <46AF5370.9020304@ericsson.com>
Date: Tue, 31 Jul 2007 17:21:20 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: tsvwg <tsvwg@ietf.org>, NSIS <nsis@ietf.org>, 
	IETF SIPPING WG <sipping@ietf.org>, sip@ietf.org
Content-Type: text/plain; charset=UTF-8; format=flowed
X-OriginalArrivalTime: 31 Jul 2007 15:21:20.0301 (UTC)
	FILETIME=[7279C5D0:01C7D386]
X-Brightmail-Tracker: AAAAAA==
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 96d3a783a4707f1ab458eb15058bb2d7
Cc: 
Subject: [Tsvwg] Draft Liaision response to SG13 on Emergency
	Telecommunications
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi

This is the draft for a liaison response to be sent to SG 13 of the=20
ITU-T from the TSVWG, NSIS, SIP and SIPPING WGs. Please provide any=20
comments at the latest by the 14th of August. After that we will address=20
any raised comments and send the liaison to ITU-T before the end of Augus=
t.

Submission
Date:		<tbd>, 2007

From: 		IETF Working groups TSVWG, NSIS, SIP and SIPPING

To:		Georges Sebek  <tsbsg13@itu.int> ,
		Keith Knightson <kgk@igs.net>

Cc:		Magnus Westerlund <magnus.westerlund@ericsson.com>,
                 Lars Eggert <lars.eggert@nokia.com>,
                 James Polk <jmpolk@cisco.com>,
                 Martin Stiemerling <stiemerling@netlab.nec.de>,
                 John Loughney <john.loughney@nokia.com>
                 Dean Willis <dean.willis@softarmor.com>,
                 Keith Drage <drage@alcatel-lucent.com>,
                 Mary Barnes <mary.barnes@nortel.com>,
                 Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>,
                 Scott Bradner <sob@harvard.edu>,
                 Kimberly King <ksking@mitre.org>,
                 Scott Brim <swb@employees.org>

Response
Contact:	TSV WG (tsv-chairs@tools.ietf.org)
		NSIS (nsis-chairs@tools.ietf.org)
		SIPPING (sipping-chairs@tools.ietf.org)
		SIP (sip-chairs@tools.ietf.org)
=09
Purpose: 	Response to Liaison Request

Deadline:	None

Title: Response to liaison request from ITU-T Study Group 13 work on=20
emergency telecommunications

This is a response to the liaison request made by Q3/13 regarding=20
emergency telecommunications (REF: NGN-GSI/DOC =E2=80=93 60 Rev.2). We wo=
uld=20
first like to apologize for failing to meet the deadline in responding.=20
We do hope that the late answer still can be of some use.

The liaison request was made to the following working groups (WG):=20
IEPREP, TSVWG, and NSIS. Since the request was sent the IEPREP WG has=20
concluded. In addition to the WGs from which information was requested,=20
we also think that work performed by the SIP and SIPPING WG may be of=20
relevance.

Pursuant to ITU-T Study Group 13 request for information on relevant and=20
related work in the IETF regarding emergency communications, we list=20
below RFCs and works in progress that we feel may be of interest to your=20
group.  Some of the completed work is Informational, and others are in=20
the category of Standards Track.

Q.3/13 also requested that we keep you informed of any developments in=20
regards to emergency telecommunications. In those regards we would like=20
to make you aware that IETF mailing list participation and document=20
information is free and open for anyone. Allowing participants in Q.3/13=20
to keep them selves informed of any developments. If Q.3/13 desire to=20
get further information about specific ongoing work, then please send a=20
liaison request to the responsible WG for those specific documents.

The following list is divided under the associated working groups from=20
which the work has been done within the IETF.


SIP Working Group

RFC 4411

Title:
    Extending the Session Initiation Protocol (SIP)
    Reason Header for Preemption Events

Abstract:
   This document proposes an IANA Registration extension to the Session
    Initiation Protocol (SIP) Reason Header to be included in a BYE
    Method Request as a result of a session preemption event, either at a
    user agent (UA), or somewhere in the network involving a
    reservation-based protocol such as the Resource ReSerVation Protocol
    (RSVP) or Next Steps in Signaling (NSIS).  This document does not
    attempt to address routers failing in the packet path; instead, it
    addresses a deliberate tear down of a flow between UAs, and informs
    the terminated UA(s) with an indication of what occurred.

RFC 4412

Title:
    Communications Resource Priority for the Session Initiation
    Protocol (SIP)

Abstract:
    This document defines two new Session Initiation Protocol (SIP)
    header fields for communicating resource priority, namely,
    "Resource-Priority" and "Accept-Resource-Priority".  The
    "Resource-Priority" header field can influence the behavior of SIP
    user agents (such as telephone gateways and IP telephones) and SIP
    proxies.  It does not directly influence the forwarding behavior of
    IP routers.



SIPPING Working Group

    The below two documents are proposed work items not yet accepted as
    IETF WG items but are likely of interest as they update RFC 4412.

Work In Progress:   draft-polk-sip-rph-in-responses-00

Title:
    Allowing SIP Resource Priority Header in SIP Responses

Abstract:
    The Session Initiation Protocol (SIP) Resource Priority Header
    (RPH), in its current form, is ignored in SIP responses.  This was a
    design choice during RFC 4412's development. This is now considered
    a bad design choice in certain scenarios.  This document corrects
    RFC 4412's communications model by optionally allowing a SIP server
    or user agent client to process the Resource-Priority Header in a
    response.

Work In Progress:   draft-polk-sip-rph-new-namespaces--00

Title:
    New Session Initiation Protocol Resource-Priority Header Namespaces
    for the Defense Information Systems Agency

Abstract:
    This document creates additional Session Initiation Protocol
    Resource-Priority header namespaces, to be IANA registered.  This
    document intends to update RFC 4412, as a Proposed Standard document
    if published by the RFC-Editor.

IEPREP Working Group

RFC 3487

Title:
    Requirements for Resource Priority Mechanisms for the
    Session Initiation Protocol (SIP)

Abstract:
    This document summarizes requirements for prioritizing access to
    circuit-switched network, end system and proxy resources for
    emergency preparedness communications using the Session Initiation
    Protocol (SIP).

RFC 3689

Title:
    General Requirements for
    Emergency Telecommunication Service (ETS)

Abstract:
    This document presents a list of general requirements in support of
    Emergency Telecommunications Service (ETS).  Solutions to these
    requirements are not presented in this document.  Additional
    requirements pertaining to specific applications, or types of
    applications, are to be specified in separate document(s).

RFC 3690

Title:
    IP Telephony Requirements for
    Emergency Telecommunication Service (ETS)

Abstract:
    This document presents a list of requirements in support of Emergency
    Telecommunications Service (ETS) within the context of IP telephony.
    It is an extension to the general requirements presented in RFC 3689.
    Solutions to these requirements are not presented in this document.

RFC 4190

Title:
    Framework for Supporting Emergency Telecommunications
    Service (ETS) in IP Telephony

Abstract:
    This document presents a framework for supporting authorized,
    emergency-related communication within the context of IP telephony.
    We present a series of objectives that reflect a general view of how
    authorized emergency service, in line with the Emergency
    Telecommunications Service (ETS), should be realized within today's
    IP architecture and service models.  From these objectives, we
    present a corresponding set of protocols and capabilities, which
    provide a more specific set of recommendations regarding existing
    IETF protocols.  Finally, we present two scenarios that act as
    guiding models for the objectives and functions listed in this
    document.  These models, coupled with an example of an existing
    service in the Public Switched Telephone Network (PSTN), contribute
    to a constrained solution space.

RFC 4375

Title:
    Emergency Telecommunications Services (ETS) Requirements
    for a Single Administrative Domain

Abstract:
    This document presents a list of requirements in support of Emergency
    Telecommunications Service (ETS) within a single administrative
    domain.  This document focuses on a specific set of administrative
    constraints and scope.  Solutions to these requirements are not
    presented in this document.


TSV Working Group

RFC 4542

Title:
    Implementing an Emergency Telecommunications Service (ETS)
    for Real-Time Services in the Internet Protocol Suite

Abstract:
    RFCs 3689 and 3690 detail requirements for an Emergency
    Telecommunications Service (ETS), of which an Internet Emergency
    Preparedness Service (IEPS) would be a part.  Some of these types of
    services require call preemption; others require call queuing or
    other mechanisms.  IEPS requires a Call Admission Control (CAC)
    procedure and a Per Hop Behavior (PHB) for the data that meet the
    needs of this architecture.  Such a CAC procedure and PHB is
    appropriate to any service that might use H.323 or SIP to set up
    real-time sessions.  The key requirement is to guarantee an elevated
    probability of call completion to an authorized user in time of
    crisis.

    This document primarily discusses supporting ETS in the context of
    the US Government and NATO, because it focuses on the Multi-Level
    Precedence and Preemption (MLPP) and Government Emergency
    Telecommunication Service (GETS) standards.  The architectures
    described here are applicable beyond these organizations.

Work In Progress:   draft-ietf-tsvwg-emergency-rsvp-03.txt

Title:
    Resource ReSerVation Protovol (RSVP) Extensions for
    Emergency Services

Abstract:
    An Emergency Telecommunications Service (ETS) requires the ability to
    provide an elevated probability of session establishment to an
    authorized user in times of network congestion (typically, during a
    crisis). When supported over the Internet Protocol suite, this may be
    facilitated through a network layer admission control solution, which
    supports prioritized access to resources (e.g., bandwidth). These
    resources may be explicitly set aside for emergency services, or they
    may be shared with other sessions.

   This document specifies RSVP extensions that can be used to support
    such an admission priority capability at the network layer. Note that
    these extensions represent one possible solution component in
    satisfying ETS requirements. Other solution components, or other
    solutions, are outside the scope of this document.

NSIS Working Group

Work In Progress: draft-ietf-nsis-qos-nslp-14.txt

Title:
    NSLP for Quality-of-Service Signaling

Abstract:
    This specification describes the NSIS Signaling Layer Protocol
    (NSLP) for signaling QoS reservations in the Internet.  It is in
    accordance with the framework and requirements developed in NSIS.
    Together with GIST, it provides functionality similar to RSVP and
    extends it.  The QoS NSLP is independent of the underlying QoS
    specification or architecture and provides support for different
    reservation models. It is simplified by the elimination of support
    for multicast flows. This specification explains the overall
    protocol approach, design decisions made and provides examples.  It
    specifies object, message  formats and processing rules.

--=20

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------





From tsvwg-bounces@ietf.org Tue Jul 31 11:34:41 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFtk5-0005aV-Bl; Tue, 31 Jul 2007 11:34:37 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IFtk1-0005UB-WE
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 31 Jul 2007 11:34:34 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFtk0-0005Rk-HX; Tue, 31 Jul 2007 11:34:32 -0400
Received: from mail171.messagelabs.com ([216.82.253.243])
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1IFtjx-00062P-RG; Tue, 31 Jul 2007 11:34:32 -0400
X-VirusChecked: Checked
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-12.tower-171.messagelabs.com!1185896061!8098786!1
X-StarScan-Version: 5.5.12.11; banners=-,-,-
X-Originating-IP: [20.137.52.151]
Received: (qmail 14991 invoked from network); 31 Jul 2007 15:34:22 -0000
Received: from amer-mta07.csc.com (HELO amer-mta07.csc.com) (20.137.52.151)
	by server-12.tower-171.messagelabs.com with AES256-SHA encrypted SMTP;
	31 Jul 2007 15:34:22 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245])
	by amer-mta07.csc.com (Switch-3.1.6/Switch-3.1.7) with ESMTP id
	l6VFYaYJ009979; Tue, 31 Jul 2007 11:34:37 -0400 (EDT)
In-Reply-To: <46AF5370.9020304@ericsson.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: Re: [Tsvwg] Draft Liaision response to SG13 on
	Emergency	Telecommunications
MIME-Version: 1.0
X-Mailer: Lotus Notes 652HF83 November 04, 2004
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OF534C1677.A38ACB80-ON85257329.0054CDD0-85257329.005589BA@csc.com>
Date: Tue, 31 Jul 2007 11:34:17 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 7.0.2FP1
	HF180|March 29, 2007) at 07/31/2007 11:32:58 AM,
	Serialize complete at 07/31/2007 11:32:58 AM
Content-Type: multipart/alternative;
	boundary="=_alternative 0055890785257329_="
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ee8eaa76ea6a4fb3ccc9059a3f656ffc
Cc: sip@ietf.org, IETF SIPPING WG <sipping@ietf.org>, tsvwg <tsvwg@ietf.org>,
	NSIS <nsis@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

This is a multipart message in MIME format.
--=_alternative 0055890785257329_=
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64

TWFnbnVzLA0KDQpZb3UgbWlnaHQgd2FudCB0byBhZGQtDQoNCmRyYWZ0LXBvbGstdHN2d2ctc2ln
bmFsZWQtZG9tYWluLWlkLTAwLnR4dA0KYW5kIA0KZHJhZnQtcG9say1lY3JpdC1sb2NhbC1lbWVy
Z2VuY3ktcnBoLW5hbWVzcGFjZS0wMS50eHQNCg0KKEJvdGggd2VyZSBvbiB0aGUgYWdlbmRhIGFu
ZCBkaXNjdXNzZWQuKQ0KDQpBbmQgbWF5YmUNCmRyYWZ0LWNhcmxiZXJnLXRyaXAtYXR0cmlidXRl
LXJwLTAyIA0KDQoodGhvdWdoIEkgZGlkIG5vdCBzZWUgaXQgb24gdGhlIGFnZW5kYSkNCg0KSmFu
ZXQNCg0KUFMsDQoNCk15IHNwZWxsaW5nIGNoZWNrZXIgc2F5cyAiTGlhaXNpb24iIHNob3VsZCBi
ZSAiTGlhaXNvbiIsIGJ1dCBpdCBtYXkgYmUgYSANClVTIGNlbnRyaWMgZGljdGlvbmFyeS4NCkoN
Ck1hZ251cyBXZXN0ZXJsdW5kIDxtYWdudXMud2VzdGVybHVuZEBlcmljc3Nvbi5jb20+IHdyb3Rl
IG9uIDA3LzMxLzIwMDcgDQoxMToyMToyMCBBTToNCg0KPiBIaQ0KPiANCj4gVGhpcyBpcyB0aGUg
ZHJhZnQgZm9yIGEgbGlhaXNvbiByZXNwb25zZSB0byBiZSBzZW50IHRvIFNHIDEzIG9mIHRoZSAN
Cj4gSVRVLVQgZnJvbSB0aGUgVFNWV0csIE5TSVMsIFNJUCBhbmQgU0lQUElORyBXR3MuIFBsZWFz
ZSBwcm92aWRlIGFueSANCj4gY29tbWVudHMgYXQgdGhlIGxhdGVzdCBieSB0aGUgMTR0aCBvZiBB
dWd1c3QuIEFmdGVyIHRoYXQgd2Ugd2lsbCBhZGRyZXNzIA0KDQo+IGFueSByYWlzZWQgY29tbWVu
dHMgYW5kIHNlbmQgdGhlIGxpYWlzb24gdG8gSVRVLVQgYmVmb3JlIHRoZSBlbmQgb2YgDQpBdWd1
c3QuDQo+IA0KPiBTdWJtaXNzaW9uDQo+IERhdGU6ICAgICAgPHRiZD4sIDIwMDcNCj4gDQo+IEZy
b206ICAgICAgIElFVEYgV29ya2luZyBncm91cHMgVFNWV0csIE5TSVMsIFNJUCBhbmQgU0lQUElO
Rw0KPiANCj4gVG86ICAgICAgR2VvcmdlcyBTZWJlayAgPHRzYnNnMTNAaXR1LmludD4gLA0KPiAg
ICAgICBLZWl0aCBLbmlnaHRzb24gPGtna0BpZ3MubmV0Pg0KPiANCj4gQ2M6ICAgICAgTWFnbnVz
IFdlc3Rlcmx1bmQgPG1hZ251cy53ZXN0ZXJsdW5kQGVyaWNzc29uLmNvbT4sDQo+ICAgICAgICAg
ICAgICAgICAgTGFycyBFZ2dlcnQgPGxhcnMuZWdnZXJ0QG5va2lhLmNvbT4sDQo+ICAgICAgICAg
ICAgICAgICAgSmFtZXMgUG9sayA8am1wb2xrQGNpc2NvLmNvbT4sDQo+ICAgICAgICAgICAgICAg
ICAgTWFydGluIFN0aWVtZXJsaW5nIDxzdGllbWVybGluZ0BuZXRsYWIubmVjLmRlPiwNCj4gICAg
ICAgICAgICAgICAgICBKb2huIExvdWdobmV5IDxqb2huLmxvdWdobmV5QG5va2lhLmNvbT4NCj4g
ICAgICAgICAgICAgICAgICBEZWFuIFdpbGxpcyA8ZGVhbi53aWxsaXNAc29mdGFybW9yLmNvbT4s
DQo+ICAgICAgICAgICAgICAgICAgS2VpdGggRHJhZ2UgPGRyYWdlQGFsY2F0ZWwtbHVjZW50LmNv
bT4sDQo+ICAgICAgICAgICAgICAgICAgTWFyeSBCYXJuZXMgPG1hcnkuYmFybmVzQG5vcnRlbC5j
b20+LA0KPiAgICAgICAgICAgICAgICAgIEdvbnphbG8gQ2FtYXJpbGxvIDxnb256YWxvLmNhbWFy
aWxsb0Blcmljc3Nvbi5jb20+LA0KPiAgICAgICAgICAgICAgICAgIFNjb3R0IEJyYWRuZXIgPHNv
YkBoYXJ2YXJkLmVkdT4sDQo+ICAgICAgICAgICAgICAgICAgS2ltYmVybHkgS2luZyA8a3NraW5n
QG1pdHJlLm9yZz4sDQo+ICAgICAgICAgICAgICAgICAgU2NvdHQgQnJpbSA8c3diQGVtcGxveWVl
cy5vcmc+DQo+IA0KPiBSZXNwb25zZQ0KPiBDb250YWN0OiAgIFRTViBXRyAodHN2LWNoYWlyc0B0
b29scy5pZXRmLm9yZykNCj4gICAgICAgTlNJUyAobnNpcy1jaGFpcnNAdG9vbHMuaWV0Zi5vcmcp
DQo+ICAgICAgIFNJUFBJTkcgKHNpcHBpbmctY2hhaXJzQHRvb2xzLmlldGYub3JnKQ0KPiAgICAg
ICBTSVAgKHNpcC1jaGFpcnNAdG9vbHMuaWV0Zi5vcmcpDQo+IA0KPiBQdXJwb3NlOiAgICBSZXNw
b25zZSB0byBMaWFpc29uIFJlcXVlc3QNCj4gDQo+IERlYWRsaW5lOiAgIE5vbmUNCj4gDQo+IFRp
dGxlOiBSZXNwb25zZSB0byBsaWFpc29uIHJlcXVlc3QgZnJvbSBJVFUtVCBTdHVkeSBHcm91cCAx
MyB3b3JrIG9uIA0KPiBlbWVyZ2VuY3kgdGVsZWNvbW11bmljYXRpb25zDQo+IA0KPiBUaGlzIGlz
IGEgcmVzcG9uc2UgdG8gdGhlIGxpYWlzb24gcmVxdWVzdCBtYWRlIGJ5IFEzLzEzIHJlZ2FyZGlu
ZyANCj4gZW1lcmdlbmN5IHRlbGVjb21tdW5pY2F0aW9ucyAoUkVGOiBOR04tR1NJL0RPQyDigJMg
NjAgUmV2LjIpLiBXZSB3b3VsZCANCj4gZmlyc3QgbGlrZSB0byBhcG9sb2dpemUgZm9yIGZhaWxp
bmcgdG8gbWVldCB0aGUgZGVhZGxpbmUgaW4gcmVzcG9uZGluZy4gDQo+IFdlIGRvIGhvcGUgdGhh
dCB0aGUgbGF0ZSBhbnN3ZXIgc3RpbGwgY2FuIGJlIG9mIHNvbWUgdXNlLg0KPiANCj4gVGhlIGxp
YWlzb24gcmVxdWVzdCB3YXMgbWFkZSB0byB0aGUgZm9sbG93aW5nIHdvcmtpbmcgZ3JvdXBzIChX
Ryk6IA0KPiBJRVBSRVAsIFRTVldHLCBhbmQgTlNJUy4gU2luY2UgdGhlIHJlcXVlc3Qgd2FzIHNl
bnQgdGhlIElFUFJFUCBXRyBoYXMgDQo+IGNvbmNsdWRlZC4gSW4gYWRkaXRpb24gdG8gdGhlIFdH
cyBmcm9tIHdoaWNoIGluZm9ybWF0aW9uIHdhcyByZXF1ZXN0ZWQsIA0KPiB3ZSBhbHNvIHRoaW5r
IHRoYXQgd29yayBwZXJmb3JtZWQgYnkgdGhlIFNJUCBhbmQgU0lQUElORyBXRyBtYXkgYmUgb2Yg
DQo+IHJlbGV2YW5jZS4NCj4gDQo+IFB1cnN1YW50IHRvIElUVS1UIFN0dWR5IEdyb3VwIDEzIHJl
cXVlc3QgZm9yIGluZm9ybWF0aW9uIG9uIHJlbGV2YW50IGFuZCANCg0KPiByZWxhdGVkIHdvcmsg
aW4gdGhlIElFVEYgcmVnYXJkaW5nIGVtZXJnZW5jeSBjb21tdW5pY2F0aW9ucywgd2UgbGlzdCAN
Cj4gYmVsb3cgUkZDcyBhbmQgd29ya3MgaW4gcHJvZ3Jlc3MgdGhhdCB3ZSBmZWVsIG1heSBiZSBv
ZiBpbnRlcmVzdCB0byB5b3VyIA0KDQo+IGdyb3VwLiAgU29tZSBvZiB0aGUgY29tcGxldGVkIHdv
cmsgaXMgSW5mb3JtYXRpb25hbCwgYW5kIG90aGVycyBhcmUgaW4gDQo+IHRoZSBjYXRlZ29yeSBv
ZiBTdGFuZGFyZHMgVHJhY2suDQo+IA0KPiBRLjMvMTMgYWxzbyByZXF1ZXN0ZWQgdGhhdCB3ZSBr
ZWVwIHlvdSBpbmZvcm1lZCBvZiBhbnkgZGV2ZWxvcG1lbnRzIGluIA0KPiByZWdhcmRzIHRvIGVt
ZXJnZW5jeSB0ZWxlY29tbXVuaWNhdGlvbnMuIEluIHRob3NlIHJlZ2FyZHMgd2Ugd291bGQgbGlr
ZSANCj4gdG8gbWFrZSB5b3UgYXdhcmUgdGhhdCBJRVRGIG1haWxpbmcgbGlzdCBwYXJ0aWNpcGF0
aW9uIGFuZCBkb2N1bWVudCANCj4gaW5mb3JtYXRpb24gaXMgZnJlZSBhbmQgb3BlbiBmb3IgYW55
b25lLiBBbGxvd2luZyBwYXJ0aWNpcGFudHMgaW4gUS4zLzEzIA0KDQo+IHRvIGtlZXAgdGhlbSBz
ZWx2ZXMgaW5mb3JtZWQgb2YgYW55IGRldmVsb3BtZW50cy4gSWYgUS4zLzEzIGRlc2lyZSB0byAN
Cj4gZ2V0IGZ1cnRoZXIgaW5mb3JtYXRpb24gYWJvdXQgc3BlY2lmaWMgb25nb2luZyB3b3JrLCB0
aGVuIHBsZWFzZSBzZW5kIGEgDQo+IGxpYWlzb24gcmVxdWVzdCB0byB0aGUgcmVzcG9uc2libGUg
V0cgZm9yIHRob3NlIHNwZWNpZmljIGRvY3VtZW50cy4NCj4gDQo+IFRoZSBmb2xsb3dpbmcgbGlz
dCBpcyBkaXZpZGVkIHVuZGVyIHRoZSBhc3NvY2lhdGVkIHdvcmtpbmcgZ3JvdXBzIGZyb20gDQo+
IHdoaWNoIHRoZSB3b3JrIGhhcyBiZWVuIGRvbmUgd2l0aGluIHRoZSBJRVRGLg0KPiANCj4gDQo+
IFNJUCBXb3JraW5nIEdyb3VwDQo+IA0KPiBSRkMgNDQxMQ0KPiANCj4gVGl0bGU6DQo+ICAgICBF
eHRlbmRpbmcgdGhlIFNlc3Npb24gSW5pdGlhdGlvbiBQcm90b2NvbCAoU0lQKQ0KPiAgICAgUmVh
c29uIEhlYWRlciBmb3IgUHJlZW1wdGlvbiBFdmVudHMNCj4gDQo+IEFic3RyYWN0Og0KPiAgICBU
aGlzIGRvY3VtZW50IHByb3Bvc2VzIGFuIElBTkEgUmVnaXN0cmF0aW9uIGV4dGVuc2lvbiB0byB0
aGUgU2Vzc2lvbg0KPiAgICAgSW5pdGlhdGlvbiBQcm90b2NvbCAoU0lQKSBSZWFzb24gSGVhZGVy
IHRvIGJlIGluY2x1ZGVkIGluIGEgQllFDQo+ICAgICBNZXRob2QgUmVxdWVzdCBhcyBhIHJlc3Vs
dCBvZiBhIHNlc3Npb24gcHJlZW1wdGlvbiBldmVudCwgZWl0aGVyIGF0IA0KYQ0KPiAgICAgdXNl
ciBhZ2VudCAoVUEpLCBvciBzb21ld2hlcmUgaW4gdGhlIG5ldHdvcmsgaW52b2x2aW5nIGENCj4g
ICAgIHJlc2VydmF0aW9uLWJhc2VkIHByb3RvY29sIHN1Y2ggYXMgdGhlIFJlc291cmNlIFJlU2Vy
VmF0aW9uIFByb3RvY29sDQo+ICAgICAoUlNWUCkgb3IgTmV4dCBTdGVwcyBpbiBTaWduYWxpbmcg
KE5TSVMpLiAgVGhpcyBkb2N1bWVudCBkb2VzIG5vdA0KPiAgICAgYXR0ZW1wdCB0byBhZGRyZXNz
IHJvdXRlcnMgZmFpbGluZyBpbiB0aGUgcGFja2V0IHBhdGg7IGluc3RlYWQsIGl0DQo+ICAgICBh
ZGRyZXNzZXMgYSBkZWxpYmVyYXRlIHRlYXIgZG93biBvZiBhIGZsb3cgYmV0d2VlbiBVQXMsIGFu
ZCBpbmZvcm1zDQo+ICAgICB0aGUgdGVybWluYXRlZCBVQShzKSB3aXRoIGFuIGluZGljYXRpb24g
b2Ygd2hhdCBvY2N1cnJlZC4NCj4gDQo+IFJGQyA0NDEyDQo+IA0KPiBUaXRsZToNCj4gICAgIENv
bW11bmljYXRpb25zIFJlc291cmNlIFByaW9yaXR5IGZvciB0aGUgU2Vzc2lvbiBJbml0aWF0aW9u
DQo+ICAgICBQcm90b2NvbCAoU0lQKQ0KPiANCj4gQWJzdHJhY3Q6DQo+ICAgICBUaGlzIGRvY3Vt
ZW50IGRlZmluZXMgdHdvIG5ldyBTZXNzaW9uIEluaXRpYXRpb24gUHJvdG9jb2wgKFNJUCkNCj4g
ICAgIGhlYWRlciBmaWVsZHMgZm9yIGNvbW11bmljYXRpbmcgcmVzb3VyY2UgcHJpb3JpdHksIG5h
bWVseSwNCj4gICAgICJSZXNvdXJjZS1Qcmlvcml0eSIgYW5kICJBY2NlcHQtUmVzb3VyY2UtUHJp
b3JpdHkiLiAgVGhlDQo+ICAgICAiUmVzb3VyY2UtUHJpb3JpdHkiIGhlYWRlciBmaWVsZCBjYW4g
aW5mbHVlbmNlIHRoZSBiZWhhdmlvciBvZiBTSVANCj4gICAgIHVzZXIgYWdlbnRzIChzdWNoIGFz
IHRlbGVwaG9uZSBnYXRld2F5cyBhbmQgSVAgdGVsZXBob25lcykgYW5kIFNJUA0KPiAgICAgcHJv
eGllcy4gIEl0IGRvZXMgbm90IGRpcmVjdGx5IGluZmx1ZW5jZSB0aGUgZm9yd2FyZGluZyBiZWhh
dmlvciBvZg0KPiAgICAgSVAgcm91dGVycy4NCj4gDQo+IA0KPiANCj4gU0lQUElORyBXb3JraW5n
IEdyb3VwDQo+IA0KPiAgICAgVGhlIGJlbG93IHR3byBkb2N1bWVudHMgYXJlIHByb3Bvc2VkIHdv
cmsgaXRlbXMgbm90IHlldCBhY2NlcHRlZCBhcw0KPiAgICAgSUVURiBXRyBpdGVtcyBidXQgYXJl
IGxpa2VseSBvZiBpbnRlcmVzdCBhcyB0aGV5IHVwZGF0ZSBSRkMgNDQxMi4NCj4gDQo+IFdvcmsg
SW4gUHJvZ3Jlc3M6ICAgZHJhZnQtcG9say1zaXAtcnBoLWluLXJlc3BvbnNlcy0wMA0KPiANCj4g
VGl0bGU6DQo+ICAgICBBbGxvd2luZyBTSVAgUmVzb3VyY2UgUHJpb3JpdHkgSGVhZGVyIGluIFNJ
UCBSZXNwb25zZXMNCj4gDQo+IEFic3RyYWN0Og0KPiAgICAgVGhlIFNlc3Npb24gSW5pdGlhdGlv
biBQcm90b2NvbCAoU0lQKSBSZXNvdXJjZSBQcmlvcml0eSBIZWFkZXINCj4gICAgIChSUEgpLCBp
biBpdHMgY3VycmVudCBmb3JtLCBpcyBpZ25vcmVkIGluIFNJUCByZXNwb25zZXMuICBUaGlzIHdh
cyBhDQo+ICAgICBkZXNpZ24gY2hvaWNlIGR1cmluZyBSRkMgNDQxMidzIGRldmVsb3BtZW50LiBU
aGlzIGlzIG5vdyBjb25zaWRlcmVkDQo+ICAgICBhIGJhZCBkZXNpZ24gY2hvaWNlIGluIGNlcnRh
aW4gc2NlbmFyaW9zLiAgVGhpcyBkb2N1bWVudCBjb3JyZWN0cw0KPiAgICAgUkZDIDQ0MTIncyBj
b21tdW5pY2F0aW9ucyBtb2RlbCBieSBvcHRpb25hbGx5IGFsbG93aW5nIGEgU0lQIHNlcnZlcg0K
PiAgICAgb3IgdXNlciBhZ2VudCBjbGllbnQgdG8gcHJvY2VzcyB0aGUgUmVzb3VyY2UtUHJpb3Jp
dHkgSGVhZGVyIGluIGENCj4gICAgIHJlc3BvbnNlLg0KPiANCj4gV29yayBJbiBQcm9ncmVzczog
ICBkcmFmdC1wb2xrLXNpcC1ycGgtbmV3LW5hbWVzcGFjZXMtLTAwDQo+IA0KPiBUaXRsZToNCj4g
ICAgIE5ldyBTZXNzaW9uIEluaXRpYXRpb24gUHJvdG9jb2wgUmVzb3VyY2UtUHJpb3JpdHkgSGVh
ZGVyIE5hbWVzcGFjZXMNCj4gICAgIGZvciB0aGUgRGVmZW5zZSBJbmZvcm1hdGlvbiBTeXN0ZW1z
IEFnZW5jeQ0KPiANCj4gQWJzdHJhY3Q6DQo+ICAgICBUaGlzIGRvY3VtZW50IGNyZWF0ZXMgYWRk
aXRpb25hbCBTZXNzaW9uIEluaXRpYXRpb24gUHJvdG9jb2wNCj4gICAgIFJlc291cmNlLVByaW9y
aXR5IGhlYWRlciBuYW1lc3BhY2VzLCB0byBiZSBJQU5BIHJlZ2lzdGVyZWQuICBUaGlzDQo+ICAg
ICBkb2N1bWVudCBpbnRlbmRzIHRvIHVwZGF0ZSBSRkMgNDQxMiwgYXMgYSBQcm9wb3NlZCBTdGFu
ZGFyZCBkb2N1bWVudA0KPiAgICAgaWYgcHVibGlzaGVkIGJ5IHRoZSBSRkMtRWRpdG9yLg0KPiAN
Cj4gSUVQUkVQIFdvcmtpbmcgR3JvdXANCj4gDQo+IFJGQyAzNDg3DQo+IA0KPiBUaXRsZToNCj4g
ICAgIFJlcXVpcmVtZW50cyBmb3IgUmVzb3VyY2UgUHJpb3JpdHkgTWVjaGFuaXNtcyBmb3IgdGhl
DQo+ICAgICBTZXNzaW9uIEluaXRpYXRpb24gUHJvdG9jb2wgKFNJUCkNCj4gDQo+IEFic3RyYWN0
Og0KPiAgICAgVGhpcyBkb2N1bWVudCBzdW1tYXJpemVzIHJlcXVpcmVtZW50cyBmb3IgcHJpb3Jp
dGl6aW5nIGFjY2VzcyB0bw0KPiAgICAgY2lyY3VpdC1zd2l0Y2hlZCBuZXR3b3JrLCBlbmQgc3lz
dGVtIGFuZCBwcm94eSByZXNvdXJjZXMgZm9yDQo+ICAgICBlbWVyZ2VuY3kgcHJlcGFyZWRuZXNz
IGNvbW11bmljYXRpb25zIHVzaW5nIHRoZSBTZXNzaW9uIEluaXRpYXRpb24NCj4gICAgIFByb3Rv
Y29sIChTSVApLg0KPiANCj4gUkZDIDM2ODkNCj4gDQo+IFRpdGxlOg0KPiAgICAgR2VuZXJhbCBS
ZXF1aXJlbWVudHMgZm9yDQo+ICAgICBFbWVyZ2VuY3kgVGVsZWNvbW11bmljYXRpb24gU2Vydmlj
ZSAoRVRTKQ0KPiANCj4gQWJzdHJhY3Q6DQo+ICAgICBUaGlzIGRvY3VtZW50IHByZXNlbnRzIGEg
bGlzdCBvZiBnZW5lcmFsIHJlcXVpcmVtZW50cyBpbiBzdXBwb3J0IG9mDQo+ICAgICBFbWVyZ2Vu
Y3kgVGVsZWNvbW11bmljYXRpb25zIFNlcnZpY2UgKEVUUykuICBTb2x1dGlvbnMgdG8gdGhlc2UN
Cj4gICAgIHJlcXVpcmVtZW50cyBhcmUgbm90IHByZXNlbnRlZCBpbiB0aGlzIGRvY3VtZW50LiAg
QWRkaXRpb25hbA0KPiAgICAgcmVxdWlyZW1lbnRzIHBlcnRhaW5pbmcgdG8gc3BlY2lmaWMgYXBw
bGljYXRpb25zLCBvciB0eXBlcyBvZg0KPiAgICAgYXBwbGljYXRpb25zLCBhcmUgdG8gYmUgc3Bl
Y2lmaWVkIGluIHNlcGFyYXRlIGRvY3VtZW50KHMpLg0KPiANCj4gUkZDIDM2OTANCj4gDQo+IFRp
dGxlOg0KPiAgICAgSVAgVGVsZXBob255IFJlcXVpcmVtZW50cyBmb3INCj4gICAgIEVtZXJnZW5j
eSBUZWxlY29tbXVuaWNhdGlvbiBTZXJ2aWNlIChFVFMpDQo+IA0KPiBBYnN0cmFjdDoNCj4gICAg
IFRoaXMgZG9jdW1lbnQgcHJlc2VudHMgYSBsaXN0IG9mIHJlcXVpcmVtZW50cyBpbiBzdXBwb3J0
IG9mIA0KRW1lcmdlbmN5DQo+ICAgICBUZWxlY29tbXVuaWNhdGlvbnMgU2VydmljZSAoRVRTKSB3
aXRoaW4gdGhlIGNvbnRleHQgb2YgSVAgdGVsZXBob255Lg0KPiAgICAgSXQgaXMgYW4gZXh0ZW5z
aW9uIHRvIHRoZSBnZW5lcmFsIHJlcXVpcmVtZW50cyBwcmVzZW50ZWQgaW4gUkZDIA0KMzY4OS4N
Cj4gICAgIFNvbHV0aW9ucyB0byB0aGVzZSByZXF1aXJlbWVudHMgYXJlIG5vdCBwcmVzZW50ZWQg
aW4gdGhpcyBkb2N1bWVudC4NCj4gDQo+IFJGQyA0MTkwDQo+IA0KPiBUaXRsZToNCj4gICAgIEZy
YW1ld29yayBmb3IgU3VwcG9ydGluZyBFbWVyZ2VuY3kgVGVsZWNvbW11bmljYXRpb25zDQo+ICAg
ICBTZXJ2aWNlIChFVFMpIGluIElQIFRlbGVwaG9ueQ0KPiANCj4gQWJzdHJhY3Q6DQo+ICAgICBU
aGlzIGRvY3VtZW50IHByZXNlbnRzIGEgZnJhbWV3b3JrIGZvciBzdXBwb3J0aW5nIGF1dGhvcml6
ZWQsDQo+ICAgICBlbWVyZ2VuY3ktcmVsYXRlZCBjb21tdW5pY2F0aW9uIHdpdGhpbiB0aGUgY29u
dGV4dCBvZiBJUCB0ZWxlcGhvbnkuDQo+ICAgICBXZSBwcmVzZW50IGEgc2VyaWVzIG9mIG9iamVj
dGl2ZXMgdGhhdCByZWZsZWN0IGEgZ2VuZXJhbCB2aWV3IG9mIGhvdw0KPiAgICAgYXV0aG9yaXpl
ZCBlbWVyZ2VuY3kgc2VydmljZSwgaW4gbGluZSB3aXRoIHRoZSBFbWVyZ2VuY3kNCj4gICAgIFRl
bGVjb21tdW5pY2F0aW9ucyBTZXJ2aWNlIChFVFMpLCBzaG91bGQgYmUgcmVhbGl6ZWQgd2l0aGlu
IHRvZGF5J3MNCj4gICAgIElQIGFyY2hpdGVjdHVyZSBhbmQgc2VydmljZSBtb2RlbHMuICBGcm9t
IHRoZXNlIG9iamVjdGl2ZXMsIHdlDQo+ICAgICBwcmVzZW50IGEgY29ycmVzcG9uZGluZyBzZXQg
b2YgcHJvdG9jb2xzIGFuZCBjYXBhYmlsaXRpZXMsIHdoaWNoDQo+ICAgICBwcm92aWRlIGEgbW9y
ZSBzcGVjaWZpYyBzZXQgb2YgcmVjb21tZW5kYXRpb25zIHJlZ2FyZGluZyBleGlzdGluZw0KPiAg
ICAgSUVURiBwcm90b2NvbHMuICBGaW5hbGx5LCB3ZSBwcmVzZW50IHR3byBzY2VuYXJpb3MgdGhh
dCBhY3QgYXMNCj4gICAgIGd1aWRpbmcgbW9kZWxzIGZvciB0aGUgb2JqZWN0aXZlcyBhbmQgZnVu
Y3Rpb25zIGxpc3RlZCBpbiB0aGlzDQo+ICAgICBkb2N1bWVudC4gIFRoZXNlIG1vZGVscywgY291
cGxlZCB3aXRoIGFuIGV4YW1wbGUgb2YgYW4gZXhpc3RpbmcNCj4gICAgIHNlcnZpY2UgaW4gdGhl
IFB1YmxpYyBTd2l0Y2hlZCBUZWxlcGhvbmUgTmV0d29yayAoUFNUTiksIGNvbnRyaWJ1dGUNCj4g
ICAgIHRvIGEgY29uc3RyYWluZWQgc29sdXRpb24gc3BhY2UuDQo+IA0KPiBSRkMgNDM3NQ0KPiAN
Cj4gVGl0bGU6DQo+ICAgICBFbWVyZ2VuY3kgVGVsZWNvbW11bmljYXRpb25zIFNlcnZpY2VzIChF
VFMpIFJlcXVpcmVtZW50cw0KPiAgICAgZm9yIGEgU2luZ2xlIEFkbWluaXN0cmF0aXZlIERvbWFp
bg0KPiANCj4gQWJzdHJhY3Q6DQo+ICAgICBUaGlzIGRvY3VtZW50IHByZXNlbnRzIGEgbGlzdCBv
ZiByZXF1aXJlbWVudHMgaW4gc3VwcG9ydCBvZiANCkVtZXJnZW5jeQ0KPiAgICAgVGVsZWNvbW11
bmljYXRpb25zIFNlcnZpY2UgKEVUUykgd2l0aGluIGEgc2luZ2xlIGFkbWluaXN0cmF0aXZlDQo+
ICAgICBkb21haW4uICBUaGlzIGRvY3VtZW50IGZvY3VzZXMgb24gYSBzcGVjaWZpYyBzZXQgb2Yg
YWRtaW5pc3RyYXRpdmUNCj4gICAgIGNvbnN0cmFpbnRzIGFuZCBzY29wZS4gIFNvbHV0aW9ucyB0
byB0aGVzZSByZXF1aXJlbWVudHMgYXJlIG5vdA0KPiAgICAgcHJlc2VudGVkIGluIHRoaXMgZG9j
dW1lbnQuDQo+IA0KPiANCj4gVFNWIFdvcmtpbmcgR3JvdXANCj4gDQo+IFJGQyA0NTQyDQo+IA0K
PiBUaXRsZToNCj4gICAgIEltcGxlbWVudGluZyBhbiBFbWVyZ2VuY3kgVGVsZWNvbW11bmljYXRp
b25zIFNlcnZpY2UgKEVUUykNCj4gICAgIGZvciBSZWFsLVRpbWUgU2VydmljZXMgaW4gdGhlIElu
dGVybmV0IFByb3RvY29sIFN1aXRlDQo+IA0KPiBBYnN0cmFjdDoNCj4gICAgIFJGQ3MgMzY4OSBh
bmQgMzY5MCBkZXRhaWwgcmVxdWlyZW1lbnRzIGZvciBhbiBFbWVyZ2VuY3kNCj4gICAgIFRlbGVj
b21tdW5pY2F0aW9ucyBTZXJ2aWNlIChFVFMpLCBvZiB3aGljaCBhbiBJbnRlcm5ldCBFbWVyZ2Vu
Y3kNCj4gICAgIFByZXBhcmVkbmVzcyBTZXJ2aWNlIChJRVBTKSB3b3VsZCBiZSBhIHBhcnQuICBT
b21lIG9mIHRoZXNlIHR5cGVzIG9mDQo+ICAgICBzZXJ2aWNlcyByZXF1aXJlIGNhbGwgcHJlZW1w
dGlvbjsgb3RoZXJzIHJlcXVpcmUgY2FsbCBxdWV1aW5nIG9yDQo+ICAgICBvdGhlciBtZWNoYW5p
c21zLiAgSUVQUyByZXF1aXJlcyBhIENhbGwgQWRtaXNzaW9uIENvbnRyb2wgKENBQykNCj4gICAg
IHByb2NlZHVyZSBhbmQgYSBQZXIgSG9wIEJlaGF2aW9yIChQSEIpIGZvciB0aGUgZGF0YSB0aGF0
IG1lZXQgdGhlDQo+ICAgICBuZWVkcyBvZiB0aGlzIGFyY2hpdGVjdHVyZS4gIFN1Y2ggYSBDQUMg
cHJvY2VkdXJlIGFuZCBQSEIgaXMNCj4gICAgIGFwcHJvcHJpYXRlIHRvIGFueSBzZXJ2aWNlIHRo
YXQgbWlnaHQgdXNlIEguMzIzIG9yIFNJUCB0byBzZXQgdXANCj4gICAgIHJlYWwtdGltZSBzZXNz
aW9ucy4gIFRoZSBrZXkgcmVxdWlyZW1lbnQgaXMgdG8gZ3VhcmFudGVlIGFuIGVsZXZhdGVkDQo+
ICAgICBwcm9iYWJpbGl0eSBvZiBjYWxsIGNvbXBsZXRpb24gdG8gYW4gYXV0aG9yaXplZCB1c2Vy
IGluIHRpbWUgb2YNCj4gICAgIGNyaXNpcy4NCj4gDQo+ICAgICBUaGlzIGRvY3VtZW50IHByaW1h
cmlseSBkaXNjdXNzZXMgc3VwcG9ydGluZyBFVFMgaW4gdGhlIGNvbnRleHQgb2YNCj4gICAgIHRo
ZSBVUyBHb3Zlcm5tZW50IGFuZCBOQVRPLCBiZWNhdXNlIGl0IGZvY3VzZXMgb24gdGhlIE11bHRp
LUxldmVsDQo+ICAgICBQcmVjZWRlbmNlIGFuZCBQcmVlbXB0aW9uIChNTFBQKSBhbmQgR292ZXJu
bWVudCBFbWVyZ2VuY3kNCj4gICAgIFRlbGVjb21tdW5pY2F0aW9uIFNlcnZpY2UgKEdFVFMpIHN0
YW5kYXJkcy4gIFRoZSBhcmNoaXRlY3R1cmVzDQo+ICAgICBkZXNjcmliZWQgaGVyZSBhcmUgYXBw
bGljYWJsZSBiZXlvbmQgdGhlc2Ugb3JnYW5pemF0aW9ucy4NCj4gDQo+IFdvcmsgSW4gUHJvZ3Jl
c3M6ICAgZHJhZnQtaWV0Zi10c3Z3Zy1lbWVyZ2VuY3ktcnN2cC0wMy50eHQNCj4gDQo+IFRpdGxl
Og0KPiAgICAgUmVzb3VyY2UgUmVTZXJWYXRpb24gUHJvdG92b2wgKFJTVlApIEV4dGVuc2lvbnMg
Zm9yDQo+ICAgICBFbWVyZ2VuY3kgU2VydmljZXMNCj4gDQo+IEFic3RyYWN0Og0KPiAgICAgQW4g
RW1lcmdlbmN5IFRlbGVjb21tdW5pY2F0aW9ucyBTZXJ2aWNlIChFVFMpIHJlcXVpcmVzIHRoZSBh
YmlsaXR5IA0KdG8NCj4gICAgIHByb3ZpZGUgYW4gZWxldmF0ZWQgcHJvYmFiaWxpdHkgb2Ygc2Vz
c2lvbiBlc3RhYmxpc2htZW50IHRvIGFuDQo+ICAgICBhdXRob3JpemVkIHVzZXIgaW4gdGltZXMg
b2YgbmV0d29yayBjb25nZXN0aW9uICh0eXBpY2FsbHksIGR1cmluZyBhDQo+ICAgICBjcmlzaXMp
LiBXaGVuIHN1cHBvcnRlZCBvdmVyIHRoZSBJbnRlcm5ldCBQcm90b2NvbCBzdWl0ZSwgdGhpcyBt
YXkgDQpiZQ0KPiAgICAgZmFjaWxpdGF0ZWQgdGhyb3VnaCBhIG5ldHdvcmsgbGF5ZXIgYWRtaXNz
aW9uIGNvbnRyb2wgc29sdXRpb24sIA0Kd2hpY2gNCj4gICAgIHN1cHBvcnRzIHByaW9yaXRpemVk
IGFjY2VzcyB0byByZXNvdXJjZXMgKGUuZy4sIGJhbmR3aWR0aCkuIFRoZXNlDQo+ICAgICByZXNv
dXJjZXMgbWF5IGJlIGV4cGxpY2l0bHkgc2V0IGFzaWRlIGZvciBlbWVyZ2VuY3kgc2VydmljZXMs
IG9yIA0KdGhleQ0KPiAgICAgbWF5IGJlIHNoYXJlZCB3aXRoIG90aGVyIHNlc3Npb25zLg0KPiAN
Cj4gICAgVGhpcyBkb2N1bWVudCBzcGVjaWZpZXMgUlNWUCBleHRlbnNpb25zIHRoYXQgY2FuIGJl
IHVzZWQgdG8gc3VwcG9ydA0KPiAgICAgc3VjaCBhbiBhZG1pc3Npb24gcHJpb3JpdHkgY2FwYWJp
bGl0eSBhdCB0aGUgbmV0d29yayBsYXllci4gTm90ZSANCnRoYXQNCj4gICAgIHRoZXNlIGV4dGVu
c2lvbnMgcmVwcmVzZW50IG9uZSBwb3NzaWJsZSBzb2x1dGlvbiBjb21wb25lbnQgaW4NCj4gICAg
IHNhdGlzZnlpbmcgRVRTIHJlcXVpcmVtZW50cy4gT3RoZXIgc29sdXRpb24gY29tcG9uZW50cywg
b3Igb3RoZXINCj4gICAgIHNvbHV0aW9ucywgYXJlIG91dHNpZGUgdGhlIHNjb3BlIG9mIHRoaXMg
ZG9jdW1lbnQuDQo+IA0KPiBOU0lTIFdvcmtpbmcgR3JvdXANCj4gDQo+IFdvcmsgSW4gUHJvZ3Jl
c3M6IGRyYWZ0LWlldGYtbnNpcy1xb3MtbnNscC0xNC50eHQNCj4gDQo+IFRpdGxlOg0KPiAgICAg
TlNMUCBmb3IgUXVhbGl0eS1vZi1TZXJ2aWNlIFNpZ25hbGluZw0KPiANCj4gQWJzdHJhY3Q6DQo+
ICAgICBUaGlzIHNwZWNpZmljYXRpb24gZGVzY3JpYmVzIHRoZSBOU0lTIFNpZ25hbGluZyBMYXll
ciBQcm90b2NvbA0KPiAgICAgKE5TTFApIGZvciBzaWduYWxpbmcgUW9TIHJlc2VydmF0aW9ucyBp
biB0aGUgSW50ZXJuZXQuICBJdCBpcyBpbg0KPiAgICAgYWNjb3JkYW5jZSB3aXRoIHRoZSBmcmFt
ZXdvcmsgYW5kIHJlcXVpcmVtZW50cyBkZXZlbG9wZWQgaW4gTlNJUy4NCj4gICAgIFRvZ2V0aGVy
IHdpdGggR0lTVCwgaXQgcHJvdmlkZXMgZnVuY3Rpb25hbGl0eSBzaW1pbGFyIHRvIFJTVlAgYW5k
DQo+ICAgICBleHRlbmRzIGl0LiAgVGhlIFFvUyBOU0xQIGlzIGluZGVwZW5kZW50IG9mIHRoZSB1
bmRlcmx5aW5nIFFvUw0KPiAgICAgc3BlY2lmaWNhdGlvbiBvciBhcmNoaXRlY3R1cmUgYW5kIHBy
b3ZpZGVzIHN1cHBvcnQgZm9yIGRpZmZlcmVudA0KPiAgICAgcmVzZXJ2YXRpb24gbW9kZWxzLiBJ
dCBpcyBzaW1wbGlmaWVkIGJ5IHRoZSBlbGltaW5hdGlvbiBvZiBzdXBwb3J0DQo+ICAgICBmb3Ig
bXVsdGljYXN0IGZsb3dzLiBUaGlzIHNwZWNpZmljYXRpb24gZXhwbGFpbnMgdGhlIG92ZXJhbGwN
Cj4gICAgIHByb3RvY29sIGFwcHJvYWNoLCBkZXNpZ24gZGVjaXNpb25zIG1hZGUgYW5kIHByb3Zp
ZGVzIGV4YW1wbGVzLiAgSXQNCj4gICAgIHNwZWNpZmllcyBvYmplY3QsIG1lc3NhZ2UgIGZvcm1h
dHMgYW5kIHByb2Nlc3NpbmcgcnVsZXMuDQo+IA0KPiAtLSANCj4gDQo+IE1hZ251cyBXZXN0ZXJs
dW5kDQo+IA0KPiBJRVRGIFRyYW5zcG9ydCBBcmVhIERpcmVjdG9yICYgVFNWV0cgQ2hhaXINCj4g
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLQ0KPiBNdWx0aW1lZGlhIFRlY2hub2xvZ2llcywgRXJpY3Nzb24gUmVzZWFy
Y2ggRUFCL1RWTS9NDQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gRXJpY3Nzb24gQUIgICAgICAgICAgICAg
ICAgfCBQaG9uZSArNDYgOCA0MDQ4Mjg3DQo+IFRvcnNoYW1zZ2F0YW4gMjMgICAgICAgICAgIHwg
RmF4ICAgKzQ2IDggNzU3NTU1MA0KPiBTLTE2NCA4MCBTdG9ja2hvbG0sIFN3ZWRlbiB8IG1haWx0
bzogbWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nzb24uY29tDQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gDQo+
IA0KDQo=
--=_alternative 0055890785257329_=
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPk1hZ251cyw8YnI+DQo8YnI+DQpZ
b3UgbWlnaHQgd2FudCB0byBhZGQtPC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBmYWNl
PSJzYW5zLXNlcmlmIj5kcmFmdC1wb2xrLXRzdndnLXNpZ25hbGVkLWRvbWFpbi1pZC0wMC50eHQ8
L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPmFuZCA8YnI+DQpkcmFm
dC1wb2xrLWVjcml0LWxvY2FsLWVtZXJnZW5jeS1ycGgtbmFtZXNwYWNlLTAxLnR4dDwvZm9udD4N
Cjxicj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+KEJvdGggd2VyZSBvbiB0
aGUgYWdlbmRhIGFuZCBkaXNjdXNzZWQuKTwvZm9udD4NCjxicj4NCjxicj48Zm9udCBzaXplPTIg
ZmFjZT0ic2Fucy1zZXJpZiI+QW5kIG1heWJlPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNl
PSJzYW5zLXNlcmlmIj5kcmFmdC1jYXJsYmVyZy10cmlwLWF0dHJpYnV0ZS1ycC0wMg0KPC9mb250
Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4odGhvdWdoIEkgZGlk
IG5vdCBzZWUgaXQgb24gdGhlIGFnZW5kYSk8L2ZvbnQ+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0y
IGZhY2U9InNhbnMtc2VyaWYiPkphbmV0PC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBm
YWNlPSJzYW5zLXNlcmlmIj5QUyw8L2ZvbnQ+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9
InNhbnMtc2VyaWYiPk15IHNwZWxsaW5nIGNoZWNrZXIgc2F5cyAmcXVvdDtMaWFpc2lvbiZxdW90
Ow0Kc2hvdWxkIGJlICZxdW90O0xpYWlzb24mcXVvdDssIGJ1dCBpdCBtYXkgYmUgYSBVUyBjZW50
cmljIGRpY3Rpb25hcnkuPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlm
Ij5KPC9mb250Pg0KPGJyPjxmb250IHNpemU9Mj48dHQ+TWFnbnVzIFdlc3Rlcmx1bmQgJmx0O21h
Z251cy53ZXN0ZXJsdW5kQGVyaWNzc29uLmNvbSZndDsNCndyb3RlIG9uIDA3LzMxLzIwMDcgMTE6
MjE6MjAgQU06PGJyPg0KPGJyPg0KJmd0OyBIaTxicj4NCiZndDsgPGJyPg0KJmd0OyBUaGlzIGlz
IHRoZSBkcmFmdCBmb3IgYSBsaWFpc29uIHJlc3BvbnNlIHRvIGJlIHNlbnQgdG8gU0cgMTMgb2Yg
dGhlDQo8YnI+DQomZ3Q7IElUVS1UIGZyb20gdGhlIFRTVldHLCBOU0lTLCBTSVAgYW5kIFNJUFBJ
TkcgV0dzLiBQbGVhc2UgcHJvdmlkZSBhbnkNCjxicj4NCiZndDsgY29tbWVudHMgYXQgdGhlIGxh
dGVzdCBieSB0aGUgMTR0aCBvZiBBdWd1c3QuIEFmdGVyIHRoYXQgd2Ugd2lsbCBhZGRyZXNzDQo8
YnI+DQomZ3Q7IGFueSByYWlzZWQgY29tbWVudHMgYW5kIHNlbmQgdGhlIGxpYWlzb24gdG8gSVRV
LVQgYmVmb3JlIHRoZSBlbmQgb2YNCkF1Z3VzdC48YnI+DQomZ3Q7IDxicj4NCiZndDsgU3VibWlz
c2lvbjxicj4NCiZndDsgRGF0ZTogJm5ic3A7ICZuYnNwOyAmbmJzcDsmbHQ7dGJkJmd0OywgMjAw
Nzxicj4NCiZndDsgPGJyPg0KJmd0OyBGcm9tOiAmbmJzcDsgJm5ic3A7ICZuYnNwOyBJRVRGIFdv
cmtpbmcgZ3JvdXBzIFRTVldHLCBOU0lTLCBTSVAgYW5kDQpTSVBQSU5HPGJyPg0KJmd0OyA8YnI+
DQomZ3Q7IFRvOiAmbmJzcDsgJm5ic3A7ICZuYnNwO0dlb3JnZXMgU2ViZWsgJm5ic3A7Jmx0O3Rz
YnNnMTNAaXR1LmludCZndDsNCiw8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IEtlaXRo
IEtuaWdodHNvbiAmbHQ7a2drQGlncy5uZXQmZ3Q7PGJyPg0KJmd0OyA8YnI+DQomZ3Q7IENjOiAm
bmJzcDsgJm5ic3A7ICZuYnNwO01hZ251cyBXZXN0ZXJsdW5kICZsdDttYWdudXMud2VzdGVybHVu
ZEBlcmljc3Nvbi5jb20mZ3Q7LDxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtMYXJzDQpFZ2dlcnQgJmx0O2xhcnMu
ZWdnZXJ0QG5va2lhLmNvbSZndDssPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO0phbWVzDQpQb2xrICZsdDtqbXBv
bGtAY2lzY28uY29tJmd0Oyw8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7TWFydGluDQpTdGllbWVybGluZyAmbHQ7
c3RpZW1lcmxpbmdAbmV0bGFiLm5lYy5kZSZndDssPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO0pvaG4NCkxvdWdo
bmV5ICZsdDtqb2huLmxvdWdobmV5QG5va2lhLmNvbSZndDs8YnI+DQomZ3Q7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7RGVhbg0K
V2lsbGlzICZsdDtkZWFuLndpbGxpc0Bzb2Z0YXJtb3IuY29tJmd0Oyw8YnI+DQomZ3Q7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
S2VpdGgNCkRyYWdlICZsdDtkcmFnZUBhbGNhdGVsLWx1Y2VudC5jb20mZ3Q7LDxicj4NCiZndDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDtNYXJ5DQpCYXJuZXMgJmx0O21hcnkuYmFybmVzQG5vcnRlbC5jb20mZ3Q7LDxicj4NCiZn
dDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDtHb256YWxvDQpDYW1hcmlsbG8gJmx0O2dvbnphbG8uY2FtYXJpbGxvQGVyaWNzc29u
LmNvbSZndDssPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO1Njb3R0DQpCcmFkbmVyICZsdDtzb2JAaGFydmFyZC5l
ZHUmZ3Q7LDxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtLaW1iZXJseQ0KS2luZyAmbHQ7a3NraW5nQG1pdHJlLm9y
ZyZndDssPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwO1Njb3R0DQpCcmltICZsdDtzd2JAZW1wbG95ZWVzLm9yZyZn
dDs8YnI+DQomZ3Q7IDxicj4NCiZndDsgUmVzcG9uc2U8YnI+DQomZ3Q7IENvbnRhY3Q6ICZuYnNw
OyBUU1YgV0cgKHRzdi1jaGFpcnNAdG9vbHMuaWV0Zi5vcmcpPGJyPg0KJmd0OyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyBOU0lTIChuc2lzLWNoYWlyc0B0b29scy5pZXRmLm9yZyk8YnI+DQomZ3Q7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7IFNJUFBJTkcgKHNpcHBpbmctY2hhaXJzQHRvb2xzLmlldGYub3Jn
KTxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgU0lQIChzaXAtY2hhaXJzQHRvb2xzLmll
dGYub3JnKTxicj4NCiZndDsgJm5ic3A7ICZuYnNwOzxicj4NCiZndDsgUHVycG9zZTogJm5ic3A7
ICZuYnNwO1Jlc3BvbnNlIHRvIExpYWlzb24gUmVxdWVzdDxicj4NCiZndDsgPGJyPg0KJmd0OyBE
ZWFkbGluZTogJm5ic3A7IE5vbmU8YnI+DQomZ3Q7IDxicj4NCiZndDsgVGl0bGU6IFJlc3BvbnNl
IHRvIGxpYWlzb24gcmVxdWVzdCBmcm9tIElUVS1UIFN0dWR5IEdyb3VwIDEzIHdvcmsNCm9uIDxi
cj4NCiZndDsgZW1lcmdlbmN5IHRlbGVjb21tdW5pY2F0aW9uczxicj4NCiZndDsgPGJyPg0KJmd0
OyBUaGlzIGlzIGEgcmVzcG9uc2UgdG8gdGhlIGxpYWlzb24gcmVxdWVzdCBtYWRlIGJ5IFEzLzEz
IHJlZ2FyZGluZw0KPGJyPg0KJmd0OyBlbWVyZ2VuY3kgdGVsZWNvbW11bmljYXRpb25zIChSRUY6
IE5HTi1HU0kvRE9DIOKAkyA2MCBSZXYuMikuIFdlIHdvdWxkDQo8YnI+DQomZ3Q7IGZpcnN0IGxp
a2UgdG8gYXBvbG9naXplIGZvciBmYWlsaW5nIHRvIG1lZXQgdGhlIGRlYWRsaW5lIGluIHJlc3Bv
bmRpbmcuDQo8YnI+DQomZ3Q7IFdlIGRvIGhvcGUgdGhhdCB0aGUgbGF0ZSBhbnN3ZXIgc3RpbGwg
Y2FuIGJlIG9mIHNvbWUgdXNlLjxicj4NCiZndDsgPGJyPg0KJmd0OyBUaGUgbGlhaXNvbiByZXF1
ZXN0IHdhcyBtYWRlIHRvIHRoZSBmb2xsb3dpbmcgd29ya2luZyBncm91cHMgKFdHKToNCjxicj4N
CiZndDsgSUVQUkVQLCBUU1ZXRywgYW5kIE5TSVMuIFNpbmNlIHRoZSByZXF1ZXN0IHdhcyBzZW50
IHRoZSBJRVBSRVAgV0cNCmhhcyA8YnI+DQomZ3Q7IGNvbmNsdWRlZC4gSW4gYWRkaXRpb24gdG8g
dGhlIFdHcyBmcm9tIHdoaWNoIGluZm9ybWF0aW9uIHdhcyByZXF1ZXN0ZWQsDQo8YnI+DQomZ3Q7
IHdlIGFsc28gdGhpbmsgdGhhdCB3b3JrIHBlcmZvcm1lZCBieSB0aGUgU0lQIGFuZCBTSVBQSU5H
IFdHIG1heSBiZQ0Kb2YgPGJyPg0KJmd0OyByZWxldmFuY2UuPGJyPg0KJmd0OyA8YnI+DQomZ3Q7
IFB1cnN1YW50IHRvIElUVS1UIFN0dWR5IEdyb3VwIDEzIHJlcXVlc3QgZm9yIGluZm9ybWF0aW9u
IG9uIHJlbGV2YW50DQphbmQgPGJyPg0KJmd0OyByZWxhdGVkIHdvcmsgaW4gdGhlIElFVEYgcmVn
YXJkaW5nIGVtZXJnZW5jeSBjb21tdW5pY2F0aW9ucywgd2UgbGlzdA0KPGJyPg0KJmd0OyBiZWxv
dyBSRkNzIGFuZCB3b3JrcyBpbiBwcm9ncmVzcyB0aGF0IHdlIGZlZWwgbWF5IGJlIG9mIGludGVy
ZXN0IHRvDQp5b3VyIDxicj4NCiZndDsgZ3JvdXAuICZuYnNwO1NvbWUgb2YgdGhlIGNvbXBsZXRl
ZCB3b3JrIGlzIEluZm9ybWF0aW9uYWwsIGFuZCBvdGhlcnMNCmFyZSBpbiA8YnI+DQomZ3Q7IHRo
ZSBjYXRlZ29yeSBvZiBTdGFuZGFyZHMgVHJhY2suPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IFEuMy8x
MyBhbHNvIHJlcXVlc3RlZCB0aGF0IHdlIGtlZXAgeW91IGluZm9ybWVkIG9mIGFueSBkZXZlbG9w
bWVudHMNCmluIDxicj4NCiZndDsgcmVnYXJkcyB0byBlbWVyZ2VuY3kgdGVsZWNvbW11bmljYXRp
b25zLiBJbiB0aG9zZSByZWdhcmRzIHdlIHdvdWxkDQpsaWtlIDxicj4NCiZndDsgdG8gbWFrZSB5
b3UgYXdhcmUgdGhhdCBJRVRGIG1haWxpbmcgbGlzdCBwYXJ0aWNpcGF0aW9uIGFuZCBkb2N1bWVu
dA0KPGJyPg0KJmd0OyBpbmZvcm1hdGlvbiBpcyBmcmVlIGFuZCBvcGVuIGZvciBhbnlvbmUuIEFs
bG93aW5nIHBhcnRpY2lwYW50cyBpbg0KUS4zLzEzIDxicj4NCiZndDsgdG8ga2VlcCB0aGVtIHNl
bHZlcyBpbmZvcm1lZCBvZiBhbnkgZGV2ZWxvcG1lbnRzLiBJZiBRLjMvMTMgZGVzaXJlDQp0byA8
YnI+DQomZ3Q7IGdldCBmdXJ0aGVyIGluZm9ybWF0aW9uIGFib3V0IHNwZWNpZmljIG9uZ29pbmcg
d29yaywgdGhlbiBwbGVhc2Ugc2VuZA0KYSA8YnI+DQomZ3Q7IGxpYWlzb24gcmVxdWVzdCB0byB0
aGUgcmVzcG9uc2libGUgV0cgZm9yIHRob3NlIHNwZWNpZmljIGRvY3VtZW50cy48YnI+DQomZ3Q7
IDxicj4NCiZndDsgVGhlIGZvbGxvd2luZyBsaXN0IGlzIGRpdmlkZWQgdW5kZXIgdGhlIGFzc29j
aWF0ZWQgd29ya2luZyBncm91cHMNCmZyb20gPGJyPg0KJmd0OyB3aGljaCB0aGUgd29yayBoYXMg
YmVlbiBkb25lIHdpdGhpbiB0aGUgSUVURi48YnI+DQomZ3Q7IDxicj4NCiZndDsgPGJyPg0KJmd0
OyBTSVAgV29ya2luZyBHcm91cDxicj4NCiZndDsgPGJyPg0KJmd0OyBSRkMgNDQxMTxicj4NCiZn
dDsgPGJyPg0KJmd0OyBUaXRsZTo8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgRXh0ZW5kaW5nIHRo
ZSBTZXNzaW9uIEluaXRpYXRpb24gUHJvdG9jb2wgKFNJUCk8YnI+DQomZ3Q7ICZuYnNwOyAmbmJz
cDsgUmVhc29uIEhlYWRlciBmb3IgUHJlZW1wdGlvbiBFdmVudHM8YnI+DQomZ3Q7IDxicj4NCiZn
dDsgQWJzdHJhY3Q6PGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7VGhpcyBkb2N1bWVudCBwcm9wb3Nl
cyBhbiBJQU5BIFJlZ2lzdHJhdGlvbiBleHRlbnNpb24NCnRvIHRoZSBTZXNzaW9uPGJyPg0KJmd0
OyAmbmJzcDsgJm5ic3A7IEluaXRpYXRpb24gUHJvdG9jb2wgKFNJUCkgUmVhc29uIEhlYWRlciB0
byBiZSBpbmNsdWRlZA0KaW4gYSBCWUU8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgTWV0aG9kIFJl
cXVlc3QgYXMgYSByZXN1bHQgb2YgYSBzZXNzaW9uIHByZWVtcHRpb24gZXZlbnQsDQplaXRoZXIg
YXQgYTxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyB1c2VyIGFnZW50IChVQSksIG9yIHNvbWV3aGVy
ZSBpbiB0aGUgbmV0d29yayBpbnZvbHZpbmcNCmE8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgcmVz
ZXJ2YXRpb24tYmFzZWQgcHJvdG9jb2wgc3VjaCBhcyB0aGUgUmVzb3VyY2UgUmVTZXJWYXRpb24N
ClByb3RvY29sPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7IChSU1ZQKSBvciBOZXh0IFN0ZXBzIGlu
IFNpZ25hbGluZyAoTlNJUykuICZuYnNwO1RoaXMNCmRvY3VtZW50IGRvZXMgbm90PGJyPg0KJmd0
OyAmbmJzcDsgJm5ic3A7IGF0dGVtcHQgdG8gYWRkcmVzcyByb3V0ZXJzIGZhaWxpbmcgaW4gdGhl
IHBhY2tldCBwYXRoOw0KaW5zdGVhZCwgaXQ8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgYWRkcmVz
c2VzIGEgZGVsaWJlcmF0ZSB0ZWFyIGRvd24gb2YgYSBmbG93IGJldHdlZW4gVUFzLA0KYW5kIGlu
Zm9ybXM8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgdGhlIHRlcm1pbmF0ZWQgVUEocykgd2l0aCBh
biBpbmRpY2F0aW9uIG9mIHdoYXQgb2NjdXJyZWQuPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IFJGQyA0
NDEyPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IFRpdGxlOjxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyBD
b21tdW5pY2F0aW9ucyBSZXNvdXJjZSBQcmlvcml0eSBmb3IgdGhlIFNlc3Npb24gSW5pdGlhdGlv
bjxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyBQcm90b2NvbCAoU0lQKTxicj4NCiZndDsgPGJyPg0K
Jmd0OyBBYnN0cmFjdDo8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgVGhpcyBkb2N1bWVudCBkZWZp
bmVzIHR3byBuZXcgU2Vzc2lvbiBJbml0aWF0aW9uIFByb3RvY29sDQooU0lQKTxicj4NCiZndDsg
Jm5ic3A7ICZuYnNwOyBoZWFkZXIgZmllbGRzIGZvciBjb21tdW5pY2F0aW5nIHJlc291cmNlIHBy
aW9yaXR5LCBuYW1lbHksPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7ICZxdW90O1Jlc291cmNlLVBy
aW9yaXR5JnF1b3Q7IGFuZCAmcXVvdDtBY2NlcHQtUmVzb3VyY2UtUHJpb3JpdHkmcXVvdDsuDQom
bmJzcDtUaGU8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgJnF1b3Q7UmVzb3VyY2UtUHJpb3JpdHkm
cXVvdDsgaGVhZGVyIGZpZWxkIGNhbiBpbmZsdWVuY2UNCnRoZSBiZWhhdmlvciBvZiBTSVA8YnI+
DQomZ3Q7ICZuYnNwOyAmbmJzcDsgdXNlciBhZ2VudHMgKHN1Y2ggYXMgdGVsZXBob25lIGdhdGV3
YXlzIGFuZCBJUCB0ZWxlcGhvbmVzKQ0KYW5kIFNJUDxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyBw
cm94aWVzLiAmbmJzcDtJdCBkb2VzIG5vdCBkaXJlY3RseSBpbmZsdWVuY2UgdGhlIGZvcndhcmRp
bmcNCmJlaGF2aW9yIG9mPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7IElQIHJvdXRlcnMuPGJyPg0K
Jmd0OyA8YnI+DQomZ3Q7IDxicj4NCiZndDsgPGJyPg0KJmd0OyBTSVBQSU5HIFdvcmtpbmcgR3Jv
dXA8YnI+DQomZ3Q7IDxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyBUaGUgYmVsb3cgdHdvIGRvY3Vt
ZW50cyBhcmUgcHJvcG9zZWQgd29yayBpdGVtcyBub3QNCnlldCBhY2NlcHRlZCBhczxicj4NCiZn
dDsgJm5ic3A7ICZuYnNwOyBJRVRGIFdHIGl0ZW1zIGJ1dCBhcmUgbGlrZWx5IG9mIGludGVyZXN0
IGFzIHRoZXkgdXBkYXRlDQpSRkMgNDQxMi48YnI+DQomZ3Q7IDxicj4NCiZndDsgV29yayBJbiBQ
cm9ncmVzczogJm5ic3A7IGRyYWZ0LXBvbGstc2lwLXJwaC1pbi1yZXNwb25zZXMtMDA8YnI+DQom
Z3Q7IDxicj4NCiZndDsgVGl0bGU6PGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7IEFsbG93aW5nIFNJ
UCBSZXNvdXJjZSBQcmlvcml0eSBIZWFkZXIgaW4gU0lQIFJlc3BvbnNlczxicj4NCiZndDsgPGJy
Pg0KJmd0OyBBYnN0cmFjdDo8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgVGhlIFNlc3Npb24gSW5p
dGlhdGlvbiBQcm90b2NvbCAoU0lQKSBSZXNvdXJjZSBQcmlvcml0eQ0KSGVhZGVyPGJyPg0KJmd0
OyAmbmJzcDsgJm5ic3A7IChSUEgpLCBpbiBpdHMgY3VycmVudCBmb3JtLCBpcyBpZ25vcmVkIGlu
IFNJUCByZXNwb25zZXMuDQombmJzcDtUaGlzIHdhcyBhPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7
IGRlc2lnbiBjaG9pY2UgZHVyaW5nIFJGQyA0NDEyJ3MgZGV2ZWxvcG1lbnQuIFRoaXMgaXMNCm5v
dyBjb25zaWRlcmVkPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7IGEgYmFkIGRlc2lnbiBjaG9pY2Ug
aW4gY2VydGFpbiBzY2VuYXJpb3MuICZuYnNwO1RoaXMNCmRvY3VtZW50IGNvcnJlY3RzPGJyPg0K
Jmd0OyAmbmJzcDsgJm5ic3A7IFJGQyA0NDEyJ3MgY29tbXVuaWNhdGlvbnMgbW9kZWwgYnkgb3B0
aW9uYWxseSBhbGxvd2luZw0KYSBTSVAgc2VydmVyPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7IG9y
IHVzZXIgYWdlbnQgY2xpZW50IHRvIHByb2Nlc3MgdGhlIFJlc291cmNlLVByaW9yaXR5DQpIZWFk
ZXIgaW4gYTxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyByZXNwb25zZS48YnI+DQomZ3Q7IDxicj4N
CiZndDsgV29yayBJbiBQcm9ncmVzczogJm5ic3A7IGRyYWZ0LXBvbGstc2lwLXJwaC1uZXctbmFt
ZXNwYWNlcy0tMDA8YnI+DQomZ3Q7IDxicj4NCiZndDsgVGl0bGU6PGJyPg0KJmd0OyAmbmJzcDsg
Jm5ic3A7IE5ldyBTZXNzaW9uIEluaXRpYXRpb24gUHJvdG9jb2wgUmVzb3VyY2UtUHJpb3JpdHkg
SGVhZGVyDQpOYW1lc3BhY2VzPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7IGZvciB0aGUgRGVmZW5z
ZSBJbmZvcm1hdGlvbiBTeXN0ZW1zIEFnZW5jeTxicj4NCiZndDsgPGJyPg0KJmd0OyBBYnN0cmFj
dDo8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgVGhpcyBkb2N1bWVudCBjcmVhdGVzIGFkZGl0aW9u
YWwgU2Vzc2lvbiBJbml0aWF0aW9uDQpQcm90b2NvbDxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyBS
ZXNvdXJjZS1Qcmlvcml0eSBoZWFkZXIgbmFtZXNwYWNlcywgdG8gYmUgSUFOQSByZWdpc3RlcmVk
Lg0KJm5ic3A7VGhpczxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyBkb2N1bWVudCBpbnRlbmRzIHRv
IHVwZGF0ZSBSRkMgNDQxMiwgYXMgYSBQcm9wb3NlZCBTdGFuZGFyZA0KZG9jdW1lbnQ8YnI+DQom
Z3Q7ICZuYnNwOyAmbmJzcDsgaWYgcHVibGlzaGVkIGJ5IHRoZSBSRkMtRWRpdG9yLjxicj4NCiZn
dDsgPGJyPg0KJmd0OyBJRVBSRVAgV29ya2luZyBHcm91cDxicj4NCiZndDsgPGJyPg0KJmd0OyBS
RkMgMzQ4Nzxicj4NCiZndDsgPGJyPg0KJmd0OyBUaXRsZTo8YnI+DQomZ3Q7ICZuYnNwOyAmbmJz
cDsgUmVxdWlyZW1lbnRzIGZvciBSZXNvdXJjZSBQcmlvcml0eSBNZWNoYW5pc21zIGZvciB0aGU8
YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgU2Vzc2lvbiBJbml0aWF0aW9uIFByb3RvY29sIChTSVAp
PGJyPg0KJmd0OyA8YnI+DQomZ3Q7IEFic3RyYWN0Ojxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyBU
aGlzIGRvY3VtZW50IHN1bW1hcml6ZXMgcmVxdWlyZW1lbnRzIGZvciBwcmlvcml0aXppbmcNCmFj
Y2VzcyB0bzxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyBjaXJjdWl0LXN3aXRjaGVkIG5ldHdvcmss
IGVuZCBzeXN0ZW0gYW5kIHByb3h5IHJlc291cmNlcw0KZm9yPGJyPg0KJmd0OyAmbmJzcDsgJm5i
c3A7IGVtZXJnZW5jeSBwcmVwYXJlZG5lc3MgY29tbXVuaWNhdGlvbnMgdXNpbmcgdGhlIFNlc3Np
b24NCkluaXRpYXRpb248YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgUHJvdG9jb2wgKFNJUCkuPGJy
Pg0KJmd0OyA8YnI+DQomZ3Q7IFJGQyAzNjg5PGJyPg0KJmd0OyA8YnI+DQomZ3Q7IFRpdGxlOjxi
cj4NCiZndDsgJm5ic3A7ICZuYnNwOyBHZW5lcmFsIFJlcXVpcmVtZW50cyBmb3I8YnI+DQomZ3Q7
ICZuYnNwOyAmbmJzcDsgRW1lcmdlbmN5IFRlbGVjb21tdW5pY2F0aW9uIFNlcnZpY2UgKEVUUyk8
YnI+DQomZ3Q7IDxicj4NCiZndDsgQWJzdHJhY3Q6PGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7IFRo
aXMgZG9jdW1lbnQgcHJlc2VudHMgYSBsaXN0IG9mIGdlbmVyYWwgcmVxdWlyZW1lbnRzDQppbiBz
dXBwb3J0IG9mPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7IEVtZXJnZW5jeSBUZWxlY29tbXVuaWNh
dGlvbnMgU2VydmljZSAoRVRTKS4gJm5ic3A7U29sdXRpb25zDQp0byB0aGVzZTxicj4NCiZndDsg
Jm5ic3A7ICZuYnNwOyByZXF1aXJlbWVudHMgYXJlIG5vdCBwcmVzZW50ZWQgaW4gdGhpcyBkb2N1
bWVudC4gJm5ic3A7QWRkaXRpb25hbDxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyByZXF1aXJlbWVu
dHMgcGVydGFpbmluZyB0byBzcGVjaWZpYyBhcHBsaWNhdGlvbnMsIG9yDQp0eXBlcyBvZjxicj4N
CiZndDsgJm5ic3A7ICZuYnNwOyBhcHBsaWNhdGlvbnMsIGFyZSB0byBiZSBzcGVjaWZpZWQgaW4g
c2VwYXJhdGUgZG9jdW1lbnQocykuPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IFJGQyAzNjkwPGJyPg0K
Jmd0OyA8YnI+DQomZ3Q7IFRpdGxlOjxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyBJUCBUZWxlcGhv
bnkgUmVxdWlyZW1lbnRzIGZvcjxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyBFbWVyZ2VuY3kgVGVs
ZWNvbW11bmljYXRpb24gU2VydmljZSAoRVRTKTxicj4NCiZndDsgPGJyPg0KJmd0OyBBYnN0cmFj
dDo8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgVGhpcyBkb2N1bWVudCBwcmVzZW50cyBhIGxpc3Qg
b2YgcmVxdWlyZW1lbnRzIGluIHN1cHBvcnQNCm9mIEVtZXJnZW5jeTxicj4NCiZndDsgJm5ic3A7
ICZuYnNwOyBUZWxlY29tbXVuaWNhdGlvbnMgU2VydmljZSAoRVRTKSB3aXRoaW4gdGhlIGNvbnRl
eHQNCm9mIElQIHRlbGVwaG9ueS48YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgSXQgaXMgYW4gZXh0
ZW5zaW9uIHRvIHRoZSBnZW5lcmFsIHJlcXVpcmVtZW50cyBwcmVzZW50ZWQNCmluIFJGQyAzNjg5
Ljxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyBTb2x1dGlvbnMgdG8gdGhlc2UgcmVxdWlyZW1lbnRz
IGFyZSBub3QgcHJlc2VudGVkIGluDQp0aGlzIGRvY3VtZW50Ljxicj4NCiZndDsgPGJyPg0KJmd0
OyBSRkMgNDE5MDxicj4NCiZndDsgPGJyPg0KJmd0OyBUaXRsZTo8YnI+DQomZ3Q7ICZuYnNwOyAm
bmJzcDsgRnJhbWV3b3JrIGZvciBTdXBwb3J0aW5nIEVtZXJnZW5jeSBUZWxlY29tbXVuaWNhdGlv
bnM8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgU2VydmljZSAoRVRTKSBpbiBJUCBUZWxlcGhvbnk8
YnI+DQomZ3Q7IDxicj4NCiZndDsgQWJzdHJhY3Q6PGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7IFRo
aXMgZG9jdW1lbnQgcHJlc2VudHMgYSBmcmFtZXdvcmsgZm9yIHN1cHBvcnRpbmcgYXV0aG9yaXpl
ZCw8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgZW1lcmdlbmN5LXJlbGF0ZWQgY29tbXVuaWNhdGlv
biB3aXRoaW4gdGhlIGNvbnRleHQgb2YNCklQIHRlbGVwaG9ueS48YnI+DQomZ3Q7ICZuYnNwOyAm
bmJzcDsgV2UgcHJlc2VudCBhIHNlcmllcyBvZiBvYmplY3RpdmVzIHRoYXQgcmVmbGVjdCBhIGdl
bmVyYWwNCnZpZXcgb2YgaG93PGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7IGF1dGhvcml6ZWQgZW1l
cmdlbmN5IHNlcnZpY2UsIGluIGxpbmUgd2l0aCB0aGUgRW1lcmdlbmN5PGJyPg0KJmd0OyAmbmJz
cDsgJm5ic3A7IFRlbGVjb21tdW5pY2F0aW9ucyBTZXJ2aWNlIChFVFMpLCBzaG91bGQgYmUgcmVh
bGl6ZWQNCndpdGhpbiB0b2RheSdzPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7IElQIGFyY2hpdGVj
dHVyZSBhbmQgc2VydmljZSBtb2RlbHMuICZuYnNwO0Zyb20gdGhlc2UNCm9iamVjdGl2ZXMsIHdl
PGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7IHByZXNlbnQgYSBjb3JyZXNwb25kaW5nIHNldCBvZiBw
cm90b2NvbHMgYW5kIGNhcGFiaWxpdGllcywNCndoaWNoPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7
IHByb3ZpZGUgYSBtb3JlIHNwZWNpZmljIHNldCBvZiByZWNvbW1lbmRhdGlvbnMgcmVnYXJkaW5n
DQpleGlzdGluZzxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyBJRVRGIHByb3RvY29scy4gJm5ic3A7
RmluYWxseSwgd2UgcHJlc2VudCB0d28gc2NlbmFyaW9zDQp0aGF0IGFjdCBhczxicj4NCiZndDsg
Jm5ic3A7ICZuYnNwOyBndWlkaW5nIG1vZGVscyBmb3IgdGhlIG9iamVjdGl2ZXMgYW5kIGZ1bmN0
aW9ucyBsaXN0ZWQNCmluIHRoaXM8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgZG9jdW1lbnQuICZu
YnNwO1RoZXNlIG1vZGVscywgY291cGxlZCB3aXRoIGFuIGV4YW1wbGUNCm9mIGFuIGV4aXN0aW5n
PGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7IHNlcnZpY2UgaW4gdGhlIFB1YmxpYyBTd2l0Y2hlZCBU
ZWxlcGhvbmUgTmV0d29yayAoUFNUTiksDQpjb250cmlidXRlPGJyPg0KJmd0OyAmbmJzcDsgJm5i
c3A7IHRvIGEgY29uc3RyYWluZWQgc29sdXRpb24gc3BhY2UuPGJyPg0KJmd0OyA8YnI+DQomZ3Q7
IFJGQyA0Mzc1PGJyPg0KJmd0OyA8YnI+DQomZ3Q7IFRpdGxlOjxicj4NCiZndDsgJm5ic3A7ICZu
YnNwOyBFbWVyZ2VuY3kgVGVsZWNvbW11bmljYXRpb25zIFNlcnZpY2VzIChFVFMpIFJlcXVpcmVt
ZW50czxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyBmb3IgYSBTaW5nbGUgQWRtaW5pc3RyYXRpdmUg
RG9tYWluPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IEFic3RyYWN0Ojxicj4NCiZndDsgJm5ic3A7ICZu
YnNwOyBUaGlzIGRvY3VtZW50IHByZXNlbnRzIGEgbGlzdCBvZiByZXF1aXJlbWVudHMgaW4gc3Vw
cG9ydA0Kb2YgRW1lcmdlbmN5PGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7IFRlbGVjb21tdW5pY2F0
aW9ucyBTZXJ2aWNlIChFVFMpIHdpdGhpbiBhIHNpbmdsZSBhZG1pbmlzdHJhdGl2ZTxicj4NCiZn
dDsgJm5ic3A7ICZuYnNwOyBkb21haW4uICZuYnNwO1RoaXMgZG9jdW1lbnQgZm9jdXNlcyBvbiBh
IHNwZWNpZmljIHNldA0Kb2YgYWRtaW5pc3RyYXRpdmU8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsg
Y29uc3RyYWludHMgYW5kIHNjb3BlLiAmbmJzcDtTb2x1dGlvbnMgdG8gdGhlc2UgcmVxdWlyZW1l
bnRzDQphcmUgbm90PGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7IHByZXNlbnRlZCBpbiB0aGlzIGRv
Y3VtZW50Ljxicj4NCiZndDsgPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IFRTViBXb3JraW5nIEdyb3Vw
PGJyPg0KJmd0OyA8YnI+DQomZ3Q7IFJGQyA0NTQyPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IFRpdGxl
Ojxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyBJbXBsZW1lbnRpbmcgYW4gRW1lcmdlbmN5IFRlbGVj
b21tdW5pY2F0aW9ucyBTZXJ2aWNlDQooRVRTKTxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyBmb3Ig
UmVhbC1UaW1lIFNlcnZpY2VzIGluIHRoZSBJbnRlcm5ldCBQcm90b2NvbCBTdWl0ZTxicj4NCiZn
dDsgPGJyPg0KJmd0OyBBYnN0cmFjdDo8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgUkZDcyAzNjg5
IGFuZCAzNjkwIGRldGFpbCByZXF1aXJlbWVudHMgZm9yIGFuIEVtZXJnZW5jeTxicj4NCiZndDsg
Jm5ic3A7ICZuYnNwOyBUZWxlY29tbXVuaWNhdGlvbnMgU2VydmljZSAoRVRTKSwgb2Ygd2hpY2gg
YW4gSW50ZXJuZXQNCkVtZXJnZW5jeTxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyBQcmVwYXJlZG5l
c3MgU2VydmljZSAoSUVQUykgd291bGQgYmUgYSBwYXJ0LiAmbmJzcDtTb21lDQpvZiB0aGVzZSB0
eXBlcyBvZjxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyBzZXJ2aWNlcyByZXF1aXJlIGNhbGwgcHJl
ZW1wdGlvbjsgb3RoZXJzIHJlcXVpcmUgY2FsbA0KcXVldWluZyBvcjxicj4NCiZndDsgJm5ic3A7
ICZuYnNwOyBvdGhlciBtZWNoYW5pc21zLiAmbmJzcDtJRVBTIHJlcXVpcmVzIGEgQ2FsbCBBZG1p
c3Npb24NCkNvbnRyb2wgKENBQyk8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgcHJvY2VkdXJlIGFu
ZCBhIFBlciBIb3AgQmVoYXZpb3IgKFBIQikgZm9yIHRoZSBkYXRhDQp0aGF0IG1lZXQgdGhlPGJy
Pg0KJmd0OyAmbmJzcDsgJm5ic3A7IG5lZWRzIG9mIHRoaXMgYXJjaGl0ZWN0dXJlLiAmbmJzcDtT
dWNoIGEgQ0FDIHByb2NlZHVyZQ0KYW5kIFBIQiBpczxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyBh
cHByb3ByaWF0ZSB0byBhbnkgc2VydmljZSB0aGF0IG1pZ2h0IHVzZSBILjMyMyBvciBTSVANCnRv
IHNldCB1cDxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyByZWFsLXRpbWUgc2Vzc2lvbnMuICZuYnNw
O1RoZSBrZXkgcmVxdWlyZW1lbnQgaXMgdG8NCmd1YXJhbnRlZSBhbiBlbGV2YXRlZDxicj4NCiZn
dDsgJm5ic3A7ICZuYnNwOyBwcm9iYWJpbGl0eSBvZiBjYWxsIGNvbXBsZXRpb24gdG8gYW4gYXV0
aG9yaXplZCB1c2VyDQppbiB0aW1lIG9mPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7IGNyaXNpcy48
YnI+DQomZ3Q7IDxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyBUaGlzIGRvY3VtZW50IHByaW1hcmls
eSBkaXNjdXNzZXMgc3VwcG9ydGluZyBFVFMgaW4NCnRoZSBjb250ZXh0IG9mPGJyPg0KJmd0OyAm
bmJzcDsgJm5ic3A7IHRoZSBVUyBHb3Zlcm5tZW50IGFuZCBOQVRPLCBiZWNhdXNlIGl0IGZvY3Vz
ZXMgb24gdGhlDQpNdWx0aS1MZXZlbDxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyBQcmVjZWRlbmNl
IGFuZCBQcmVlbXB0aW9uIChNTFBQKSBhbmQgR292ZXJubWVudCBFbWVyZ2VuY3k8YnI+DQomZ3Q7
ICZuYnNwOyAmbmJzcDsgVGVsZWNvbW11bmljYXRpb24gU2VydmljZSAoR0VUUykgc3RhbmRhcmRz
LiAmbmJzcDtUaGUNCmFyY2hpdGVjdHVyZXM8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgZGVzY3Jp
YmVkIGhlcmUgYXJlIGFwcGxpY2FibGUgYmV5b25kIHRoZXNlIG9yZ2FuaXphdGlvbnMuPGJyPg0K
Jmd0OyA8YnI+DQomZ3Q7IFdvcmsgSW4gUHJvZ3Jlc3M6ICZuYnNwOyBkcmFmdC1pZXRmLXRzdndn
LWVtZXJnZW5jeS1yc3ZwLTAzLnR4dDxicj4NCiZndDsgPGJyPg0KJmd0OyBUaXRsZTo8YnI+DQom
Z3Q7ICZuYnNwOyAmbmJzcDsgUmVzb3VyY2UgUmVTZXJWYXRpb24gUHJvdG92b2wgKFJTVlApIEV4
dGVuc2lvbnMgZm9yPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7IEVtZXJnZW5jeSBTZXJ2aWNlczxi
cj4NCiZndDsgPGJyPg0KJmd0OyBBYnN0cmFjdDo8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgQW4g
RW1lcmdlbmN5IFRlbGVjb21tdW5pY2F0aW9ucyBTZXJ2aWNlIChFVFMpIHJlcXVpcmVzDQp0aGUg
YWJpbGl0eSB0bzxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyBwcm92aWRlIGFuIGVsZXZhdGVkIHBy
b2JhYmlsaXR5IG9mIHNlc3Npb24gZXN0YWJsaXNobWVudA0KdG8gYW48YnI+DQomZ3Q7ICZuYnNw
OyAmbmJzcDsgYXV0aG9yaXplZCB1c2VyIGluIHRpbWVzIG9mIG5ldHdvcmsgY29uZ2VzdGlvbiAo
dHlwaWNhbGx5LA0KZHVyaW5nIGE8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgY3Jpc2lzKS4gV2hl
biBzdXBwb3J0ZWQgb3ZlciB0aGUgSW50ZXJuZXQgUHJvdG9jb2wgc3VpdGUsDQp0aGlzIG1heSBi
ZTxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyBmYWNpbGl0YXRlZCB0aHJvdWdoIGEgbmV0d29yayBs
YXllciBhZG1pc3Npb24gY29udHJvbA0Kc29sdXRpb24sIHdoaWNoPGJyPg0KJmd0OyAmbmJzcDsg
Jm5ic3A7IHN1cHBvcnRzIHByaW9yaXRpemVkIGFjY2VzcyB0byByZXNvdXJjZXMgKGUuZy4sIGJh
bmR3aWR0aCkuDQpUaGVzZTxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyByZXNvdXJjZXMgbWF5IGJl
IGV4cGxpY2l0bHkgc2V0IGFzaWRlIGZvciBlbWVyZ2VuY3kNCnNlcnZpY2VzLCBvciB0aGV5PGJy
Pg0KJmd0OyAmbmJzcDsgJm5ic3A7IG1heSBiZSBzaGFyZWQgd2l0aCBvdGhlciBzZXNzaW9ucy48
YnI+DQomZ3Q7IDxicj4NCiZndDsgJm5ic3A7ICZuYnNwO1RoaXMgZG9jdW1lbnQgc3BlY2lmaWVz
IFJTVlAgZXh0ZW5zaW9ucyB0aGF0IGNhbiBiZSB1c2VkDQp0byBzdXBwb3J0PGJyPg0KJmd0OyAm
bmJzcDsgJm5ic3A7IHN1Y2ggYW4gYWRtaXNzaW9uIHByaW9yaXR5IGNhcGFiaWxpdHkgYXQgdGhl
IG5ldHdvcmsNCmxheWVyLiBOb3RlIHRoYXQ8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgdGhlc2Ug
ZXh0ZW5zaW9ucyByZXByZXNlbnQgb25lIHBvc3NpYmxlIHNvbHV0aW9uIGNvbXBvbmVudA0KaW48
YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgc2F0aXNmeWluZyBFVFMgcmVxdWlyZW1lbnRzLiBPdGhl
ciBzb2x1dGlvbiBjb21wb25lbnRzLA0Kb3Igb3RoZXI8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsg
c29sdXRpb25zLCBhcmUgb3V0c2lkZSB0aGUgc2NvcGUgb2YgdGhpcyBkb2N1bWVudC48YnI+DQom
Z3Q7IDxicj4NCiZndDsgTlNJUyBXb3JraW5nIEdyb3VwPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IFdv
cmsgSW4gUHJvZ3Jlc3M6IGRyYWZ0LWlldGYtbnNpcy1xb3MtbnNscC0xNC50eHQ8YnI+DQomZ3Q7
IDxicj4NCiZndDsgVGl0bGU6PGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7IE5TTFAgZm9yIFF1YWxp
dHktb2YtU2VydmljZSBTaWduYWxpbmc8YnI+DQomZ3Q7IDxicj4NCiZndDsgQWJzdHJhY3Q6PGJy
Pg0KJmd0OyAmbmJzcDsgJm5ic3A7IFRoaXMgc3BlY2lmaWNhdGlvbiBkZXNjcmliZXMgdGhlIE5T
SVMgU2lnbmFsaW5nIExheWVyDQpQcm90b2NvbDxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyAoTlNM
UCkgZm9yIHNpZ25hbGluZyBRb1MgcmVzZXJ2YXRpb25zIGluIHRoZSBJbnRlcm5ldC4NCiZuYnNw
O0l0IGlzIGluPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7IGFjY29yZGFuY2Ugd2l0aCB0aGUgZnJh
bWV3b3JrIGFuZCByZXF1aXJlbWVudHMgZGV2ZWxvcGVkDQppbiBOU0lTLjxicj4NCiZndDsgJm5i
c3A7ICZuYnNwOyBUb2dldGhlciB3aXRoIEdJU1QsIGl0IHByb3ZpZGVzIGZ1bmN0aW9uYWxpdHkg
c2ltaWxhcg0KdG8gUlNWUCBhbmQ8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgZXh0ZW5kcyBpdC4g
Jm5ic3A7VGhlIFFvUyBOU0xQIGlzIGluZGVwZW5kZW50IG9mIHRoZQ0KdW5kZXJseWluZyBRb1M8
YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgc3BlY2lmaWNhdGlvbiBvciBhcmNoaXRlY3R1cmUgYW5k
IHByb3ZpZGVzIHN1cHBvcnQgZm9yDQpkaWZmZXJlbnQ8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsg
cmVzZXJ2YXRpb24gbW9kZWxzLiBJdCBpcyBzaW1wbGlmaWVkIGJ5IHRoZSBlbGltaW5hdGlvbg0K
b2Ygc3VwcG9ydDxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyBmb3IgbXVsdGljYXN0IGZsb3dzLiBU
aGlzIHNwZWNpZmljYXRpb24gZXhwbGFpbnMgdGhlDQpvdmVyYWxsPGJyPg0KJmd0OyAmbmJzcDsg
Jm5ic3A7IHByb3RvY29sIGFwcHJvYWNoLCBkZXNpZ24gZGVjaXNpb25zIG1hZGUgYW5kIHByb3Zp
ZGVzDQpleGFtcGxlcy4gJm5ic3A7SXQ8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgc3BlY2lmaWVz
IG9iamVjdCwgbWVzc2FnZSAmbmJzcDtmb3JtYXRzIGFuZCBwcm9jZXNzaW5nDQpydWxlcy48YnI+
DQomZ3Q7IDxicj4NCiZndDsgLS0gPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IE1hZ251cyBXZXN0ZXJs
dW5kPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IElFVEYgVHJhbnNwb3J0IEFyZWEgRGlyZWN0b3IgJmFt
cDsgVFNWV0cgQ2hhaXI8YnI+DQomZ3Q7IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08YnI+DQomZ3Q7IE11bHRpbWVk
aWEgVGVjaG5vbG9naWVzLCBFcmljc3NvbiBSZXNlYXJjaCBFQUIvVFZNL008YnI+DQomZ3Q7IC0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS08YnI+DQomZ3Q7IEVyaWNzc29uIEFCICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDt8DQpQaG9uZSArNDYgOCA0MDQ4Mjg3PGJy
Pg0KJmd0OyBUb3JzaGFtc2dhdGFuIDIzICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgfCBGYXggJm5ic3A7ICs0Ng0KOCA3NTc1NTUwPGJyPg0KJmd0OyBTLTE2NCA4MCBTdG9ja2hv
bG0sIFN3ZWRlbiB8IG1haWx0bzogbWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nzb24uY29tPGJyPg0K
Jmd0OyAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IDxicj4NCjwvdHQ+PC9mb250
Pg0K
--=_alternative 0055890785257329_=--





From tsvwg-bounces@ietf.org Tue Jul 31 15:09:32 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFx5y-0001gp-6B; Tue, 31 Jul 2007 15:09:26 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IFx5w-0001db-P1
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 31 Jul 2007 15:09:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFx5w-0001dT-FO; Tue, 31 Jul 2007 15:09:24 -0400
Received: from drew.ipv6.franken.de ([2001:638:a02:a001:20e:cff:fe4a:feaa]
	helo=mail-n.franken.de) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IFx5s-0002WU-8Y; Tue, 31 Jul 2007 15:09:24 -0400
Received: from [192.168.1.17] (p508FEBD3.dip.t-dialin.net [80.143.235.211])
	by mail-n.franken.de (Postfix) with ESMTP id DA3C48000095;
	Tue, 31 Jul 2007 21:09:17 +0200 (CEST)
	(KNF-authenticated sender: macmic)
In-Reply-To: <6dbbbf160707270547q4ddde312g95feca7dde736e6b@mail.gmail.com>
References: <OF24565732.6AADA0AB-ON48257325.00301996@chinamobile.com>
	<6dbbbf160707270547q4ddde312g95feca7dde736e6b@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=GBK; delsp=yes; format=flowed
Message-Id: <BB3D6EB8-5B3D-489B-8BCE-C5EE7362CA6F@lurchi.franken.de>
Content-Transfer-Encoding: quoted-printable
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Date: Tue, 31 Jul 2007 21:09:14 +0200
To: Ankit Kumar Sharma <ankisharma@gmail.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 4.0 (++++)
X-Scan-Signature: 21f6736b171db90b7af90d77f0c0e285
Cc: =?UTF-8?Q? =E9=99=88=E6=97=AD ?= <chenxu@chinamobile.com>,
	SIGTRAN <sigtran@ietf.org>, TSWG <tsvwg@ietf.org>
Subject: [Tsvwg] Re: [Sigtran] The requiremnts and
	proposalsforM2PA/M3UA/SCTPExtension from China Mobile
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi Ankit,

comments in-line.

Best regards
Michael

On Jul 27, 2007, at 2:47 PM, Ankit Kumar Sharma wrote:

> chenxu,
>
> On 7/27/07, =B3=C2=D0=F1 <chenxu@chinamobile.com > wrote: Dear Michael =
Tuexen,
>
>
> >    1. What does "unionize of the primary paths between nodes" mean?
>    It means=A3=ACfor one multi-homed SCTP endpoint,the primary path=20
> =A3=A8source IP address=3DIP1---destination IP=3DIP2=A3=A9 shall be =
the same as =20
> the remote endpoint's ( source IP address=3DIP2---destination IP=3DIP1 =
 )
>
>    Many venders implement Multi-homing in the following way:
>
>     one multi-homed SCTP endpoint has two local IP addresses(IP1/=20
> IP2) and two remote IP address(IP3/IP4) within an association.
>     There's two paths within an association:IP1-IP3,and IP2-IP4.not =20=

> 4 paths.
>
>     For example, endpoint1 has two local IP addresses(IP1/IP2)=A3=AC =
and =20
> endpoint2 has two local IP addresses(IP3/IP4).
>
> if two endpoints' primary path isn't the same,that is endpoint1 use =20=

> IP1-IP3 as the primary path, use IP2-IP4 as the second path;  =20
> endpoint2 use IP3-IP2 as the primary path, use IP4-IP1 as the =20
> second path.
I would consider it the following way:
The first end-point (owning IP1 and IP2) has two paths, one towards =20
IP3 and
another one towards IP4.
When sending a packet towards the peer SCTP choses IP3 or IP4 as the =20
destination
address and normally the source address is selected based on the =20
routing table.
The peer will accept the messages as long as the source address is =20
either IP1
or IP2. The pairing IP1/IP2 and IP3/IP4 is not enforced by the SCTP =20
implementation.
>
>
>     These two endpoints can't  send data to each other successfully.
>  >     2. Not sure about the SACK issue: You are currently allowed to
> >    send the SACK back to an addresses different from the source
> >    address of the corresponding DATA chunk. As far as I know
> >    it is only a SHOULD describing that you send the SACK back
> >    to the source address of the DATA chunk.
>
>      You are right,it is only a SHOULD describing that you send the =20=

> SACK back
>    to the source address of the DATA chunk in RFC2960.
>       That's why we get in trouble in multi-homing situation.
>       If the  path to the source address of the DATA chunk is =20
> unreachable=A3=ACthe sack can't send to the remote endpoint for ever =20=

> although the other path is available.Soon the other path will be =20
> failure.
>
> I don't see any problem in SCTP RFC for above mentioned scenario.
> As per RFC 2719, following is the defination of "SHOULD":
> 3. SHOULD This word, or the adjective "RECOMMENDED", mean that =20
> there may exist valid reasons in particular circumstances to ignore a
> particular item, but the full implications must be understood and
>
> carefully weighed before choosing a different course.
>
> Now please look at following excerpt from section 6.4(Multi-homed =20
> SCTP Endpoints) of SCTP RFC:
> " When a receiver of a duplicate DATA chunk sends a SACK to a multi-
> homed endpoint it MAY be beneficial to vary the destination address
> and not use the source address of the DATA chunk. The reason being
>
> that receiving a duplicate from a multi-homed endpoint might indicate
> that the return path (as specified in the source address of the DATA
> chunk) for the SACK is broken.
> "
> So as per your scenario, if SOURCE address of sender is not =20
> reachable then our SACK would be lost. After RTO expiry at sender, =20
> sender would again try to send the DATA chunk. Now, receiver could =20
> behave as per above mentioned excerpt.
>
> Best Regard
> Chen Xu
> China Mobile
> chenxu@chinamobile.com
>
>
>
>
>
>
>
> =3D=3D=3D=3D=3D=3D=3D 2007-07-26 22:23:20 =C4=FA=D4=DA=C0=B4=D0=C5=D6=D0=
=D0=B4=B5=C0=A3=BA=3D=3D=3D=3D=3D=3D=3D
>
> >Dear all,
> >
> >I'm sending this also to TSVWG, since the SCTP discussion has to be
> >done the that WG.
> >
> >Addressing the SCTP statement:
> >
> >1. What does "unionize of the primary paths between nodes" mean?
> >2. Not sure about the SACK issue: You are currently allowed to
> >    send the SACK back to an addresses different from the source
> >    address of the corresponding DATA chunk. As far as I know
> >    it is only a SHOULD describing that you send the SACK back
> >    to the source address of the DATA chunk.
> >
> >Best regards
> >Michael
> >
> >On Jul 26, 2007, at 4:22 AM, chenxu wrote:
> >
> >> Dear all,
> >>
> >>      Sorry to submit the rar file! And thanks Rui Gomes!
> >>
> >> The contents of the attachments are as follows:
> >>
> >>   =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D
> >>   for SCTP of China Mobile.ppt
> >>  =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D
> >>
> >>  The Requirement and Proposal
> >>   for SCTP Specification Extension
> >>   of China Mobile
> >>
> >>  Chen Xu , Zhang Hao
> >>  China Mobile
> >>
> >>  Content
> >>
> >>  Background
> >>  Problem description
> >>  Requirement for Supplement of RFC4460
> >>  Proposal for Supplement of RFC4460
> >>
> >>  Background
> >>
> >>  The world trend of IP bearer for signalling will make SIGTRAN
> >>  standard widely used in signalling network.
> >>  Traditional and new Telecom carriers implement signalling over =20
> IP to
> >>  Reduce  cost for extended capacity
> >>  Removes the links/linkset limitation imposed by traditional TDM
> >>  linksets for traffic growth
> >>  Avoid major network re-engineering when traffic grows
> >>  SCTP is the basis of signalling over IP
> >>
> >>  SCTP is also important to China Mobile
> >>  Applying to the Nc interface to transport BICC messages
> >>  Applying to the Mc interface to transport H.248 messages
> >>  Applying to the interface between MSC Server and the embedded =20
> SG to
> >>  transport access network signalling
> >>  Applying to signalling network
> >>  the interface between IPSEPs
> >>  the interface between IPSTPs
> >>  the interface between IPSEP and IPSTP
> >>
> >>
> >> Problem description
> >>
> >> China Mobile has a large number of subscribers and has built the
> >>  largest soft-switch network in the world. The signaling traffic
> >>  between two nodes is very large.
> >>  China Mobile imports multi-vender's products. The compatibility
> >>  between different vender's products is important.
> >>  The illegibility of Multi-homing mechanism in SCTP protocol brings
> >>  on compatibility problems
> >>  SCTP did not define the mechanism how the SACK is send back to
> >>  endpoint by other path when one path fails.
> >>  SCTP defines multi-homing, but it did not define how the primary
> >>  path can be unionized between two nodes.
> >>  Requirement for Supplement of RFC4460
> >>  Define the mechanism that SACK is send back to endpoint by the
> >>  secondary path if the primary path fails .
> >>  Define  the mechanism how the primary path can be unionized =20
> between
> >>  two nodes.
> >>
> >>
> >>  Proposal for Supplement of RFC4460
> >>
> >>
> >>  1=A3=A9Add the mechanism how the primary path can be unionized =
between
> >>  two nodes in Section 5  'Association Initialization '.
> >>  2=A3=A9 Add the mechanism that SACK is send back to endpoint by =
the
> >>  secondary path if the primary path fails in Section 6.2
> >>  'Acknowledgement on Reception of DATA Chunks '.
> >>
> >> (That's all for SCTP)
> >>
> >>
> >>  =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D
> >>  for M3UA of China Mobile.ppt
> >>  =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D
> >>
> >>  The Requirement and Proposal
> >>   for M3UA Specification Extension
> >>   of China Mobile
> >>
> >>  Chen Xu
> >>  China Mobile
> >>
> >>
> >>  Content
> >>
> >> Background
> >>  Problem Description
> >>  Requirement for Extension of RFC4666
> >>  Proposal for Extension of RFC4666
> >>
> >>
> >>
> >>  Background
> >>
> >>  The application of SIGTRAN standard for SG has ever solved the
> >>  problems of  No.7 Signalling System Interworking IP and
> >>  transmission of  access network signalling  in  R4 CS core =20
> network.
> >>  The world trend of IP bearer for signalling will make SIGTRAN
> >>  standard widely used in signalling network.
> >>  Traditional and new Telecom carriers implement signalling over =20
> IP to
> >>  Reduce  cost for extended capacity
> >>  Removes the links/linkset limitation imposed by traditional TDM
> >>  linksets for traffic growth
> >>  Avoid major network re-engineering as traffic grows
> >>
> >>  SIGTRAN is also important to China Mobile
> >>  Applying to the Nc interface of BICC network to transport BICC
> >>  messages
> >>  Applying to the interface between MSC Server and embeded SG to
> >>  transport access network signalling
> >>  Applying to signalling network
> >>  the interface between IPSEPs=A1=AA=A1=AAM3UA
> >>  the interface between IPSTPs=A1=AA=A1=AAM2PA
> >>  the interface between IPSEP and IPSTP=A1=AA=A1=AAM3UA
> >>
> >>  Problem description
> >>
> >>  M3UA specification doesn't  define signaling network  management
> >>  function
> >>  M3UA is designed for SG-IPSEP and IPSEP-IPSEP applications,
> >>  therefore network level management function isn't required.
> >>  SSNM messages defined in M3UA are only used for interworking with
> >> SS7.
> >>  China Mobile has a large number of subscribers and has built the
> >>  largest soft-switch network in the world, its signaling network
> >>  will be the multi-level and multi-area mode.
> >>  It will has two signalling routeing  scene:IPSEP-IPSTP-IPSTP-IPSEP
> >>  and IPSEP-IPSTP-IPSEP
> >>  The interworking  function with MTP3 in M3UA can realize the
> >>  signaling network  management for  IPSEP-IPSTP-IPSTP-IPSEP scene;
> >>  Current M3UA  can not  realize the signaling network  management
> >>  for  IPSEP-IPSTP-IPSEP scene.
> >>
> >>  Requirement for Extension of RFC4666
> >>
> >>  Define the Application for IPSTP-IPSEP interface.(Still uses SGP-
> >>  ASP procedures)
> >>  Define the signalling network management function=A3=ACmessages =
,and
> >>  procedures.(Describe how to use SSNM messages to support signaling
> >>  network management for IPSEP-(M3UA)-IPSTP-(M3UA)-IPSEP scene. )
> >>
> >>  Proposal for Extension of RFC4666
> >>
> >>  1=A3=A9Add different kinds of routing scenes applications for =
IPSEP-
> >>  IPSTP interface in Section 1.5  'Sample Configuration '.
> >>  2=A3=A9Add the M3UA signalling network management function in =
Section
> >>  1.4  'Functional Areas'.
> >>  3=A3=A9 Add the Client/Server Model for IPSTP-IPSEP interface in
> >>  Section 1.4.8 .  'SCTP Client/Server Model'.
> >>  4=A3=A9Extend the DUPU message code in Chapter 3 'M3UA Protocol
> >>  Elements'.
> >>  5=A3=A9Add the signalling network management procedure in Chapter
> >>  4'procedure'.
> >>  6) Add the requirement of Multi user data streams for M3UA over
> >>  SCTP Application in Section 1.4.7 ' SCTP Stream Mapping'.
> >>
> >> (That's all for M3UA)
> >>
> >>
> >>  =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D
> >>  for M2PA of China Mobile.ppt
> >>  =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D
> >>
> >>  The Requirement and Proposal
> >>   for M2PA Specification Revision
> >>   of China Mobile
> >>
> >>  Chen Xu
> >>  China Mobile
> >>
> >>  Content
> >>
> >>  Background
> >>  Problem Description
> >>  Requirement for Revision of RFC4165
> >>  Proposal for Revision of RFC4165
> >>
> >>
> >>  Background
> >>
> >>  M2PA protocol is a peer to peer protocol, it not only supports
> >>  seamless management operation of MTP3 protocol peers over an IP
> >>  network connection, but also removes the links/linkset limitation
> >>  imposed by traditional TDM linksets for traffic growth.
> >>
> >>  The Standardization of M2PA is behind the application of it.
> >>  Although the RFC edition is released in 2005, M2PA is widely used
> >>  in the  Signaling network rebuilding over IP for traditional
> >>  operators and in the Signaling network construction for  new
> >>  operators  since 2002.
> >>
> >>  Various draft editions and the major differences between them make
> >>  problems when one  IPSTP provider interworking with another.
> >>
> >>  Problem Description
> >>
> >>
> >>  RFC4165 needs to be supplemented and revised =A3=BA
> >>  Some  procedures  are  described a little bit simply and referred
> >>  to MTP2 directly ,  which  makes IPSTP  providers realizing the
> >>  procedures in different ways ,for  there's difference between MTP2
> >>  and M2PA in some aspects.      .
> >>  Some IPSTP providers use the same idea as MTP2
> >>  Others take the relation between M2PA and SCTP into account.
> >>
> >>  T7 isn't defined and given the range, which makes IPSTP providers
> >>  realizing it in different ways.
> >>
> >>  How to fill in and process FSN and BSN in M2PA Header isn't
> >>  defined clearly.
> >>
> >>
> >>  Requirement for Revision of RFC4165
> >>
> >>  Supplement the description of the whole idea for Link Alignment
> >>  procedure and Processor Outage procedure.
> >>  Supplement the definition and range of M2PA Timers.
> >>  Supplement the rules of usage of FSN and BSN in M2PA Header.
> >>
> >>
> >>  Proposal for Revision of RFC4165
> >>
> >>  1=A3=A9Supplement the whole idea , the phase division , the =
correlated
> >>  messages and Timers of Link Alignment procedure in Section 4.1.3.
> >>  2=A3=A9Supplement the whole idea of Processor Outage procedure, =
and
> >>  describe the rules of LPO and RPO processing separately .
> >>  3=A3=A9Supplement the rules of usage of FSN and BSN in M2PA Header =
in
> >>  Section 4.2.1
> >>  4=A3=A9Supplement the definition and range of M2PA Timers in =
Appendix.
> >>
> >> (That's all for M2PA)
> >>
> >> Chen Xu
> >> China Mobile
> >> chenxu@chinamobile.com
> >> _______________________________________________
> >> Sigtran mailing list
> >> Sigtran@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/sigtran
>
>
>
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>
>






From tsvwg-bounces@ietf.org Tue Jul 31 20:09:59 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IG1ml-0001ue-Sp; Tue, 31 Jul 2007 20:09:55 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IG1ml-0001uZ-58
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 31 Jul 2007 20:09:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IG1mk-0001uR-Ra
	for tsvwg@ietf.org; Tue, 31 Jul 2007 20:09:54 -0400
Received: from smtp3.smtp.bt.com ([217.32.164.138])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IG1mj-0001L0-60
	for tsvwg@ietf.org; Tue, 31 Jul 2007 20:09:54 -0400
Received: from i2kc08-ukbr.domain1.systemhost.net ([193.113.197.71]) by
	smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Aug 2007 01:09:52 +0100
Received: from cbibipnt08.iuser.iroot.adidom.com ([147.149.100.81]) by
	i2kc08-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 1 Aug 2007 01:09:52 +0100
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by
	cbibipnt08.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a
	P0803.399); id 1185926991330; Wed, 1 Aug 2007 01:09:51 +0100
Received: from mut.jungle.bt.co.uk ([10.86.0.19])
	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id
	l7109lIE014158; Wed, 1 Aug 2007 01:09:50 +0100
Message-Id: <5.2.1.1.2.20070731234936.04a65eb8@pop3.jungle.bt.co.uk>
X-Sender: rbriscoe@pop3.jungle.bt.co.uk
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Wed, 01 Aug 2007 01:10:05 +0100
To: Sally Floyd <sallyfloyd@mac.com>
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
In-Reply-To: <a77a82372c75e173c8679a03c3181cea@mac.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: -1.36 () ALL_TRUSTED
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 01 Aug 2007 00:09:52.0298 (UTC)
	FILETIME=[484C80A0:01C7D3D0]
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 5fb88b8381f3896aeacc5a021513237b
Cc: tsvwg WG <tsvwg@ietf.org>
Subject: [Tsvwg] Re: feedback on draft-briscoe-tsvwg-ecn-tunnel-00
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Sally,

I was taking a couple of weeks off when you sent this, so only now am I 
catching up with the backlog...

At 22:30 19/07/2007, Sally Floyd wrote:
>Bob -
>
>Here is some feedback on Layered Encapsulation of Congestion Notification,
>draft-briscoe-tsvwg-ecn-tunnel-00.
>
>As I have said earlier, it is fine by me to update RFC 3168 to say
>that a tunnel ingress should copy the ECN field from the inner
>header to the outer header.  So this feedback is about smaller bits
>and pieces.  (SHOULD vs. MUST, for example...)
>
>- Sally
>
>
>Feedback on draft-briscoe-tsvwg-ecn-tunnel-00:
>
>Section 3.1:
>"ECN at the IP layer is designed to carry information about congestion
>from a congested resource to some downstream node that will feed the
>information back somehow to the point upstream of the congestion that
>can regulate the load on the congested resource."
>
>Actually, that is not true.  RFC 3168 has two parts, specifying
>ECN in both IP and in TCP, but ECN in the IP layer wasn't designed
>only for unicast transport protocols.  E.g., at the time multicast
>was a big deal in some of the research community, with receivers
>joining and leaving layered multicast groups.  From the first
>paragraph of the Introduction of RFC 3168:
>
>"We ... describe modifications needed to TCP to make it ECN-capable.
>Modifications to other transport protocols (e.g., unreliable unicast
>or multicast, reliable multicast, other reliable unicast transport
>protocols) could be considered as those protocols are developed and
>advance through the standards process."
>
>And later, in Section 6 on "Support from the Transport Protocol":
>
>"Second, the transport protocol must be capable of reacting
>appropriately to the receipt of CE packets.  This reaction could be
>in the form of the data receiver informing the data sender of the
>received CE packet (e.g., TCP), of the data receiver unsubscribing to
>a layered multicast group (e.g., RLM [MJV96]), or of some other
>action that ultimately reduces the arrival rate of that flow on that
>congested link."
>
>So ECN was designed with transport protocols in mind, but it was not
>designed only for unicast, TCP-like transport protocols.  In particular,
>there could be protocols where the transport receiver is the actor,
>not the transport sender.

Good point. How about...

"ECN at the IP layer is designed to carry information about congestion
from a congested resource towards downstream nodes. Typically a downstream 
transport might feed the information back somehow to the point upstream of 
the congestion that can regulate the load on the congested resource, but 
other actions are possible (see [RFC3168] Sec.6)."


>Section 3.2:
>"It might be useful for the tunnel egress to be able to tell whether
>congestion occurred across a tunnel or upstream of it."
>
>The rest of the paragraph is specific to multi-level congestion
>marking such as PCN (and even in this case, I assume that the tunnel
>egress can only tell whether congestion occurred across the tunnel
>or upstream of it if the ECN field was not already at the highest
>of the multi levels at tunnel ingress).
>
>It seems *conceivable* to me that someone might want to design a
>tunnel where the egress would want to know whether congestion
>occurred across the tunnel or upstream of it, but where the ingress
>was not a Load Regulator.  (I don't know why, offhand, though
>multicast comes to mind.)  *If* one wanted to allow this in some
>future tunnel, then one should change the MUST about copying the
>ECN field from the inner to the outer header at ingress to a SHOULD.
>And if one didn't want to allow this, then this should be made as
>explicit as possible, I would say.  Making it completely clear that
>when the ECN field is copied from the inner to the outer header at
>ingress, then the tunnel egress won't necessarily be able to tell
>whether congestion occurred across a tunnel or upstream of it.
>(I guess that a simple way out would be just to stretch the
>definition of "Load Regulator", to say that any time the tunnel
>egress wants to be able to tell whether congestion occurred
>across the tunnel or upstream of it, the ingress is called a
>Load Regulator.)

Actually, I think you'll find the rest of the para isn't specific to PCN 
and it answers your question (particularly from "But the same information 
could be gleaned...").

Essentially, even if the ingress copies the incoming header to the outer, 
any _additional_ marking along the tunnel can be detected at the tunnel 
egress as a difference between inner & outer.

Having realised this, there was no reason not to say MUST as:
- a single behaviour is always preferable to multiple options
- and copying at ingress actually doesn't lose info that might one day be 
useful about what happened across the tunnel.

Strictly, additional marking isn't quite the same as additional congestion 
(additional congestion which might have just happened to mark the same 
packet as was already marked). But, I don't think we should start 
introducing complicating options to allow for this corner case within some 
possible future scheme to extract what happened within the tunnel, that 
we're not sure anyone will ever want anyway. That corner case might be 
important to some scheme in the future during high congestion, but I 
suggest it will be their task to change MUST to SHOULD if they really need to.



>Section 5:
>In Table 1, are you ruling out the possibility of a future
>tunnel design, with a Load Regulator at the ingress, where
>packets are ECN-Capable within the tunnel, but not ECN-Capable
>outside the tunnel?  (This could result in an inner header
>that was not-ECT, but an outer header that was ECT or CE.)

This table is a restatement of full functionality RFC3168 and RFC4301 
tunnel egress behaviour, which I haven't changed (except for adding a 
couple of warnings for illegal transitions that were missed in those two RFCs).

You're right, I hadn't considered that this would preclude an inner 
ECN-capable control loop.

See the next mail to Gorry about this: I *think* that we can make these 
control loop-within-loop issues orthogonal to tunnelling by showing that 
such functions can always be put before encapsulation or after 
decapsulation. Then we can simply define what to do in the appropriate 
I-D/RFC about in-path load regulation without crossing the issue of tunnelling.

>Is this table specific to PCN?

Not at all. As I said, Table 1 is just a restatement of vanilla RFC3168 / 
RFC4301. In fact, if PCN uses 2 congestion marking levels (admission & 
termination), we'll have to define a different egress behaviour for PCN, 
with the central square of the matrix changing from:

ECT(0)  ECT(0)
ECT(1) ECT(1)

to

ECT(0)  ECT(1)
ECT(0) ECT(1)

If we did this for all DSCPs, it would also correctly preserve the ECN 
nonce (see discussion in security considerations section about how RFC3168 
& RFC4301 currently lose nonce protection over a tunnel).


>It would seem OK to me to
>think about an ECN-Capable tunnel with a Load Regulator in
>the middle of a non-ECN-Capable end-to-end connection.
>
>
>When the ingress is a Load Regulator, why "MUST" it reset
>the outer heater to ECT(0)?  Isn't this PCN-specific?  Might
>an ingress that is a Load Regulator in some cases want to
>use both ECN(0) and ECN(1) *within the tunnel*, with some
>tunnel-specific mechanism for using ECN(0) ad ECN(1) to
>check for misbehaving nodes along the path?  (I am not
>recommending it, just arguing against precluding
>it unnecessarily...)

Actually, I wasn't writing this with PCN in mind - I was just repeating 
what RFC3168 already said about resetting CE to ECT(0). I'm not sure what 
PCN should do yet, because the PCN encoding is very much up in the air at 
the moment (see draft-chan-pcn-encoding-comparison-00.txt, to which the 
authors have agreed substantial changes following considerable bashing on 
the list).

Anyway, as said above, I *think* I can take this in-path load regulator 
stuff out of this ecn-tunnel draft. Then it can be defined for each 
specific case, while tunnel implementations could all do the same thing 
irrespective of in-path load regulators. And any XXX-specific behaviour 
could be in a XXX doc, not this tunnelling doc, where XXX = 
{PCN|PWE3|CAPWAP|etc}.


>Section 9:
>"With the rules as they stand in RFC3168 and RFC4301, within a
>tunnel a CE marking could be added and subsequently removed by a
>non-compliant node without detection, because the evidence of such
>misbehaviour is removed by the decapsulator." Yep, as with this
>document, RFC 3168 didn't copy ECT(0) or ECT(1) from the outer to
>the inner header upon decapsulation.  But the tunnel egress, if it
>wanted, could look to see if the ECT fields in the inner and outer
>headers didn't match, and infer cheating within the tunnel, if it
>wanted (in the RFC 3168 case, that is, where the ECT field from the
>inner header is copied to the outer header).

True (strictly only the full functionality case of RFC3168).

>But if you say that
>an encapsulator that is a Load Regulator MUST set the outer header
>to ECT(0), you lose that possibility of protection at the egress
>of non-compliant nodes within the tunnel, it would seem to me.
>Worth mentioning somewhere.

You're right - I could have said it sets either ECT(0) or ECT(1), with 
ECT(0) as default. But, as I said, I hope I won't need to say anything in 
this I-D about in-path load regulators.



>Nits:
> From the abstract:
>This document "gives general principles to guide the design of
>alternate congestion marking behaviours for specific PHBs and for
>lower layer congestion notification schemes."
>
>Where did this document do that?  That seems misleading to me.

I meant "... gives general principles to guide the design of tunnelling 
behaviours for alternate congestion marking schemes used by specific PHBs, 
and and the design of encapsulations by lower layer headers supporting 
congestion notification."

That's what sections 3 & 4 were meant to do. Is this better?


>Section 6:
>When you first use "full-functionality" and "limited-functionality"
>modes, you might want to refer the reader to RFC 3168.

OK


>Section 7:
>"neither identified the need to raise an alarm if the inner header
>was CE but the outer header was ECT."
>
>RFC 3168 didn't identify the need to raise an alarm in this case
>because there *is* no need to raise an alarm when the inner header
>is not copied to the outer header, as is the case in RFC 3168.

Good point for ECT(0).

But in RFC3168, wasn't ECT(1) an illegal outer header if the inner header 
was CE, so a "MAY warn" would have been appropriate in that case at least?

Anyway, I'll change the offending text, to simply say that, once CE is 
copied to the outer at ingress, these extra warnings MAY be appropriate (or 
words to that effect).


Bob


____________________________________________________________________________
Notice: This contribution is the personal view of the author and does not 
necessarily reflect the technical nor commercial direction of BT plc.
____________________________________________________________________________
Bob Briscoe,                           Networks Research Centre, BT Research
B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 645196 







From tsvwg-bounces@ietf.org Tue Jul 31 20:50:40 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IG2Q7-00020n-Et; Tue, 31 Jul 2007 20:50:35 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IG2Q6-00020h-LU
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 31 Jul 2007 20:50:34 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IG2Q6-00020Z-9P
	for tsvwg@ietf.org; Tue, 31 Jul 2007 20:50:34 -0400
Received: from smtp2.smtp.bt.com ([217.32.164.150])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IG2Q4-0003ds-Ul
	for tsvwg@ietf.org; Tue, 31 Jul 2007 20:50:34 -0400
Received: from i2kc08-ukbr.domain1.systemhost.net ([193.113.197.71]) by
	smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Aug 2007 01:50:31 +0100
Received: from cbibipnt08.iuser.iroot.adidom.com ([147.149.100.81]) by
	i2kc08-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 1 Aug 2007 01:50:31 +0100
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by
	cbibipnt08.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a
	P0803.399); id 1185929430298; Wed, 1 Aug 2007 01:50:30 +0100
Received: from mut.jungle.bt.co.uk ([10.86.0.19])
	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id
	l710oRmH014414; Wed, 1 Aug 2007 01:50:29 +0100
Message-Id: <5.2.1.1.2.20070731215135.04a04098@pop3.jungle.bt.co.uk>
X-Sender: rbriscoe@pop3.jungle.bt.co.uk
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Wed, 01 Aug 2007 01:50:39 +0100
To: <gorry@erg.abdn.ac.uk>
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
Subject: RE: [Tsvwg] ECN with Tunnels - to copy or change the ECN in
	the outerheader
In-Reply-To: <F222151D3323874393F83102D614E0550A4D23F5@CORPUSMX20A.corp.
	emc.com>
References: <C2CF6041.7927%gorry@erg.abdn.ac.uk>
	<C2CF6041.7927%gorry@erg.abdn.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: -1.36 () ALL_TRUSTED
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 01 Aug 2007 00:50:31.0423 (UTC)
	FILETIME=[F62170F0:01C7D3D5]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a3f7094ccc62748c06b21fcf44c073ee
Cc: "BLACK, David" <Black_David@emc.com>, tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Gorry,

At 03:42 30/07/2007, Black_David@emc.com wrote:
>Gorry,
>
>>[GF]: I have a query about the draft on ECN use with Tunnels, relating to 
>>the ECN codepoint copying that I raised in the TSV meeting yesterday.
>>
>>As I understand, the adjustment to IPsec related only to copying the 2 
>>ECN bits (plus DS codepoints) from the outer to the inner on ingress and 
>>back again at egress. I agree we SHOULD also do a similar recommendation 
>>for Tunnels in general, and I'd like to see this STD-Track for use in the 
>>General Internet.
>
>[DB]: IPsec (RFC 4301) does something slightly different on egress - it only
>copies a CE codepoint from outer to inner.

[BB]: I deliberately kept the behaviour at the egress unchanged from 
RFC3168 ECN and RFC4301 IPsec (except I added some "MAY warn" statements 
for illegal transitions).


>>[GF]: However, I am concerned that this draft does not only address these 
>>problems (which could be a PS), but it also adds new concepts as well.
>>
>>In the ECN architecture, my understanding is that HOSTs choose to set the 
>>ECN field to ECT(0) and ECT(1), depending upon the policy at the sender.

[BB]: FYI,  somewhere around the time the ECN spec was in the last stages 
of becoming RFC3168 in early 2001, I discussed with Sally the possibility 
of in-path nodes ('proxies') setting ECT (I think it was off-list, but I 
believe I summarised the conversation to the list). Sally's sensible view 
was that any such behaviour would have to be defined at the time such a 
proxy was defined. That's essentially what the PCN w-g is doing now (back 
then, we were working on what has become PCN, which is why I had an interest).

>>[GF]: ECN Nonce ( RFC3540) implies a specific semantic to this. The IETF 
>>has a BCP that also says how other alternative semantics may be applied 
>>with specific DS codepoints (RFC4774).
>>
>>There seem to be two new ideas here. While this may be being considered 
>>in other places, I do not recall it as a part of the original design for ECN:
>>
>>* The idea that packets from an end host that do not use an ECN-capable 
>>transport can be mapped to an ECT codepoint over a congestion-controlled 
>>tunnel. The current scope of this work in the IETF seems to be scoped 
>>only for use within a PCN domain.
>
>[DB]: I tend to agree.  Absent something like PCN that invokes alternate 
>semantics for the ECN field, the congestion control for the tunnel would 
>have to be TCP-like (reaction to congestion-marked packet is equivalent to 
>reaction to dropped packet) in order to comply with RFC 3168.

[BB]: I relegated the stuff about an in-path load regulator to an appendix 
because I didn't want to introduce new stuff, but I did want to somehow 
give advice relevant to the PCN w-g (and possibly PWE3 and CAPWAP who are 
both knocking around ideas about in-path load regulators).

In-path load regulation is often a bad idea, but I didn't want to make that 
judgement in this draft, which is just about how tunnels handle the wire 
protocol. So I wanted to keep it at the level of "In any cases where the 
IETF deems in-path load regulation is sensible, this is what you should do 
with the wire protocol, if the load regulator co-incides with a tunnel 
ingress."

Just before the Chicago IETF, as David says, I realised I'd got the stuff 
about in-path load regulators wrong anyway. I now believe that an in-path 
load regulator would reset CE to ECT *before* any tunnel encapsulation.

I *think* these second thoughts mean that in-path load regulation is 
orthogonal to tunnelling, so I can just remove it from this draft 
altogether. And it can be dealt with in the relevant w-g (e.g. PCN, PWE3 or 
CAPWAP).

But I'd like to allow myself third thoughts when I update to -01. At that 
time, if I leave anything in about in-path load regulators I'll pop it onto 
the list first to get your reaction (and others).

>>[GF]: * The idea that packets marked with an ECN codepoint may be 
>>remarked to a different ECN codepoint by some tunnel endpoints, including 
>>mapping CE to an ECT value, and mapping ECT(1) to ECT(0).
>>
>>   "If the tunnel ingress is also a Load Regulator, it MUST instead reset
>>    the outer header to ECT(0)."

[BB]: Strictly, this idea isn't new. It was the full functionality mode in 
RFC3168. The CE is preserved through the inner header and pops out the 
other end of the tunnel, whatever variant of egress behaviour it encounters.

However, you are right that the idea of an in-path load regulator doing 
this is new (but likely to be removed anyway - so lets not worry about it 
for now).

>>[GF]: Section 7:
>>   "The rule that a tunnel ingress MUST copy any ECN field into the outer
>>    header is a change to RFC3168 (unless it is a Load Regulator as well, in
>>    which case there is no change)."
>
>[DB]: Bob and I have had some serious private discussions about this.
>IMHO, the charitable conclusion is that the Load Regulator
>concept in the draft has not been completely thought through
>(after all, it is a "draft"), and I believe Bob is considering
>just dropping it from the next version of this draft.
>
>>[GF]: The draft describes permitting a mid-box/router to choose to reset the
>>code point to ECT(0) when it was originally set to some other value.
>>
>>- So my view on this varies depending on the original value:
>>N-ECT  -> ECT(0) ... I think this was the goal,
>>                    but is this safe in the general internet?
>
>[DB]: Provided that the tunnel ingress *knows* that the tunnel egress
>will do the "right thing" (e.g., drop if outer is marked with CE,
>else forward with N-ECT from inner header) this should be ok, but
>*knows* can't just be *assumes*.  This is headed in the interesting
>direction of running a congestion control feedback loop from tunnel
>ingress to egress in a fashion transparent to the end-to-end
>congestion control.  There are some details to watch out for, as
>a drop could activate both ingress-to-egress and end-to-end
>congestion control.

[BB]: I agree with David here.

>>[GF]:
>>ECT(0) -> ECT(0) ... No change
>>ECT(1) -> ECT(0) ... This contradicts  RFC3540 and RFC4774, and seems
>>                    like we are limiting options for using schemes
>>                    currently permitted and options for the future.
>
>[DB]: Hmm ... I have the impression that non-support for 3540 (experimental)
>is "in play" as a potential part of PCN.  FWIW, 4301 (IPsec) tunneled
>the 3540 nonce rather than propagating it through the outer header.
>Beyond this, I can't agree with the "contradicts ... RFC 4774"
>statement without a much longer discussion ;-).

[BB]: As I point out in the security considerations section of this draft, 
RFC3168 tunnel behaviour currently complicates the ECN nonce anyway, losing 
the sender's nonce protection over the length of the tunnel (noting Sally's 
point in the previous mail that the tunnel egress could detect changes to 
the nonce in these cases). Ideally, I would have redefined the egress 
behaviour to fix this, but I left it as it is, to avoid changing IPsec again.

We could fix the nonce as well, using this draft. But in discussions with 
David B, Bruce Davie and separately with the Transport ADs, the proposed 
plan is to wait until PCN is more mature, then we can take everything that 
might need taking into account, all together.

Current plan is to issue an update to this draft, still as individual 
draft-briscoe-tsvwg-ecn-tunnel-01 to make some necessary corrections to 
this draft that don't depend on where PCN might go, but then leave the I-D 
on hold for at least one IETF cycle to allow us to identify any consensus 
the PCN w-g is converging on regarding header encoding.

[BTW, PCN doesn't need to support the nonce edge-edge because PCN boundary 
nodes don't do predictable edge-edge packet ordering so a binary nonce 
wouldn't work anyway (but PCN may have to preserve an e2e nonce by 
tunnelling the e2e header - this is how I would approach the possibility of 
end-to-end having to coexist with edge-to-edge control loops).]

>>[GF]:
>>CE    -> ECT(0) ... What are the implications of this when transiting
>>                    a network using ECN or alt. ECN semantics?

[BB]: This is the way RFC3168 worked: full functionality mode reset CE -> 
ECT(0) at tunnel ingress and ignored which ECT value was in the outer 
header at the egress, instead reinstating the ECT values from the inner header.

>[DB]: As long as CE is tunneled through the inner header and not overwritten
>at tunnel egress (i.e., end receiver gets CE, not ECT(0) in received
>packet), this should be ok, as a router that would otherwise set CE
>doesn't do anything different with a packet that is already marked
>with CE vs. just marked with ECT.  Dropping a CE-packet doesn't change
>the reaction of a correct end-system and is not helpful to a correct
>end-system.

[BB]: A final process note:

As I said in the presentation last week, this draft currently aims to serve 
two purposes that I believe can both sit in one doc intended for PS:
1) A PS to bring 3168 into line with 4301
2) Informational guidance on the tunnelling constraints to consider 
if  defining new ECN field semantics for certain DS PHBs (like PCN) or for 
integrating IP congestion notification with lower layer protocols.

This leads to a potential for gridlock (or a race condition) with the PCN 
working group...

It would be wrong to bring RFC3168 into line with RFC4301 *before* PCN has 
decided its encoding, just in case there is something we can say in this 
ecn-tunnel doc that would ensure all tunnels 'just work' without special 
PCN modifications. IOW, the IETF needs to avoid the possibility of making 
two changes in quick succession to ECN tunnelling. Otherwise, the 
intermediate stage would create yet another tunnel endpoint variant that 
corresponding tunnel endpoints would have to check for.

But I wanted to have the guidance written down to improve the chances of 
the PCN w-g defining an encoding (chartered to be delivered to the IESG by 
Mar'08) so that tunnels would indeed 'just work' without special PCN 
modifications.

Even if I had split this draft into informational and PS parts, the PCN w-g 
need the informational part before Oct'07 for it to be useful. So, is it a 
reasonable approach to get the guidance in as good a shape as possible 
(thru discussions like this on the list) while still remaining as an 
individual draft? Then the PCN w-g can note the guidance in the knowledge 
it might be useful, but it is not fully baked or even formally adopted by 
the IETF. Thus relaxing the potential for gridlock.

Hope this helps.

Cheers


Bob


____________________________________________________________________________
Bob Briscoe, <bob.briscoe@bt.com>      Networks Research Centre, BT Research
B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 645196 







From tsvwg-bounces@ietf.org Tue Jul 31 22:08:18 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IG3dA-00068U-Kz; Tue, 31 Jul 2007 22:08:08 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IG3d9-00067q-Bj
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 31 Jul 2007 22:08:07 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IG3d8-00067g-VR
	for tsvwg@ietf.org; Tue, 31 Jul 2007 22:08:07 -0400
Received: from smtp1.smtp.bt.com ([217.32.164.137])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IG3d8-0005XU-2k
	for tsvwg@ietf.org; Tue, 31 Jul 2007 22:08:06 -0400
Received: from i2kc06-ukbr.domain1.systemhost.net ([193.113.197.70]) by
	smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Aug 2007 03:08:02 +0100
Received: from cbibipnt05.iuser.iroot.adidom.com ([147.149.196.177]) by
	i2kc06-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 1 Aug 2007 03:08:02 +0100
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 118593408133; Wed, 1 Aug 2007 03:08:01 +0100
Received: from mut.jungle.bt.co.uk ([10.86.0.9])
	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id
	l7127qgY015095; Wed, 1 Aug 2007 03:07:58 +0100
Message-Id: <5.2.1.1.2.20070801015324.04b7eb78@pop3.jungle.bt.co.uk>
X-Sender: rbriscoe@pop3.jungle.bt.co.uk
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Wed, 01 Aug 2007 03:02:41 +0100
To: Sally Floyd <sallyfloyd@mac.com>
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
In-Reply-To: <3144d54f51c807e534a10759210d5729@mac.com>
References: <5.2.1.1.2.20070617041232.04188110@pop3.jungle.bt.co.uk>
	<5.2.1.1.2.20070617041232.04188110@pop3.jungle.bt.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: -1.36 () ALL_TRUSTED
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 01 Aug 2007 02:08:02.0757 (UTC)
	FILETIME=[CA8AAF50:01C7D3E0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0770535483960d190d4a0d020e7060bd
Cc: PCN IETF list <pcn@ietf.org>, DCCP IETF list <dccp@ietf.org>,
	tsvwg IETF list <tsvwg@ietf.org>
Subject: [Tsvwg] Re: [dccp] Initial I-D: draft-briscoe-tsvwg-byte-pkt-mark-00
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Sally,

Again, catching up on my backlog - apologies for delayed reply...

At 00:30 20/07/2007, Sally Floyd wrote:
>Bob -
>
>Some feedback on "Byte and Packet Congestion Notification",
>draft-briscoe-tsvwg-byte-pkt-mark-00:
>
>It seems odd to me to talk about RED in byte vs. packet mode, and
>not to talk about the similar performance difference between
>Drop-Tail queues in bytes vs. packets.  (Well, someone could
>care about RED and not Drop-Tail because one cared only
>about packet marks in an ECN environment, but for this document
>it strikes me as quite odd to talk about RED in byte vs. packet mode,
>and not to talk also about Drop-Tail queues in bytes vs. packets.)
>
>I am enclosing some text from some 2/26/2007 email that I sent you
>about this, in response to "draft-briscoe-tsvwg-byte-pkt-mark-00c".
>(I didn't reread the new draft, but I did look at the diffs between
>draft-briscoe-tsvwg-byte-pkt-mark-00 and
>draft-briscoe-tsvwg-byte-pkt-mark-00c, and I didn't notice anything
>added about Drop-Tail queues in bytes vs. packets.)

After I had posted the draft, I realised I still hadn't taken this point 
you made into account. Sorry about that - it will be in the -01 update.

I tried to make up for this at least in my presentation in Chicago, where I 
warned people not to turn off RED altogether (actually, I hadn't read this 
latest email from you before last week's presentation, but I had remembered 
this excellent point you had made in your previous offlist email).

But I accept, there's a lot more to this issue that I need to address 
properly in the next draft.

> From my 2/26/2007 email:
>----------------------------------------------------------------
>"As is discussed at length and illustrated with simulations in [RFC
>4828], drop-tail queues also have a wide range of possible behaviors,
>in terms of dropping packets from a flow proportionally to the
>sending rate in bits per second, or to the sending rate in packets
>per second, or something else entirely.  For example, the abstract
>of [RFC 4828] includes the following:"
>
>     "Flows using TFRC-SP compete reasonably fairly with large-packet TCP
>     and TFRC flows in environments where large-packet flows and small-
>     packet flows experience similar packet drop rates.  However, in
>     environments where small-packet flows experience lower packet drop
>     rates than large-packet flows (e.g., with Drop-Tail queues in units
>     of bytes), TFRC-SP can receive considerably more than its share of
>     the bandwidth."
>
>"This is discussed more in Section 4.5.1, and in Appendix B.3 of that draft."

My immediate thought was that, if a vendor is implementing AQM, they are 
offering an alterantive to drop tail, so I was giving advice on whether to 
take a packet's size into account when deciding whether to drop it _in an 
AQM algorithm_.

You are right that my line of reasoning leads to the conclusion that I made 
- that transports should take account of packet size, not AQM algorithms.

You are right that transports using small packets will see less drop from 
unmodified (drop tail) queues. So if such transports scale down their 
response to smaller dropped packets (as TFRC-SP proposes), they will go 
faster than transports sending large packets that compete for the same 
drop-tail queue.

My reasoning then goes that we, the IETF, need to decide unequivocally 
where this bias should be reversed:
a) treat the cause, by recommending AQM with packet-mode drop wherever 
possible?
b) treat the symptom, by recommending transports don't take account of 
packet size?

The more successful we are at a), the more b) type solutions will be 
incorrect, and we will instead want transports to take account of packet size.

If we believed b) was the right approach, we shouldn't have ever 
recommended a). But it's too late to turn back, because we already 
recommended a) - largely because we wanted to remove the bias towards small 
packets of drop tail. And I believe RED is now very widely deployed (BT 
have certainly deployed it, and I believe it is common elsewhere).

I also believe a) was (and still is) the better path. I believe we should 
press on with a), encouraging AQM. Not turn back now. I also don't believe 
we can expect the industry to follow both paths, without adding 
considerable complexity to the Internet.

>"My understanding is that buffer architectures in routers can be
>complex, but one buffer architecture is to have a fixed number of
>slots for packet headers in the output queue, with the actual data
>packet stored elsewhere in the router.  So in this design, the queue
>would essentially have a fixed number of slots for packet headers,
>with each packet taking exactly one packet-header slot, regardless
>of the packet size in bytes.

This is surely the question of how to measure the queue length in order to 
decide an interim drop probability, not how to determine whether to modify 
the interim drop probability dependent on the size of the packet currently 
being considered for drop.

I believe I correctly reflected your advice on queue measurement in my 
sections 4 & 6.1.

>Functionally, this would be equivalent
>to a Drop-Tail queue in packets in NS.

I don't believe this is correct.
- As an overloaded drop tail queue forwards packets to the line, at any one 
time it is more likely to have made space for an arriving small packet than 
a large one. So the drop rate of larger packets will be greater.
- As an overloaded queue of fixed size headers forwards packets to the 
line, no more space is needed for the header of a large packet than a small 
one, so the drop rate of large and small packets will be the same (assuming 
the buffer for the payloads held elsewhere is not the limiting resource)

Am I missing something?

>But there could also be
>routers whose Drop-Tail queues are more like the Drop-Tail queue
>in bytes in NS, where small packets are more likely than large
>packets to find a slot in the queue.  So the complications are not
>only about AQM..."

The general point is true, that the complications are not only about AQM. 
Even tho I think the specific sentence I objected to above is wrong, it 
doesn't invalidate your general argument that this isn't only about AQM, 
which I hope I have addressed now, and I will also try to address more 
rigorously in the -01 update of this draft.

>----------------------------------------------------------------
>
>
>As an aside, in the future should I forward feedback about this draft to
>only one of the three mailing lists above?

I think tsvwg will be enough (as requested in the draft). I was just 
hiliting the existence of this draft to the other lists it was relevant to, 
but discussion not specific to one of the other w-gs need only be on tsvwg.

I've cc'd them one last time, so anyone who wants to follow this discussion 
knows where it has gone.

Cheers


Bob


____________________________________________________________________________
Bob Briscoe, <bob.briscoe@bt.com>      Networks Research Centre, BT Research
B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 645196 







From tsvwg-bounces@ietf.org Tue Jul 31 23:10:18 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IG4bD-00013D-I2; Tue, 31 Jul 2007 23:10:11 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IG4bC-00012x-J7
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 31 Jul 2007 23:10:10 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IG4bC-00012o-7X
	for tsvwg@ietf.org; Tue, 31 Jul 2007 23:10:10 -0400
Received: from smtp2.smtp.bt.com ([217.32.164.150])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IG4bA-0007J7-Sg
	for tsvwg@ietf.org; Tue, 31 Jul 2007 23:10:09 -0400
Received: from i2kc06-ukbr.domain1.systemhost.net ([193.113.197.70]) by
	smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Aug 2007 04:10:07 +0100
Received: from cbibipnt05.iuser.iroot.adidom.com ([147.149.196.177]) by
	i2kc06-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 1 Aug 2007 04:10:07 +0100
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 1185937805843; Wed, 1 Aug 2007 04:10:05 +0100
Received: from mut.jungle.bt.co.uk ([10.86.0.1])
	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id
	l7139xLU016206; Wed, 1 Aug 2007 04:10:03 +0100
Message-Id: <5.2.1.1.2.20070801031129.04a4ddb0@pop3.jungle.bt.co.uk>
X-Sender: rbriscoe@pop3.jungle.bt.co.uk
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Wed, 01 Aug 2007 04:09:59 +0100
To: dpapadimitriou@psg.com, dpapadimitriou@psg.com,
	dimitri.papadimitriou@alcatel-lucent.be
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
Subject: Re: [Tsvwg] Re: terminology issues in 
	draft-floyd-tsvwg-besteffort - flat monthly pricing
In-Reply-To: <46AEF6DC.2080104@psg.com>
References: <5.2.1.1.2.20070730181738.04a1c4b8@pop3.jungle.bt.co.uk>
	<5.2.1.1.2.20070726141117.04e7a828@pop3.jungle.bt.co.uk>
	<5.2.1.1.2.20070726141117.04e7a828@pop3.jungle.bt.co.uk>
	<5.2.1.1.2.20070730181738.04a1c4b8@pop3.jungle.bt.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: -1.36 () ALL_TRUSTED
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 01 Aug 2007 03:10:07.0210 (UTC)
	FILETIME=[767D1CA0:01C7D3E9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d16ce744298aacf98517bc7c108bd198
Cc: tsvwg IETF list <tsvwg@ietf.org>, Mark Allman <mallman@icir.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Dimitri,

At 09:46 31/07/2007, dimitri papadimitriou wrote:
>bob,
>
>see in-line
>
>>>you wrote:
>>>
>>>"so there won't be sufficient incentives for anyone to invest in more 
>>>capacity for those of us who want to use the Internet responsibly."
>>>
>>>this might be indeed a concern
>>>
>>>but as shorter life socialist ;-) i do also strongly believe that before 
>>>discussing the solution space we should first within the IETF community 
>>>at large come with a good, clear, and common understanding whether this 
>>>is a concern or not, if this is the case how important & urgent it might 
>>>be, have better understanding about of some of the root causes, etc.
>>I've been working in non-IETF fora where that issue has been debated for 
>>some years. That would be difficult for the IETF to do. It's difficult 
>>for economists to come to any conclusion on that issue. Partly because it 
>>gets convolved with monopoly issues in access networks.
>
>since you are trying to address a non technical problem with a technical 
>solution, there is a need for:
>- determining whether this is a concern that the ietf is willing to
>   address
>- understanding root causes and effects and how penalizing they are
>- the impact of the various mechanisms that could be put in place to
>   solve the issue(s)
>- whether the proposed solution really solves the problem for which they
>   have been defined (reliability) and whether the cure is not worse
>   than the disease itself (side effects)
>
>all these point deserve imho a much better documentation that what's 
>available and necessary in order to progress such effort

I agree. Many people have now clocked that there is probably a big problem 
here, but no-one (including me) has really quantified the problem, or the 
likely impact of the proposed solution (tho I have tried to _characterise_ 
the likely impact of my proposed solution in terms of how I expect the 
Internet might evolve).

I have an idea how to create a model to comapre the Internet with and 
without, and I've started a new research activity here in BT to quantify 
the problem at least by delivering a model and allowing people to see what 
the impact would be if they plug in assumptions that they believe are valid.

But, as the guy at this URL says:
<http://paperpicker.wordpress.com/2006/12/21/dismantling-a-religion-is-tcp-wrong/>
"It would be nice to see a simulation illustrating the difference, but that 
does not have to be Briscoe's job, of course. It is the networking research 
community who should react."


>>But in my view, the problem is a lot more basic - in the current Internet 
>>architecture there isn't even the basics of a mechanism to support 
>>resource allocation: accountability. That sounds like billing, but that's 
>>not what I mean. I mean being able to attribute a cost to a user or 
>>network (irrespective of what you do with the information).
>
>per rfc 2828, accountability is the property of a system or a service
>(including all of its system resources) that ensures that the actions of
>a system entity may be traced uniquely to that entity, so that it can be
>held responsible for its actions.

Yes. The solution I have proposed actually makes a leap here - it moves 
information about the effect of the entity's action towards the entity, 
rather than identifying the entity where its effect is felt.

>in the present case, i think you are referring to the process where
>users would be accountable for the openly accessible internet resources
>they are making use of

Exactly

>the main technical point is fairness rules & enforcement on responsible 
>internet's resources usage (outside of any market,business or economical 
>pressure)

That's not really the main technical point, which as you rightly point out 
is primarily about accountability. Fairness enforcement and better fairness 
are likely outcomes of accountability. They are secondary effects, that I 
predict will happen because of the invisible hand of economics - if we only 
had accountability. IOW, my tract on fairness was my attempt to answer your 
third bullet - on what impact there will be from introducing accountability.


>>It would be equivalent to a supermarket not being able to tell who had 
>>taken stuff off the shelves. I think most economists would agree that 
>>lack of accountability removes most incentives to invest if demand 
>>doesn't easily satiate (e.g. a provider has the incentive to keep 
>>investing in supplying all-you-can-eat buffet to people with limited 
>>stomach capacity, but if faced with a range of customers with huge 
>>stomachs, they tend to find other ways to limit demand - e.g. one plate each).
>
>hence, your concern is to limit the demand for economical reasons

That's not a good characterisation. My concern is to ensure either demand 
shrinks or supply grows - whichever users want. I certainly don't want to 
limit demand if it is true demand (rather than just desire or whim).

>mine, is to avoid starvation that could result if too big stomachs are 
>present at the same time for societal reasons

I would share with your concern (and Sally's) if I was proposing congestion 
pricing to end-users. But I don't believe congestion pricing will be common 
at all. I've proposed bulk per-user token bucket policers 
<draft-briscoe-tsvwg-re-ecn-04.txt>, which prevent small stomachs being 
starved except for short periods. I've also shown (in a paper on the likely 
impact on DDoS) why ISPs are likely to offer only token bucket policers to 
their users (which would tend to rule out starvation).
"Using Self-interest to Prevent Malice;
Fixing the Denial of Service Flaw of the Internet"
<http://www.cs.ucl.ac.uk/staff/B.Briscoe/projects/refb/#refb_dplinc>
It is an early workshop-style paper that outlines what we expect a more 
rigorous model would look like (ie it doesn't yet meet your requirement for 
more rigor). And I'm the first to admit, no-one can really predict how such 
subtle distinctions will play out.

All I can say is that each society will be able to control the outcome if 
it chooses to: ruling out starvation is possible with the technology I have 
proposed - but I don't believe such policy choices should be embedded in 
the technology that the IETF gives to the world. No matter how strongly 
some of us believe that starvation is wrong.


>hence, you see that one may have multitude of causes, different 
>motivations, multiple approaches to the problem and a set of resulting 
>solutions, all these points deserve much better analysis in my opinion

Of course. For many years now I've been working as hard as I can, but 
there's a limit to how much we can do - only a few of us have been rowing 
this boat. I hope I have brought it sufficiently to everyone's attention 
that a larger part of the research community will focus on the better 
analysis you'd like.

However, I believe TCP's lack of attention to flow durations alone is 
sufficient grounds for the IETF to be greatly concerned about the current 
resource control approach. We all already know the long-tailed distribution 
of flow durations, so we can all imagine just how bad resource allocations 
are going to be that don't take duration into account.


Bob


____________________________________________________________________________
Bob Briscoe, <bob.briscoe@bt.com>      Networks Research Centre, BT Research
B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 645196 







