
From lars.eggert@nokia.com  Tue May  3 05:52:49 2011
Return-Path: <lars.eggert@nokia.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8901EE0818 for <tsv-area@ietfa.amsl.com>; Tue,  3 May 2011 05:52:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.087
X-Spam-Level: 
X-Spam-Status: No, score=-104.087 tagged_above=-999 required=5 tests=[AWL=1.401, BAYES_00=-2.599, GB_I_INVITATION=-2, RCVD_IN_DNSWL_LOW=-1, SARE_NETPROD=0.111, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m7XhGJhevocn for <tsv-area@ietfa.amsl.com>; Tue,  3 May 2011 05:52:48 -0700 (PDT)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by ietfa.amsl.com (Postfix) with ESMTP id D6010E0769 for <tsv-area@ietf.org>; Tue,  3 May 2011 05:52:48 -0700 (PDT)
Received: from mail.fit.nokia.com (esdhcp030222.research.nokia.com [172.21.30.222]) by mgw-da01.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p43Cqkdi027690 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsv-area@ietf.org>; Tue, 3 May 2011 15:52:47 +0300
From: Lars Eggert <lars.eggert@nokia.com>
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.97 at fit.nokia.com
Content-Type: multipart/signed; boundary=Apple-Mail-1--297560833; protocol="application/pkcs7-signature"; micalg=sha1
Subject: FIVE DAYS REMAINING: Call for Nominations: Applied Networking Research Prize (ANRP)
Date: Tue, 3 May 2011 15:52:33 +0300
Message-Id: <F7B0D44A-8B72-4617-AC7D-C9737A52F3E7@nokia.com>
To: tsv-area@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mail.fit.nokia.com); Tue, 03 May 2011 15:52:39 +0300 (EEST)
X-Nokia-AV: Clean
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: anrp@isoc.org
List-Id: IETF Transport Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 May 2011 12:52:49 -0000

--Apple-Mail-1--297560833
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii


                CALL FOR NOMINATIONS:

       APPLIED NETWORKING RESEARCH PRIZE (ANRP)


*** Apply until May 8, 2011 for the ANR Prize for IETF-81,
*** July 24-29, 2011 in Quebec City, Canada!

The Applied Networking Research Prize (ANRP) is awarded for
recent results in applied networking research that are relevant
for transitioning into shipping Internet products and related
standardization efforts. Researchers with relevant, recently
published results are encouraged to apply for this prize, which
will offer them the opportunity to present and discuss their work
with the engineers, network operators, policy makers and
scientists that participate in the Internet Engineering Task
Force (IETF) and its research arm, the Internet Research Task
Force (IRTF). Third-party nominations for this prize are also
encouraged. The goal of the Applied Networking Research Prize
(ANRP) is to recognize the best new ideas in networking, and
bring them to the IETF and IRTF especially in cases where they
would not otherwise see much exposure or discussion.

The Applied Networking Research Prize (ANRP) consists of:

* cash prize of $500 (USD)

* invited talk at the IRTF Open Meeting

* travel grant to attend the week-long IETF meeting
 (airfare, hotel, registration, stipend)

* recognition at the IETF plenary

* invitation to related social activities

* potential for additional travel grants to future IETF
 meetings, based on community feedback

The Applied Networking Research Prize (ANRP) will be awarded
three times per year, in conjunction with the three annual IETF
meetings.


HOW TO APPLY

Applicants must nominate a peer-reviewed, recently-published,
original journal, conference or workshop paper. Both self
nominations (nominating one's own paper) and third-party
nominations (nominating someone else's paper) are encouraged. The
nominee must be one of the main authors of the nominated paper.

The nominated paper should provide a scientific foundation for
possible future IETF engineering work or IRTF experimentation,
analyze the behavior of Internet protocols in operational
deployments or realistic testbeds, make an important contribution
to the understanding of Internet scalability, performance,
reliability, security or capability, or otherwise be of relevance
to ongoing or future IETF or IRTF activities.

Applicants must briefly describe how the nominated paper relates
to these goals, and are encouraged to describe how presentation
of these research results will foster their transition into new
IETF engineering or IRTF experimentation, or otherwise seed new
activities that will have an impact on the real-world Internet.

The goal of the Applied Networking Research Prize (ANRP) is to
foster the transitioning of research results into real-world
benefits for the Internet. Therefore, applicants must indicate
that they (or the nominee, in case of third-party applications)
are available to attend the respective IETF meeting in person and
in its entirety.

Applications must include:

* the name and email address of the nominee

* a reference to the published nominated paper

* a PDF copy of the nominated paper

* a statement that describes how the nominated paper
 fulfills the goals of the award

* a statement that the nominee is available to attend the
 respective IETF meeting in person and in its entirety

* a brief biography or CV of the nominee

* optionally, any other supporting information (link to
 nominee's web site, etc.)

*** Applications are submitted by email to anrp@isoc.org. ***


SELECTION PROCESS

A small selection committee comprised of individuals
knowledgeable about the IRTF, IETF and the broader networking
research community will evaluate the submissions against these
selection criteria. The goal is to select 1-2 submissions for the
Applied Networking Research Prize (ANRP) during each application
period. All applicants will be notified by email.


IMPORTANT DATES

Applications open:      April 11, 2011
Applications close:     May 8, 2011
Notifications:          May 31, 2011
IETF-81 Meeting:        July 24-29, 2011


SPONSORS

The Applied Networking Research Prize (ANRP) is supported by the
Internet Society (ISOC), as part of its Internet Research Award
Programme, in coordination with the Internet Research Task Force
(IRTF).


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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMRjCCBVAw
ggQ4oAMCAQICEGxdPUZzCwUJ8KBiJwH+bYgwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMDEwMTUwMDAwMDBaFw0x
MTEwMTUyMzU5NTlaMIIBEzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEkMCIGCSqGSIb3DQEJARYVbGFycy5lZ2dlcnRAbm9r
aWEuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwolKEyOz/NQZJJlw0x9XBS9W
wCmabdY1fXpbWSdcaJiEWhQpRzSIC/pgIwCgaUW9g3JsWioXCawyjUVeg8xR42sR690f4z+OPAUm
3jokZxsuRaGX6fuPkPQomYAGz7htUHws/8FZIU+4dciETQf4vF5ptitJ+QZCVRCTLqisj6mG/kG4
65Op3G5/YZF9F/a390LdhuRP6vdY2Y+dqm8LDa0zmENPpoE98u1pIZGqCcnskN/nNBtEPd+a4lNh
ZSGnPuL4XCUSJYR9NB7FAYBvi5N7LSWHR3fspwa5EgpXynJcsLzaLA0iGfjFOBYFxul/07edmyw4
FIXuCIkaMDUfEwIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcX
ATAqMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIF
oDAdBgNVHSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDov
L2luZGMxZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3Js
MA0GCSqGSIb3DQEBBQUAA4IBAQAlSTzUKqa3ZouKWFQfIJ+4l/KsztPnY4Onwzt8lqAmeiFPqOmf
kLTXbXDKtC6caFadNtyHpnsmQFFKXwhe5Z9/AaVSwryu6F9992DzYLp3j8PE0DSU0wmpUXUtp+rz
TFqJRkzB8RCBoq/TPBmkMPr68qB0TkU3dbYiVIvscOt1MRkdHiwG4wKQLyCf8XRRWqmMY6lbun7g
kiEWiris5StGKRvE5+e1SrcdnoZxIKQFF7Etr+4ftClrsDQWX9nRCEjYcmz4y/deq+HU8ylBaKZE
0ZJmcnYlAaD50OYWi0ckGDnKYyeMUEtCZJSV0otm2LqyIUAu9WPv/GNHt2ntjnUaMIIG7jCCBdag
AwIBAgIQcRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAV
BgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTow
OAYDVQQLEzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5
MUUwQwYDVQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24g
QXV0aG9yaXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBO
ZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29t
L3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJp
U2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0B
AQEFAAOCAQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6Zvg
SU6Lb9UB0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHs
EnMhjfXcMM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO
4YM/d/mZ//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSy
riMGZSalJ1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCC
ArUwNAYIKwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20w
EgYDVR0TAQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUH
AgEWHGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWdu
LmNvbS9wY2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgw
VhYJaW1hZ2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDov
L2xvZ28udmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQ
cml2YXRlTGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYD
VR0jBIHpMIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4x
HzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlT
aWduLCBJbmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENs
YXNzIDEgUHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaE
VIULAM+vOEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlM
JBq6WaSHO3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKv
YLMVirOVnDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDR
yxTWcVibvtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy
+kgOZY5JyNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/
wYIxggSLMIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMu
MR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2Ug
YXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2Ny
aWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJ
AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDUwMzEyNTIzM1owIwYJKoZIhvcNAQkE
MRYEFHFoltvB42BDNruBrQj57QJ51YdlMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l
dHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlT
aWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEGxdPUZzCwUJ8KBiJwH+
bYgwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJt
cyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1
YWwgU3Vic2NyaWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMA0GCSqGSIb3DQEBAQUABIIB
AJmRbKjqLTtlxykYQQrrrdmaxW3/eVjUi1NbyXewqRq5eAP7RQz8I4sUsFV7b86NueRJ/UOaqBsY
ITi6tBBlcNYEeo5emnmLfoh7JrkH+iJ389hfApN8GZ/KS4Id+yooAqqYqkRjICdGtjq14AElQQHG
JXchQKoyRu+aDv8qoyXlmICcimiYKnDFBA/xHk+k0ZDIR35QsWwxdM9Fc1BNgKkqJEcQbJk9PMRc
cS/6Yn76MyVrFe/CE8yo01fKiB1Q22MbRJdghsGtYwGu6ZK10Wijyiz98lx/XrRQ7J+N05EC2nrH
yJ8+AJriyg1qimzcZVoORJiaLcWdWEWnY7fEJLAAAAAAAAA=

--Apple-Mail-1--297560833--

From dwing@cisco.com  Thu May  5 17:45:26 2011
Return-Path: <dwing@cisco.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF133E06FB; Thu,  5 May 2011 17:45:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.367
X-Spam-Level: 
X-Spam-Status: No, score=-110.367 tagged_above=-999 required=5 tests=[AWL=0.232, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ILHwr2wlgqhz; Thu,  5 May 2011 17:45:25 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by ietfa.amsl.com (Postfix) with ESMTP id CF422E06CF; Thu,  5 May 2011 17:45:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=3408; q=dns/txt; s=iport; t=1304642725; x=1305852325; h=from:to:subject:date:message-id:mime-version: content-transfer-encoding; bh=MgatDgcccnj+klpW+Rg/C15wpY7+y5+bae5wjxXkc/M=; b=QJx+3Xoeszjx4qtIHhqr8DsNLvOIfQxtvM5KfSa6A7GZqWWcltmi2tLE F9KWeErg8OP36/x4+ypNgSn9yk85g90bVfuEG7hGOTeYMdmqWkSH1wDzR aYbK8BFlp4H3Ieo2zS9ccyuFQtMaVOcCkgwq0wX/+Yt0x7hP/EXK05fbE Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAHpDw02rRDoG/2dsb2JhbACZfYxCd6gGniOGBwSGOJgB
X-IronPort-AV: E=Sophos;i="4.64,323,1301875200"; d="scan'208";a="309522647"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by sj-iport-3.cisco.com with ESMTP; 06 May 2011 00:42:58 +0000
Received: from dwingWS ([10.32.240.194]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p460gw2e016390; Fri, 6 May 2011 00:42:58 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'David Harrington'" <ietfdbh@comcast.net>, "'Transport Directorate'" <tsv-dir@ietf.org>, <tsv-area@ietf.org>, <draft-ietf-softwire-dual-stack-lite@tools.ietf.org>
Subject: TSVDIR review, draft-ietf-softwire-dual-stack-lite-08
Date: Thu, 5 May 2011 17:42:57 -0700
Message-ID: <034e01cc0b86$8b9eb8e0$a2dc2aa0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcwLhotQF09IEkEUQgq4rzA1nGrQvQ==
Content-Language: en-us
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 May 2011 00:45:26 -0000

I've reviewed this document as part of the transport area directorate's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the document's
authors for their information and to allow them to address any issues
raised. The authors should consider this review together with any other
last-call comments they receive. Please always CC  tsv-dir@ietf.org if you
reply to or forward this review.

This draft is basically ready for publication, but has nits that should be
fixed before publication:


In draft-ietf-softwire-dual-stack-lite-08, it says:

   8.3. Application Level Gateways (ALG)

   AFTR performs NAT-44 and inherits the limitations of NAT.  Some
   protocols require ALGs in the NAT device to traverse through the NAT.
   For example: SIP and ICMP require ALGs to work properly.

Three comments on that "For example:"

1. I do not believe SIP requires an ALG.

Here are three citations that SIP ALG is unnecessary:
 * ICE (RFC5245), which has the SIP endpoint do its own NAT traversal.  With
   this, a SIP ALG is unnecessary.
 * Session Border Controllers routinely implement 'media latching'
(described 
   in draft-ietf-mmusic-media-path-middleboxes), which works with endpoints
that
   don't implement ICE.  With this, a SIP ALG is unnecessary.
 * draft-ietf-sipping-nat-scenarios describes how all of this stuff works in
   great detail, and its Section 3 says SIP ALG is not required.

I worry that the IETF is requiring / suggesting / recommending that vendors
implement ALGs in NATs.  If the IETF were to make such a recommendation, it
needs to come from BEHAVE which is where the NAT work occurs, not SOFTWIRE.

Unless there is a citation that SIP ALG is necessary, please strike it.


2. "ALG" is an abbreviation for Application Layer Gateway, but ICMP is not
an application; it is a layer 4 protocol.  If anything, it is traditionally
considered a "layer 3.5", because it is not normally used for transport but
rather to signal the IP layer.  The term "ALG" is not appropriate when
discussing ICMP.  RFC5508, which describes the behavior of ICMP for NAT,
does not use the term ALG (or Application) when describing ICMP.  I suggest
simply striking "ICMP" from the example of protocols needing an ALG.

This also requires updating the text:

   This specification only requires that the AFTR MUST
   support [RFC5508].

by moving it out of the ALG section and to section 8.2 ("NAT Conformance")
where there are already citations for RFC4787 (UDP operation) and RFC5382
(TCP operation).  

I suggest striking the mention of RFC5508 from the ALG section and adding it
to Section 8.2 ("NAT Conformance"), like this:

OLD:
   A dual-stack lite AFTR MUST implement behavior conforming to the best
   current practice, currently documented in [RFC4787] and [RFC5382].
NEW:
   A dual-stack lite AFTR MUST implement behavior conforming to the best
   current practice, currently documented in [RFC4787], [RFC5382], and
.................................................................^^^^^
   [RFC5508].
...^^^^^^^^^


3. If the authors desire an example of a protocol that requires an ALG, a
good example is "active-mode FTP".  (Which is seldom used anymore, because
it requires an ALG!  It has been surpassed by passive-mode FTP.)

-d



From mcgrew@cisco.com  Tue May 10 16:04:03 2011
Return-Path: <mcgrew@cisco.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E7D7E06DC; Tue, 10 May 2011 16:04:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mrusk3EDEa05; Tue, 10 May 2011 16:04:00 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by ietfa.amsl.com (Postfix) with ESMTP id E0BF8E06CE; Tue, 10 May 2011 16:04:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mcgrew@cisco.com; l=5014; q=dns/txt; s=iport; t=1305068640; x=1306278240; h=cc:message-id:from:to:in-reply-to: content-transfer-encoding:mime-version:subject:date: references; bh=91PYmIY2f99aexEEb78LhybT9j0oOcNZR9TB+/uBEUw=; b=eIEoMX6DUjAawpRwIvGJryGRwcsoN2fOwN7nk2c6cgl5l44vwLgznd0I /ExYzZNJq0iZVCnuTf/u1RWcELH/8ZeyE0ki5bw6KP8Na6hOT/Em6dHYU Esv2Ks1X6UlY1mxVhUexxeMaAUQoIj1oq5ub4VzA0OS5QoXqAVUpKLSVL M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAJLDyU2rRDoH/2dsb2JhbACmDHeIcB2gH54khg8EhkKGVoJWjixV
X-IronPort-AV: E=Sophos;i="4.64,348,1301875200"; d="scan'208";a="695212342"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-6.cisco.com with ESMTP; 10 May 2011 23:04:00 +0000
Received: from stealth-10-32-254-213.cisco.com (stealth-10-32-254-213.cisco.com [10.32.254.213]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p4AN3wvw029465; Tue, 10 May 2011 23:03:59 GMT
Message-Id: <D1CCED3D-C041-4DA2-B999-D3EF7FC889D0@cisco.com>
From: David McGrew <mcgrew@cisco.com>
To: sqs@cs.stanford.edu, dm@uun.org, M.Handley@cs.ucl.ac.uk, mike@shiftleft.org, dabo@cs.stanford.edu, bittau@cs.stanford.edu
In-Reply-To: <4DC6C56D.6040709@ieca.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: [saag] fyi: tcpcrypt draft
Date: Tue, 10 May 2011 16:03:58 -0700
References: <4DC6C56D.6040709@ieca.com>
X-Mailer: Apple Mail (2.936)
X-Mailman-Approved-At: Wed, 11 May 2011 05:52:25 -0700
Cc: Sean Turner <turners@ieca.com>, tsv-area@ietf.org, saag@ietf.org
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2011 23:04:03 -0000

Hello Tcpcrypt authors,

I have skimmed the internet draft and the USENIX Security paper on  
tcpcrypt, and while it is interesting and thought-provoking work, I  
have a hard time understanding what the goals of the I-D are relative  
to the TCP standard.  The draft says "Standards Track"; would  
Experimental be more appropriate?  It mentions the following objectives:

"Tcpcrypt maintains the confidentiality of data transmitted in TCP  
segments against a passive eavesdropper.  It can be used to protect  
already established TCP connections against denial-of-service attacks  
involving injection of forged RST segments or desynchronizing of  
sequence numbers."  Yes, but TLS and IPsec perform the former  
function, and IPsec and TCP-AO perform the latter.  In addition,  
running TCP over DTLS would also accomplishes the latter function;  
this practice is done in some (so-called) SSLVPNs.

"Finally, applications that perform authentication can obtain end-to- 
end confidentiality and integrity guarantees by tying authentication  
to tcpcrypt Session ID values."  This seems like a potentially useful  
feature, though it seems similar to channel binding (RFCs 5056 and  
5929).

"Tcpcrypt is designed to require relatively low overhead, particularly  
at servers, so as to be useful even in the case of servers accepting  
many TCP connections per second."  The idea of batching signatures  
seems like a useful contribution that could be put to good use by  
servers that are under heavy loads.  But why not implement this idea  
in a way that could be used by multiple applications and protocols?    
It should not be hard to define a format for digital signatures that  
carries a few extra hash values, and allows a verifying party to check  
the signature on the message that they care about, while ignoring the  
rest.  The idea of reversing the client/server association between RSA  
encryption/decryption is a pragmatic way to help out servers, though  
it is tied to a specific algorithm (the results would be quite  
different for ECDH or ECDSA, say).  Both of those performance  
optimizations are definitely interesting, but I don't understand why  
the best way utilize those ideas would be through a new cryptographic  
protocol within the TCP layer.

I also have some comments on some other points.  The USENIX Security  
paper mentions the goal of ubiquitous encryption (though the draft  
does not).  Requiring changes to the TCP stack would hinder deployment  
and work against the goal of ubiquity.

The draft describes the RSA public keys as "ephemeral", and the  
companion paper says that the protocol achieves forward secrecy.   
However, if it was really the case that a new RSA keypair was  
generated for each exchange, then the performance would be  
significantly worse than what is shown in the paper, because the cost  
of that operation is significantly higher than that of RSA  
decryption.   I think the claims and/or guidance to implementers needs  
to be clarified.

The Security Considerations section looks like boilerplate, while it  
seems that there is a lot to be discussed, such as the security  
properties of Session IDs.

Is it possible to relate the protocol to a previously analyzed  
protocol?   It is similar to ISO/IEC 11770-3, in that it relies on  
public key encryption of nonces, without signatures.  Perhaps there is  
some analysis of that protocol, or of a protocol with cryptosuite  
negotiation, that could be leveraged.  The companion paper does have a  
brief analysis of the security of the protocol, but it would be good  
if it were possible to benefit from detailed analyses of all aspects  
of protocol security.  (I do realize that the analysis is made easier  
by the relative simplicity of the protocol; that's a good thing.)

The security analysis defines the parameter "k ~ 256 is the minimum of  
the min-entropy of a public key".  Surely that doesn't match the 2048- 
bit RSA examples in the paper?

As a side note, I am surprised to see a proposal to add so much  
cryptographic functionality into the TCP standard, considering that  
not many years have passed since the transport area declined to add  
(much simpler) key transport functionality into TCP in support of TCP- 
AO.  Perhaps "Experimental" was intended, or perhaps I have missed or  
misunderstood some aspect of this work.

regards,

David


On May 8, 2011, at 9:31 AM, Sean Turner wrote:

> The authors of the following draft have asked that I forward this to  
> saag for comment:
>
> https://datatracker.ietf.org/doc/draft-bittau-tcp-crypt/
>
> They also noted that there's a Usenix Security paper and video:
> http://tcpcrypt.org/docs.php
>
> Please direct discussion to tsv-area@ietf.org.
>
> Cheers,
>
> spt
>
>
>
> _______________________________________________
> saag mailing list
> saag@ietf.org
> https://www.ietf.org/mailman/listinfo/saag


From pgut001@login01.cs.auckland.ac.nz  Tue May 10 19:42:29 2011
Return-Path: <pgut001@login01.cs.auckland.ac.nz>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F675E06CE; Tue, 10 May 2011 19:42:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level: 
X-Spam-Status: No, score=-1 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2sCta0UaGldZ; Tue, 10 May 2011 19:42:29 -0700 (PDT)
Received: from mx2-int.auckland.ac.nz (mx2-int.auckland.ac.nz [130.216.12.41]) by ietfa.amsl.com (Postfix) with ESMTP id 81E33E06A2; Tue, 10 May 2011 19:42:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=pgut001@cs.auckland.ac.nz; q=dns/txt; s=uoa; t=1305081749; x=1336617749; h=from:to:subject:cc:in-reply-to:message-id:date; z=From:=20Peter=20Gutmann=20<pgut001@cs.auckland.ac.nz> |To:=20bittau@cs.stanford.edu,=20dabo@cs.stanford.edu,=20 dm@uun.org,=0D=0A=20=20=20=20M.Handley@cs.ucl.ac.uk,=20mc grew@cisco.com,=20mike@shiftleft.org,=0D=0A=20=20=20=20sq s@cs.stanford.edu|Subject:=20Re:=20[saag]=20fyi:=20tcpcry pt=20draft|Cc:=20saag@ietf.org,=20tsv-area@ietf.org |In-Reply-To:=20<D1CCED3D-C041-4DA2-B999-D3EF7FC889D0@cis co.com>|Message-Id:=20<E1QJzNR-0007S1-Bu@login01.fos.auck land.ac.nz>|Date:=20Wed,=2011=20May=202011=2014:42:17=20+ 1200; bh=6YEtBbses3elp0oh4Q3yTR6z2ks7Bx/pQTawO5qR418=; b=ej04mArL+HimjpDLfjbRyog0NFALWw9UjYsrBEVk/s/0gYSTndNla2iO /XZjWvvnS0iADtRD7vi0uEeofOUPU39dLknxvS/hx3Fib1W7p8tS2OAkL hP4SYLFkPC3l9x7ylBZFxct5PPIKiwVRfY+TAmHB8H76zLwgtL6FJN95E 0=;
X-IronPort-AV: E=Sophos;i="4.64,350,1301832000"; d="scan'208";a="61179905"
X-Ironport-HAT: APP-SERVERS - $RELAYED
X-Ironport-Source: 130.216.33.150 - Outgoing - Outgoing
Received: from mf1.fos.auckland.ac.nz ([130.216.33.150]) by mx2-int.auckland.ac.nz with ESMTP/TLS/AES256-SHA; 11 May 2011 14:42:17 +1200
Received: from login01.fos.auckland.ac.nz ([130.216.34.40]) by mf1.fos.auckland.ac.nz with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from <pgut001@login01.cs.auckland.ac.nz>) id 1QJzNR-0004LB-HT; Wed, 11 May 2011 14:42:17 +1200
Received: from pgut001 by login01.fos.auckland.ac.nz with local (Exim 4.69) (envelope-from <pgut001@login01.cs.auckland.ac.nz>) id 1QJzNR-0007S1-Bu; Wed, 11 May 2011 14:42:17 +1200
From: Peter Gutmann <pgut001@cs.auckland.ac.nz>
To: bittau@cs.stanford.edu, dabo@cs.stanford.edu, dm@uun.org, M.Handley@cs.ucl.ac.uk, mcgrew@cisco.com, mike@shiftleft.org, sqs@cs.stanford.edu
Subject: Re: [saag] fyi: tcpcrypt draft
In-Reply-To: <D1CCED3D-C041-4DA2-B999-D3EF7FC889D0@cisco.com>
Message-Id: <E1QJzNR-0007S1-Bu@login01.fos.auckland.ac.nz>
Date: Wed, 11 May 2011 14:42:17 +1200
X-Mailman-Approved-At: Wed, 11 May 2011 05:52:25 -0700
Cc: tsv-area@ietf.org, saag@ietf.org
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 May 2011 02:42:29 -0000

David McGrew <mcgrew@cisco.com> writes:

>I have a hard time understanding what the goals of the I-D are relative to
>the TCP standard.  The draft says "Standards Track"; would Experimental be
>more appropriate?

+1.  I've got it set aside for next week when I may have a bit more time to
look at it, but my first reaction was "why?".  I understand it's always fun to
dream up a new crypto protocol (Ferguson and Schneier wrote a whole book on
it), but... why?  It definitely seems like an Experimental to me, not
Standards-track.

Peter.

From nico@cryptonector.com  Tue May 10 19:59:22 2011
Return-Path: <nico@cryptonector.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 319ACE06A6; Tue, 10 May 2011 19:59:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.622
X-Spam-Level: 
X-Spam-Status: No, score=0.622 tagged_above=-999 required=5 tests=[FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1M5ZR1rH2lpR; Tue, 10 May 2011 19:59:21 -0700 (PDT)
Received: from homiemail-a36.g.dreamhost.com (caiajhbdcaid.dreamhost.com [208.97.132.83]) by ietfa.amsl.com (Postfix) with ESMTP id A8B02E065D; Tue, 10 May 2011 19:59:21 -0700 (PDT)
Received: from homiemail-a36.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a36.g.dreamhost.com (Postfix) with ESMTP id 6CB99778061; Tue, 10 May 2011 19:59:21 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=cryptonector.com; h=mime-version :in-reply-to:references:date:message-id:subject:from:to:cc :content-type:content-transfer-encoding; q=dns; s= cryptonector.com; b=GzgNoh5DK+YfgxzrQKZakylzONimZ1obIWQyNh6UooLZ Vb0eLjL24IQPvyjLkDckOPGEjKJBME8AK9R6rJJtXH5uP7CTAiFbBuugWlPbc8eD xJjWSZkcakFQr0QvygP1ugGroACyOQSGVaqfou+cHrAKe9P3vUq9jbexsnOruCo=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type:content-transfer-encoding; s= cryptonector.com; bh=j49Vg80nUmssmqW2THvpZa3wzg8=; b=jPXSdI1xIag hqCkgnNvZoeKNXq5dM/+iFw3F7CFraJJbB0fA2A7oCRmu5Ig0o3JWYHY3HPW8a4z FQ42NNlBhA2a2nsT460/GQFXIFUljz2AJWDZq3MZd73DMVHy4Uo6m0xepbJmlaQ1 DULE5/pxamASKBRCuyhM5tioKlZsE3QA=
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a36.g.dreamhost.com (Postfix) with ESMTPSA id 2ED7F77805F;  Tue, 10 May 2011 19:59:21 -0700 (PDT)
Received: by vws12 with SMTP id 12so66827vws.31 for <multiple recipients>; Tue, 10 May 2011 19:59:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.68.168 with SMTP id x8mr261161vdt.77.1305082760511; Tue, 10 May 2011 19:59:20 -0700 (PDT)
Received: by 10.52.155.4 with HTTP; Tue, 10 May 2011 19:59:20 -0700 (PDT)
In-Reply-To: <D1CCED3D-C041-4DA2-B999-D3EF7FC889D0@cisco.com>
References: <4DC6C56D.6040709@ieca.com> <D1CCED3D-C041-4DA2-B999-D3EF7FC889D0@cisco.com>
Date: Tue, 10 May 2011 21:59:20 -0500
Message-ID: <BANLkTik2qtvusCSDuPmSOrdv-PTrnci3-A@mail.gmail.com>
Subject: Re: [saag] fyi: tcpcrypt draft
From: Nico Williams <nico@cryptonector.com>
To: David McGrew <mcgrew@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Wed, 11 May 2011 05:52:24 -0700
Cc: dabo@cs.stanford.edu, dm@uun.org, bittau@cs.stanford.edu, sqs@cs.stanford.edu, tsv-area@ietf.org, saag@ietf.org, mike@shiftleft.org
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 May 2011 02:59:22 -0000

On Tue, May 10, 2011 at 6:03 PM, David McGrew <mcgrew@cisco.com> wrote:
> "Finally, applications that perform authentication can obtain end-to-end
> confidentiality and integrity guarantees by tying authentication to tcpcr=
ypt
> Session ID values." =C2=A0This seems like a potentially useful feature, t=
hough it
> seems similar to channel binding (RFCs 5056 and 5929).

That's exactly what it would, well, depending on the security
properties of those session ID values.

I would prefer that the channel binding data for tcpcrypt be derived
as a keyed PRF taken over the key exchange messages, with the key
being derived from the session key.  This approach has the benefit of
strongly binding the entire negotiation (e.g., of algorithms, ...) and
also being defined independently of the key exchange algorithm (which
is nice because you propose using key transport, but I can imagine
that some will want key agreement).

I'll review the I-D in detail later.

Nico
--

From nico@cryptonector.com  Tue May 10 20:00:43 2011
Return-Path: <nico@cryptonector.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E48CE06CE; Tue, 10 May 2011 20:00:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.622
X-Spam-Level: 
X-Spam-Status: No, score=0.622 tagged_above=-999 required=5 tests=[FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j4erPs2DmySP; Tue, 10 May 2011 20:00:43 -0700 (PDT)
Received: from homiemail-a28.g.dreamhost.com (caiajhbdccac.dreamhost.com [208.97.132.202]) by ietfa.amsl.com (Postfix) with ESMTP id 3D8EFE065D; Tue, 10 May 2011 20:00:43 -0700 (PDT)
Received: from homiemail-a28.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a28.g.dreamhost.com (Postfix) with ESMTP id 156E11B4059; Tue, 10 May 2011 20:00:43 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=cryptonector.com; h=mime-version :in-reply-to:references:date:message-id:subject:from:to:cc :content-type:content-transfer-encoding; q=dns; s= cryptonector.com; b=eaylnnDa1y/wrA7gjWSGbQeL0Z7rugX/Kum9GUGLX1vp 9iYeojl//T5vXSB2zPVpfxHF5bi0but/Xgypd6bDPrvQjz0Jgww4wDc/rNofbkcW TlewdKW/1aqcC1vb2JfK18o0IwacxeZebObK8mZArsxn+RQRWa00EotZlCsK/vo=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type:content-transfer-encoding; s= cryptonector.com; bh=UvtTAFclcddJuAe6/uguyak2bFU=; b=jqA0b3SUPtA c1YHYRLThCai5zi+3sNCEveRXRUYZ8hVHclUEMHF1DBSH1OqKblC88nqBUHJqAcl WuQKh94LytWShd3g0K2X59vrKUliF4hRP0XI3p++iz//l8q8w6eMIw8l+zEoVBap 79VwB+geFvcsox3liPxz5aH5aR44Pn3k=
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a28.g.dreamhost.com (Postfix) with ESMTPSA id CB9C01B4058;  Tue, 10 May 2011 20:00:42 -0700 (PDT)
Received: by vxg33 with SMTP id 33so65716vxg.31 for <multiple recipients>; Tue, 10 May 2011 20:00:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.73.170 with SMTP id m10mr2729820vdv.160.1305082842253; Tue, 10 May 2011 20:00:42 -0700 (PDT)
Received: by 10.52.155.4 with HTTP; Tue, 10 May 2011 20:00:42 -0700 (PDT)
In-Reply-To: <E1QJzNR-0007S1-Bu@login01.fos.auckland.ac.nz>
References: <D1CCED3D-C041-4DA2-B999-D3EF7FC889D0@cisco.com> <E1QJzNR-0007S1-Bu@login01.fos.auckland.ac.nz>
Date: Tue, 10 May 2011 22:00:42 -0500
Message-ID: <BANLkTi=weJhhYD81wT14MPxpyhYHub7xMg@mail.gmail.com>
Subject: Re: [saag] fyi: tcpcrypt draft
From: Nico Williams <nico@cryptonector.com>
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Wed, 11 May 2011 05:52:25 -0700
Cc: dabo@cs.stanford.edu, dm@uun.org, bittau@cs.stanford.edu, sqs@cs.stanford.edu, mcgrew@cisco.com, tsv-area@ietf.org, saag@ietf.org, mike@shiftleft.org
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 May 2011 03:00:43 -0000

On Tue, May 10, 2011 at 9:42 PM, Peter Gutmann
<pgut001@cs.auckland.ac.nz> wrote:
> David McGrew <mcgrew@cisco.com> writes:
>
>>I have a hard time understanding what the goals of the I-D are relative t=
o
>>the TCP standard. =C2=A0The draft says "Standards Track"; would Experimen=
tal be
>>more appropriate?
>
> +1. =C2=A0I've got it set aside for next week when I may have a bit more =
time to
> look at it, but my first reaction was "why?". =C2=A0I understand it's alw=
ays fun to
> dream up a new crypto protocol (Ferguson and Schneier wrote a whole book =
on
> it), but... why? =C2=A0It definitely seems like an Experimental to me, no=
t
> Standards-track.

Most likely because someone's thinking of putting this on silicon.
Sure, there's IPsec, but then you'd need to implement RFC5660 if you
want similar semantics, and no one has yet.

Nico
--

From yiu_lee@cable.comcast.com  Wed May 11 14:44:39 2011
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1532DE08A6; Wed, 11 May 2011 14:44:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.735
X-Spam-Level: 
X-Spam-Status: No, score=-101.735 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NCRstK0-1jBK; Wed, 11 May 2011 14:44:38 -0700 (PDT)
Received: from cable.comcast.com (copdcimo01.potomac.co.ndcwest.comcast.net [76.96.32.251]) by ietfa.amsl.com (Postfix) with ESMTP id 43EEEE089C; Wed, 11 May 2011 14:44:38 -0700 (PDT)
Received: from ([24.40.55.42]) by copdcimo01.cable.comcast.com with ESMTP with TLS id 5503630.38005794; Wed, 11 May 2011 15:48:37 -0600
Received: from PACDCEXMB05.cable.comcast.com ([fe80::a5b0:e5c4:df1b:2367]) by PACDCEXHUB01.cable.comcast.com ([fe80::d1e7:20b5:9b63:21a6%12]) with mapi id 14.01.0289.001; Wed, 11 May 2011 17:44:32 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: Dan Wing <dwing@cisco.com>, 'David Harrington' <ietfdbh@comcast.net>, 'Transport Directorate' <tsv-dir@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "draft-ietf-softwire-dual-stack-lite@tools.ietf.org" <draft-ietf-softwire-dual-stack-lite@tools.ietf.org>
Subject: Re: TSVDIR review, draft-ietf-softwire-dual-stack-lite-08
Thread-Topic: TSVDIR review, draft-ietf-softwire-dual-stack-lite-08
Thread-Index: AQHMECSclu/yiPYZnk+l7jo39BoXCQ==
Date: Wed, 11 May 2011 21:44:31 +0000
Message-ID: <C9F07A11.E56F%yiu_lee@cable.comcast.com>
In-Reply-To: <034e01cc0b86$8b9eb8e0$a2dc2aa0$@com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.0.101115
x-originating-ip: [68.82.20.172]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4EE1E38210A0BE4F8D0D0B5B4E603481@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 12 May 2011 06:38:09 -0700
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 May 2011 21:44:39 -0000

Hi Dan,

Thanks very much for spending the time to review it. Comments inline:

On 5/5/11 8:42 PM, "Dan Wing" <dwing@cisco.com> wrote:

>I've reviewed this document as part of the transport area directorate's
>ongoing effort to review key IETF documents. These comments were written
>primarily for the transport area directors, but are copied to the
>document's
>authors for their information and to allow them to address any issues
>raised. The authors should consider this review together with any other
>last-call comments they receive. Please always CC  tsv-dir@ietf.org if you
>reply to or forward this review.
>
>This draft is basically ready for publication, but has nits that should be
>fixed before publication:
>
>
>In draft-ietf-softwire-dual-stack-lite-08, it says:
>
>   8.3. Application Level Gateways (ALG)
>
>   AFTR performs NAT-44 and inherits the limitations of NAT.  Some
>   protocols require ALGs in the NAT device to traverse through the NAT.
>   For example: SIP and ICMP require ALGs to work properly.
>
>Three comments on that "For example:"
>
>1. I do not believe SIP requires an ALG.
>
>Here are three citations that SIP ALG is unnecessary:
> * ICE (RFC5245), which has the SIP endpoint do its own NAT traversal.
>With
>   this, a SIP ALG is unnecessary.
> * Session Border Controllers routinely implement 'media latching'
>(described=20
>   in draft-ietf-mmusic-media-path-middleboxes), which works with
>endpoints
>that
>   don't implement ICE.  With this, a SIP ALG is unnecessary.
> * draft-ietf-sipping-nat-scenarios describes how all of this stuff works
>in
>   great detail, and its Section 3 says SIP ALG is not required.
>
>I worry that the IETF is requiring / suggesting / recommending that
>vendors
>implement ALGs in NATs.  If the IETF were to make such a recommendation,
>it
>needs to come from BEHAVE which is where the NAT work occurs, not
>SOFTWIRE.
>
>Unless there is a citation that SIP ALG is necessary, please strike it.

[YL] When we wrote this section, we anticipated the class rfc3261 SIP
without ICE and SBC. I will take your advice to strike it.
=20
>
>
>2. "ALG" is an abbreviation for Application Layer Gateway, but ICMP is not
>an application; it is a layer 4 protocol.  If anything, it is
>traditionally
>considered a "layer 3.5", because it is not normally used for transport
>but
>rather to signal the IP layer.  The term "ALG" is not appropriate when
>discussing ICMP.  RFC5508, which describes the behavior of ICMP for NAT,
>does not use the term ALG (or Application) when describing ICMP.  I
>suggest
>simply striking "ICMP" from the example of protocols needing an ALG.
>
>This also requires updating the text:
>
>   This specification only requires that the AFTR MUST
>   support [RFC5508].
>
>by moving it out of the ALG section and to section 8.2 ("NAT Conformance")
>where there are already citations for RFC4787 (UDP operation) and RFC5382
>(TCP operation). =20
>
>I suggest striking the mention of RFC5508 from the ALG section and adding
>it
>to Section 8.2 ("NAT Conformance"), like this:
>
>OLD:
>   A dual-stack lite AFTR MUST implement behavior conforming to the best
>   current practice, currently documented in [RFC4787] and [RFC5382].
>NEW:
>   A dual-stack lite AFTR MUST implement behavior conforming to the best
>   current practice, currently documented in [RFC4787], [RFC5382], and
>.................................................................^^^^^
>   [RFC5508].
>...^^^^^^^^^
>

[YL] Agreed and will update the text to reflect this in next revision.

>
>3. If the authors desire an example of a protocol that requires an ALG, a
>good example is "active-mode FTP".  (Which is seldom used anymore, because
>it requires an ALG!  It has been surpassed by passive-mode FTP.)

[YL] I think this is worth to mention some protocols may not work (such as
active ftp). I will work on the text to bring it up but not give any
recommendation.

We will release the next revision very soon.

/Yiu=20

>
>-d
>
>


From yiu_lee@cable.comcast.com  Thu May 12 18:52:58 2011
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70E6213000C; Thu, 12 May 2011 18:52:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.735
X-Spam-Level: 
X-Spam-Status: No, score=-101.735 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mUburmDgJBJp; Thu, 12 May 2011 18:52:57 -0700 (PDT)
Received: from cable.comcast.com (copdcimo01.potomac.co.ndcwest.comcast.net [76.96.32.251]) by ietfa.amsl.com (Postfix) with ESMTP id B17BCE0593; Thu, 12 May 2011 18:52:57 -0700 (PDT)
Received: from ([24.40.55.40]) by copdcimo01.cable.comcast.com with ESMTP with TLS id 5503630.38219694; Thu, 12 May 2011 19:56:59 -0600
Received: from PACDCEXMB05.cable.comcast.com ([fe80::a5b0:e5c4:df1b:2367]) by pacdcexhub03.cable.comcast.com ([fe80::d1dd:b302:b617:3755%12]) with mapi id 14.01.0289.001; Thu, 12 May 2011 21:52:51 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: Dan Wing <dwing@cisco.com>, 'David Harrington' <ietfdbh@comcast.net>, 'Transport Directorate' <tsv-dir@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>
Subject: Re: TSVDIR review, draft-ietf-softwire-dual-stack-lite-08
Thread-Topic: TSVDIR review, draft-ietf-softwire-dual-stack-lite-08
Thread-Index: AQHMERB3lu/yiPYZnk+l7jo39BoXCQ==
Date: Fri, 13 May 2011 01:52:50 +0000
Message-ID: <C9F2070A.E711%yiu_lee@cable.comcast.com>
In-Reply-To: <034e01cc0b86$8b9eb8e0$a2dc2aa0$@com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.0.101115
x-originating-ip: [24.40.55.72]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D7D475AF8283DC4C9D29D4F376F0C634@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 13 May 2011 08:05:33 -0700
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 May 2011 01:52:58 -0000

Hi Dan,

We just released a new revision of the ds-lite draft. Did we address all
your comments?

Thanks,
Yiu



On 5/5/11 8:42 PM, "Dan Wing" <dwing@cisco.com> wrote:

>I've reviewed this document as part of the transport area directorate's
>ongoing effort to review key IETF documents. These comments were written
>primarily for the transport area directors, but are copied to the
>document's
>authors for their information and to allow them to address any issues
>raised. The authors should consider this review together with any other
>last-call comments they receive. Please always CC  tsv-dir@ietf.org if you
>reply to or forward this review.
>
>This draft is basically ready for publication, but has nits that should be
>fixed before publication:
>
>
>In draft-ietf-softwire-dual-stack-lite-08, it says:
>
>   8.3. Application Level Gateways (ALG)
>
>   AFTR performs NAT-44 and inherits the limitations of NAT.  Some
>   protocols require ALGs in the NAT device to traverse through the NAT.
>   For example: SIP and ICMP require ALGs to work properly.
>
>Three comments on that "For example:"
>
>1. I do not believe SIP requires an ALG.
>
>Here are three citations that SIP ALG is unnecessary:
> * ICE (RFC5245), which has the SIP endpoint do its own NAT traversal.
>With
>   this, a SIP ALG is unnecessary.
> * Session Border Controllers routinely implement 'media latching'
>(described=20
>   in draft-ietf-mmusic-media-path-middleboxes), which works with
>endpoints
>that
>   don't implement ICE.  With this, a SIP ALG is unnecessary.
> * draft-ietf-sipping-nat-scenarios describes how all of this stuff works
>in
>   great detail, and its Section 3 says SIP ALG is not required.
>
>I worry that the IETF is requiring / suggesting / recommending that
>vendors
>implement ALGs in NATs.  If the IETF were to make such a recommendation,
>it
>needs to come from BEHAVE which is where the NAT work occurs, not
>SOFTWIRE.
>
>Unless there is a citation that SIP ALG is necessary, please strike it.
>
>
>2. "ALG" is an abbreviation for Application Layer Gateway, but ICMP is not
>an application; it is a layer 4 protocol.  If anything, it is
>traditionally
>considered a "layer 3.5", because it is not normally used for transport
>but
>rather to signal the IP layer.  The term "ALG" is not appropriate when
>discussing ICMP.  RFC5508, which describes the behavior of ICMP for NAT,
>does not use the term ALG (or Application) when describing ICMP.  I
>suggest
>simply striking "ICMP" from the example of protocols needing an ALG.
>
>This also requires updating the text:
>
>   This specification only requires that the AFTR MUST
>   support [RFC5508].
>
>by moving it out of the ALG section and to section 8.2 ("NAT Conformance")
>where there are already citations for RFC4787 (UDP operation) and RFC5382
>(TCP operation). =20
>
>I suggest striking the mention of RFC5508 from the ALG section and adding
>it
>to Section 8.2 ("NAT Conformance"), like this:
>
>OLD:
>   A dual-stack lite AFTR MUST implement behavior conforming to the best
>   current practice, currently documented in [RFC4787] and [RFC5382].
>NEW:
>   A dual-stack lite AFTR MUST implement behavior conforming to the best
>   current practice, currently documented in [RFC4787], [RFC5382], and
>.................................................................^^^^^
>   [RFC5508].
>...^^^^^^^^^
>
>
>3. If the authors desire an example of a protocol that requires an ALG, a
>good example is "active-mode FTP".  (Which is seldom used anymore, because
>it requires an ALG!  It has been surpassed by passive-mode FTP.)
>
>-d
>
>


From dwing@cisco.com  Fri May 13 15:59:32 2011
Return-Path: <dwing@cisco.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71A39E08E6; Fri, 13 May 2011 15:59:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.339
X-Spam-Level: 
X-Spam-Status: No, score=-110.339 tagged_above=-999 required=5 tests=[AWL=0.260, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jNN5dmaD-VlM; Fri, 13 May 2011 15:59:31 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by ietfa.amsl.com (Postfix) with ESMTP id C64E8E08E3; Fri, 13 May 2011 15:59:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=4335; q=dns/txt; s=iport; t=1305327571; x=1306537171; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=7N4HdbF8HdcHS6C/JXLYQ6VetaqjPQTTcnp41GVfdlA=; b=J81W3P03t7nPD4hnKjxAT8ApIM7AvDl9GsraicbdSbPpfKAP+dtDqgRW fziN+DiFKm9AANQqe23AqGXNdwTyh8n7PGBk4oH02Qg+0wQUrc4YCfT/u arSfQ8RHIBt89WyI0L0iHnHZfBoat+WJHjOjZ7x0/pWGZyN1+vMjuswcV E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhEBAFW3zU2rRDoJ/2dsb2JhbACXUYFkjF93iHCeTZ14hhgEhlCYVg
X-IronPort-AV: E=Sophos;i="4.64,366,1301875200"; d="scan'208";a="697263056"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-6.cisco.com with ESMTP; 13 May 2011 22:59:31 +0000
Received: from dwingWS ([10.32.240.195]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p4DMxVD6018903; Fri, 13 May 2011 22:59:31 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Lee, Yiu'" <Yiu_Lee@Cable.Comcast.com>, "'David Harrington'" <ietfdbh@comcast.net>, "'Transport Directorate'" <tsv-dir@ietf.org>, <tsv-area@ietf.org>
References: <034e01cc0b86$8b9eb8e0$a2dc2aa0$@com> <C9F2070A.E711%yiu_lee@cable.comcast.com>
In-Reply-To: <C9F2070A.E711%yiu_lee@cable.comcast.com>
Subject: RE: TSVDIR review, draft-ietf-softwire-dual-stack-lite-08
Date: Fri, 13 May 2011 15:59:31 -0700
Message-ID: <005f01cc11c1$6b598150$420c83f0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHMERB3lu/yiPYZnk+l7jo39BoXCZSLYKfg
Content-Language: en-us
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 May 2011 22:59:32 -0000

> -----Original Message-----
> From: tsv-area-bounces@ietf.org [mailto:tsv-area-bounces@ietf.org] On
> Behalf Of Lee, Yiu
> Sent: Thursday, May 12, 2011 6:53 PM
> To: Dan Wing; 'David Harrington'; 'Transport Directorate'; tsv-
> area@ietf.org
> Subject: Re: TSVDIR review, draft-ietf-softwire-dual-stack-lite-08
> 
> Hi Dan,
> 
> We just released a new revision of the ds-lite draft. Did we address
> all your comments?

Yes, all my comments were addressed.

Thank you,
-d


> Thanks,
> Yiu
> 
> 
> 
> On 5/5/11 8:42 PM, "Dan Wing" <dwing@cisco.com> wrote:
> 
> >I've reviewed this document as part of the transport area
> directorate's
> >ongoing effort to review key IETF documents. These comments were
> written
> >primarily for the transport area directors, but are copied to the
> >document's
> >authors for their information and to allow them to address any issues
> >raised. The authors should consider this review together with any
> other
> >last-call comments they receive. Please always CC  tsv-dir@ietf.org if
> you
> >reply to or forward this review.
> >
> >This draft is basically ready for publication, but has nits that
> should be
> >fixed before publication:
> >
> >
> >In draft-ietf-softwire-dual-stack-lite-08, it says:
> >
> >   8.3. Application Level Gateways (ALG)
> >
> >   AFTR performs NAT-44 and inherits the limitations of NAT.  Some
> >   protocols require ALGs in the NAT device to traverse through the
> NAT.
> >   For example: SIP and ICMP require ALGs to work properly.
> >
> >Three comments on that "For example:"
> >
> >1. I do not believe SIP requires an ALG.
> >
> >Here are three citations that SIP ALG is unnecessary:
> > * ICE (RFC5245), which has the SIP endpoint do its own NAT traversal.
> >With
> >   this, a SIP ALG is unnecessary.
> > * Session Border Controllers routinely implement 'media latching'
> >(described
> >   in draft-ietf-mmusic-media-path-middleboxes), which works with
> >endpoints
> >that
> >   don't implement ICE.  With this, a SIP ALG is unnecessary.
> > * draft-ietf-sipping-nat-scenarios describes how all of this stuff
> works
> >in
> >   great detail, and its Section 3 says SIP ALG is not required.
> >
> >I worry that the IETF is requiring / suggesting / recommending that
> >vendors
> >implement ALGs in NATs.  If the IETF were to make such a
> recommendation,
> >it
> >needs to come from BEHAVE which is where the NAT work occurs, not
> >SOFTWIRE.
> >
> >Unless there is a citation that SIP ALG is necessary, please strike
> it.
> >
> >
> >2. "ALG" is an abbreviation for Application Layer Gateway, but ICMP is
> not
> >an application; it is a layer 4 protocol.  If anything, it is
> >traditionally
> >considered a "layer 3.5", because it is not normally used for
> transport
> >but
> >rather to signal the IP layer.  The term "ALG" is not appropriate when
> >discussing ICMP.  RFC5508, which describes the behavior of ICMP for
> NAT,
> >does not use the term ALG (or Application) when describing ICMP.  I
> >suggest
> >simply striking "ICMP" from the example of protocols needing an ALG.
> >
> >This also requires updating the text:
> >
> >   This specification only requires that the AFTR MUST
> >   support [RFC5508].
> >
> >by moving it out of the ALG section and to section 8.2 ("NAT
> Conformance")
> >where there are already citations for RFC4787 (UDP operation) and
> RFC5382
> >(TCP operation).
> >
> >I suggest striking the mention of RFC5508 from the ALG section and
> adding
> >it
> >to Section 8.2 ("NAT Conformance"), like this:
> >
> >OLD:
> >   A dual-stack lite AFTR MUST implement behavior conforming to the
> best
> >   current practice, currently documented in [RFC4787] and [RFC5382].
> >NEW:
> >   A dual-stack lite AFTR MUST implement behavior conforming to the
> best
> >   current practice, currently documented in [RFC4787], [RFC5382], and
> >.................................................................^^^^^
> >   [RFC5508].
> >...^^^^^^^^^
> >
> >
> >3. If the authors desire an example of a protocol that requires an
> ALG, a
> >good example is "active-mode FTP".  (Which is seldom used anymore,
> because
> >it requires an ALG!  It has been surpassed by passive-mode FTP.)
> >
> >-d
> >
> >


From Rolf.Winter@neclab.eu  Thu May 19 06:25:20 2011
Return-Path: <Rolf.Winter@neclab.eu>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADDC7E0656; Thu, 19 May 2011 06:25:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WmewQGyz8F+7; Thu, 19 May 2011 06:25:20 -0700 (PDT)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41]) by ietfa.amsl.com (Postfix) with ESMTP id ABFB5E066A; Thu, 19 May 2011 06:25:19 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.neclab.eu (Postfix) with ESMTP id 4F7952C00014B; Thu, 19 May 2011 15:25:18 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office.hd)
Received: from smtp0.neclab.eu ([127.0.0.1]) by localhost (atlas2.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p6hfz02OLru3; Thu, 19 May 2011 15:25:18 +0200 (CEST)
Received: from ENCELADUS.office.hd (ENCELADUS.office.hd [192.168.24.52]) by smtp0.neclab.eu (Postfix) with ESMTP id 32EB92C000087; Thu, 19 May 2011 15:24:58 +0200 (CEST)
Received: from PALLENE.office.hd ([169.254.1.225]) by ENCELADUS.office.hd ([192.168.24.52]) with mapi id 14.01.0270.001; Thu, 19 May 2011 15:24:58 +0200
From: Rolf Winter <Rolf.Winter@neclab.eu>
To: "draft-ietf-pwe3-fat-pw@tools.ietf.org" <draft-ietf-pwe3-fat-pw@tools.ietf.org>
Subject: tsv-dir review of draft-ietf-pwe3-fat-pw-06
Thread-Topic: tsv-dir review of draft-ietf-pwe3-fat-pw-06
Thread-Index: AcwWKCW9msdBC8rsRp2Fg158oYElsQ==
Date: Thu, 19 May 2011 13:24:58 +0000
Message-ID: <791AD3077F94194BB2BDD13565B6295D05E6A0F3@PALLENE.office.hd>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.6.28]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "tsv-dir@ietf.org" <tsv-dir@ietf.org>
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 May 2011 13:25:20 -0000

Hello,

I've reviewed this document as part of the transport area directorate's ong=
oing effort to review key IETF documents. These comments were written prima=
rily for the transport area directors, but are copied to the document's aut=
hors for their information and to allow them to address any issues raised. =
The authors should consider this review together with any other last-call c=
omments they receive. Please always CC tsv-dir@ietf.org if you reply to or =
forward this review.

Generally, this is a well written document. This draft is basically ready f=
or publication, but has a few nits the authors might consider before public=
ation.=20

And here go my comments. First a few on the content but most are purely edi=
torial.


CONTENT:

Section 3 says:
"If a flow LSE is present, it MUST be checked to determine whether it
carries a reserved label.  If it is a reserved label the packet is
processed according to the rules associated with that reserved label,
otherwise the LSE is discarded."
However section 1.2 states:=20
"Note that the flow label MUST NOT be an MPLS reserved label."
Isn't that a contradiction to a certain extend. I mean, if there is a reser=
ved label in the flow LSE, isn't that an error and should not be processed?

section 8.4:
The second bullet in the section under: "The issues described above are mit=
igated by the following two factors:". I wonder whether that isn't a bit fa=
rfetched. I mean, in principle you suggest that customers could change e.g.=
 the way their applications behave to let the ingress PE to be able to bett=
er apply the flow label. That sounds like asking a customer to change somet=
hing on their application end to have a better network connectivity.

section 8.5.
Isn't a bigger problem here that you cannot guarantee that the OAM packets =
follow the same ECMP path and that violates the fate sharing requirement?

section 12:
You essentially say that the behaviour of IP packets are well defined regar=
ding congestion and nothing needs to be done. Other payload needs to be dea=
lt with by PW congestion avoidance (whatever that means). So IP packets tha=
t are not reacting to congestion (such as UDP) are no concern but other pac=
kets with the same behaviour are? Is that a correct reading of the text?


EDITORIAL:

Abstract:=20
Remove the "END" at the end.

Intro:=20
page 3. first para: s/equipments[RFC4385]/equipments [RFC4385]/
page 3. first para: s/times )/times)/
page 3. fourth para: s/the type PW/the type of PW/
page 3. fourth para: s/[RFC5286] ./[RFC5286]./

section 1.2:
page 5. first para: s/which knows flow LSE/which knows a flow LSE/

section 2:
s/identify flows/identifies flows/

section 4:
page 7: s/is unable process/is unable to process/

section 4.1:
page 8: s/(seeSection 11 )/(see Section 11)/
page 8: s/T=3D 0/T=3D0/

section 7:
s/Ingress and Egress PE's/ingress and egress PEs/

section 8.1:
page 12: s/past[I-D.stein-pwe3-pwbonding]/past [I-D.stein-pwe3-pwbonding]/

section 8.3:
page 12: s/An example of such a case is the of the/An example of such a cas=
e is the one of the/ or /An example of such a case is the/

section 8.4:
Option one says: "The operator can choose to do nothing and the system will=
 work as it does without the flow label."
Isn't this option to not use the flow label. If so a better wording would m=
aybe be: "The operator can choose to do nothing, i.e. to not employ the flo=
w label"
Option 3: 2/flows,/flows./

Why is section 9 not section 8.7? I mean it is concerned with applicability=
 which is what section 8 is about.

section 9:

s/This is can be regarded as/This can be regarded as/

section 10:

s/be will preceded/be preceded/

section 12:

s/multiple ECMP/multiple ECMPs/

Best,

Rolf


NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London =
W3 6BL | Registered in England 2832014=20



From Michael.Scharf@alcatel-lucent.com  Sun May 29 01:46:38 2011
Return-Path: <Michael.Scharf@alcatel-lucent.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CC67E06F2; Sun, 29 May 2011 01:46:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HyU22JRAo-bw; Sun, 29 May 2011 01:46:37 -0700 (PDT)
Received: from mailrelay2.alcatel.de (mailrelay2.alcatel.de [194.113.59.96]) by ietfa.amsl.com (Postfix) with ESMTP id 815ADE0651; Sun, 29 May 2011 01:46:36 -0700 (PDT)
Received: from SLFSNX.rcs.alcatel-research.de (slfsn1.rcs.de.alcatel-lucent.com [149.204.60.98]) by mailrelay2.alcatel.de (8.14.3/8.14.3/ICT) with ESMTP id p4T8kZsD028231; Sun, 29 May 2011 10:46:35 +0200
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: tsv-dir review of draft-ietf-mpls-p2mp-lsp-ping
Date: Sun, 29 May 2011 10:46:33 +0200
Message-ID: <133D9897FB9C5E4E9DF2779DC91E947C0607B07B@SLFSNX.rcs.alcatel-research.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: tsv-dir review of draft-ietf-mpls-p2mp-lsp-ping
Thread-Index: Acwd3OmgB6NhbEENR9mZnjny5fpI/Q==
From: "SCHARF, Michael" <Michael.Scharf@alcatel-lucent.com>
To: <draft-ietf-mpls-p2mp-lsp-ping@tools.ietf.org>
X-Scanned-By: MIMEDefang 2.64 on 149.204.45.73
Cc: tsv-area@ietf.org, ietf@ietf.org, tsv-dir@ietf.org
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 May 2011 08:46:38 -0000

Hello,

I've reviewed this document as part of the transport area directorate's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the
document's authors for their information and to allow them to address
any issues raised. The authors should consider this review together with
any other last-call comments they receive. Please always CC
tsv-dir@ietf.org if you reply to or forward this review.

Disclaimer: Please note that I am a transport protocol researcher and
thus not familiar with details of the MPLS OAM mechanisms.

This draft is basically ready for publication, but there is an issue
that should be fixed before publication.=20


Content:
--------

The LSP ping relies on the "Echo Jitter TLV" to deal with the implosion
of feedback messages, which is important in order to avoid congestion.
However, there seems to be a SHOULD/MUST mismatch concerning the
required reaction:

- Section 3.3: "A responding node SHOULD wait a random amount of time
between zero milliseconds and the value specified in this field."

- Section 4.1.2: "If this TLV is present, the responding LSR MUST delay
sending a response for a random amount of time between zero milliseconds
and the value indicated in the TLV."



Editorial:
----------

Section 4.2.1.3:  s/like an combination/like a combination/



Best regards

Michael

From Michael.Scharf@alcatel-lucent.com  Sun May 29 01:48:32 2011
Return-Path: <Michael.Scharf@alcatel-lucent.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAC4DE06C2; Sun, 29 May 2011 01:48:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RGaxNx5axkDC; Sun, 29 May 2011 01:48:28 -0700 (PDT)
Received: from mailrelay2.alcatel.de (mailrelay2.alcatel.de [194.113.59.96]) by ietfa.amsl.com (Postfix) with ESMTP id 0134EE0651; Sun, 29 May 2011 01:48:27 -0700 (PDT)
Received: from SLFSNX.rcs.alcatel-research.de (slfsn1.rcs.de.alcatel-lucent.com [149.204.60.98]) by mailrelay2.alcatel.de (8.14.3/8.14.3/ICT) with ESMTP id p4T8mQdW028287; Sun, 29 May 2011 10:48:26 +0200
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: tsv-dir review of draft-ietf-mpls-lsp-ping-enhanced-dsmap
Date: Sun, 29 May 2011 10:48:25 +0200
Message-ID: <133D9897FB9C5E4E9DF2779DC91E947C0607B07C@SLFSNX.rcs.alcatel-research.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: tsv-dir review of draft-ietf-mpls-lsp-ping-enhanced-dsmap
Thread-Index: Acwd3SxYnf6WDq/yTZOKi5OiznC7+Q==
From: "SCHARF, Michael" <Michael.Scharf@alcatel-lucent.com>
To: <draft-ietf-mpls-lsp-ping-enhanced-dsmap@tools.ietf.org>
X-Scanned-By: MIMEDefang 2.64 on 149.204.45.73
Cc: tsv-area@ietf.org, ietf@ietf.org, tsv-dir@ietf.org
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 May 2011 08:48:33 -0000

Hello,

I've reviewed this document as part of the transport area directorate's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the
document's authors for their information and to allow them to address
any issues raised. The authors should consider this review together with
any other last-call comments they receive. Please always CC
tsv-dir@ietf.org if you reply to or forward this review.

Disclaimer: Please note that I am a transport protocol researcher and
thus not familiar with details of the MPLS OAM mechanisms.

Generally, draft-ietf-mpls-lsp-ping-enhanced-dsmap doesn't raise
apparent transport area issues. Thus, it seems to be ready for
publication. Several editorial nits are listed below.


Editorial:
----------

Abstract: s/a LSP/an LSP/
Section 2: s/a LDP/an LDP/
Section 3.3.1.3: s/include the the FEC Stack/include the FEC Stack/
(also note the inconsistent capitalization of "Stack" in this paragraph)
Section 3.3.1.3: s/E.g.  In the/E.g. in the/
Section 4.1.1: s/Figure 7.The label/Figure 7. The label/
Section 4.4: s/an Return Code/a Return Code/



Best regards

Michael

From adrian@olddog.co.uk  Sun May 29 10:03:27 2011
Return-Path: <adrian@olddog.co.uk>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04A66E0722; Sun, 29 May 2011 10:03:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.763
X-Spam-Level: 
X-Spam-Status: No, score=-2.763 tagged_above=-999 required=5 tests=[AWL=-0.164, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qIonjBhgftBz; Sun, 29 May 2011 10:03:24 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 50BF7E071B; Sun, 29 May 2011 10:03:24 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id p4TH3JFE026137;  Sun, 29 May 2011 18:03:19 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id p4TH3HuW026131 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 29 May 2011 18:03:18 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'SCHARF, Michael'" <Michael.Scharf@alcatel-lucent.com>, <draft-ietf-mpls-p2mp-lsp-ping@tools.ietf.org>
References: <133D9897FB9C5E4E9DF2779DC91E947C0607B07B@SLFSNX.rcs.alcatel-research.de>
In-Reply-To: <133D9897FB9C5E4E9DF2779DC91E947C0607B07B@SLFSNX.rcs.alcatel-research.de>
Subject: RE: tsv-dir review of draft-ietf-mpls-p2mp-lsp-ping
Date: Sun, 29 May 2011 18:03:16 +0100
Message-ID: <0ac601cc1e22$4e237650$ea6a62f0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-language: en-gb
Thread-index: AQFOj3/kTDL6WvhFcA2KLVIsu1/8ZZWfJMaw
X-Mailman-Approved-At: Sun, 29 May 2011 19:06:16 -0700
Cc: tsv-area@ietf.org, ietf@ietf.org, tsv-dir@ietf.org
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF Transport Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 May 2011 17:03:27 -0000

Excellent catch Michael!

Looks like that has been in place since the earliest text on jitter.

I'm going to suggest that it exists because 3.3 tries to cover all cases, where
4.1.2 separates P2MP and P2P cases. But it isn't a very convincing argument, and
the text needs to be fixed.

Cheers,
Adrian

> -----Original Message-----
> From: SCHARF, Michael [mailto:Michael.Scharf@alcatel-lucent.com]
> Sent: 29 May 2011 09:47
> To: draft-ietf-mpls-p2mp-lsp-ping@tools.ietf.org
> Cc: tsv-area@ietf.org; ietf@ietf.org; tsv-dir@ietf.org
> Subject: tsv-dir review of draft-ietf-mpls-p2mp-lsp-ping
> 
> Hello,
> 
> I've reviewed this document as part of the transport area directorate's
> ongoing effort to review key IETF documents. These comments were written
> primarily for the transport area directors, but are copied to the
> document's authors for their information and to allow them to address
> any issues raised. The authors should consider this review together with
> any other last-call comments they receive. Please always CC
> tsv-dir@ietf.org if you reply to or forward this review.
> 
> Disclaimer: Please note that I am a transport protocol researcher and
> thus not familiar with details of the MPLS OAM mechanisms.
> 
> This draft is basically ready for publication, but there is an issue
> that should be fixed before publication.
> 
> 
> Content:
> --------
> 
> The LSP ping relies on the "Echo Jitter TLV" to deal with the implosion
> of feedback messages, which is important in order to avoid congestion.
> However, there seems to be a SHOULD/MUST mismatch concerning the
> required reaction:
> 
> - Section 3.3: "A responding node SHOULD wait a random amount of time
> between zero milliseconds and the value specified in this field."
> 
> - Section 4.1.2: "If this TLV is present, the responding LSR MUST delay
> sending a response for a random amount of time between zero milliseconds
> and the value indicated in the TLV."
> 
> 
> 
> Editorial:
> ----------
> 
> Section 4.2.1.3:  s/like an combination/like a combination/
> 
> 
> 
> Best regards
> 
> Michael


From ssaxena@cisco.com  Sun May 29 21:32:32 2011
Return-Path: <ssaxena@cisco.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47D0BE06A5; Sun, 29 May 2011 21:32:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RKxPx2p+PWrq; Sun, 29 May 2011 21:32:30 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by ietfa.amsl.com (Postfix) with ESMTP id D9C5EE0655; Sun, 29 May 2011 21:32:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ssaxena@cisco.com; l=2678; q=dns/txt; s=iport; t=1306729950; x=1307939550; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=r/jEWh3trcA4eUnHw/giNOyQmtguidBV7HS8R8khoX0=; b=iqS3evFIIkWklHBl4YJNJde1p5Q2Bg63vEcREzNO+7bXv2rs0om8/je1 ZQWGOOladXCC51rJlATtCOo7n9esEmrQ77ihwfkz5FEvU6zJ4UJYucxxP MdFWFk5eC609UFxEVZC7qiByWg0NM8XfSygSEa5PwoqRYPnq0w4YRKyM7 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag4BAOgc402tJXHB/2dsb2JhbABVl1uOT3epA5xlhh4EhmSOMopx
X-IronPort-AV: E=Sophos;i="4.65,290,1304294400"; d="scan'208";a="286172509"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by sj-iport-4.cisco.com with ESMTP; 30 May 2011 04:32:29 +0000
Received: from xbh-rcd-102.cisco.com (xbh-rcd-102.cisco.com [72.163.62.139]) by rcdn-core2-6.cisco.com (8.14.3/8.14.3) with ESMTP id p4U4WT7u006538;  Mon, 30 May 2011 04:32:29 GMT
Received: from xmb-rcd-206.cisco.com ([72.163.62.213]) by xbh-rcd-102.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 29 May 2011 23:32:28 -0500
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: tsv-dir review of draft-ietf-mpls-p2mp-lsp-ping
Date: Sun, 29 May 2011 23:32:27 -0500
Message-ID: <C6921F0EC3DEDB419A67B42AB1EA213804F807C4@XMB-RCD-206.cisco.com>
In-Reply-To: <0ac601cc1e22$4e237650$ea6a62f0$@olddog.co.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: tsv-dir review of draft-ietf-mpls-p2mp-lsp-ping
Thread-Index: AQFOj3/kTDL6WvhFcA2KLVIsu1/8ZZWfJMawgADBC1A=
References: <133D9897FB9C5E4E9DF2779DC91E947C0607B07B@SLFSNX.rcs.alcatel-research.de> <0ac601cc1e22$4e237650$ea6a62f0$@olddog.co.uk>
From: "Shaleen Saxena (ssaxena)" <ssaxena@cisco.com>
To: <adrian@olddog.co.uk>, "SCHARF, Michael" <Michael.Scharf@alcatel-lucent.com>, <draft-ietf-mpls-p2mp-lsp-ping@tools.ietf.org>
X-OriginalArrivalTime: 30 May 2011 04:32:28.0514 (UTC) FILETIME=[953AC420:01CC1E82]
X-Mailman-Approved-At: Mon, 30 May 2011 18:08:58 -0700
Cc: "Shaleen Saxena \(ssaxena\)" <ssaxena@cisco.com>, tsv-area@ietf.org, ietf@ietf.org, tsv-dir@ietf.org
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 May 2011 04:32:32 -0000

Hi Michael, Adrian,

Thanks for the comments. I will update the document at the earliest and
send it out to all the authors before uploading the new version.

Regards,
Shaleen


-----Original Message-----
From: Adrian Farrel [mailto:adrian@olddog.co.uk]=20
Sent: Sunday, May 29, 2011 1:03 PM
To: 'SCHARF, Michael'; draft-ietf-mpls-p2mp-lsp-ping@tools.ietf.org
Cc: tsv-area@ietf.org; ietf@ietf.org; tsv-dir@ietf.org
Subject: RE: tsv-dir review of draft-ietf-mpls-p2mp-lsp-ping

Excellent catch Michael!

Looks like that has been in place since the earliest text on jitter.

I'm going to suggest that it exists because 3.3 tries to cover all
cases, where
4.1.2 separates P2MP and P2P cases. But it isn't a very convincing
argument, and
the text needs to be fixed.

Cheers,
Adrian

> -----Original Message-----
> From: SCHARF, Michael [mailto:Michael.Scharf@alcatel-lucent.com]
> Sent: 29 May 2011 09:47
> To: draft-ietf-mpls-p2mp-lsp-ping@tools.ietf.org
> Cc: tsv-area@ietf.org; ietf@ietf.org; tsv-dir@ietf.org
> Subject: tsv-dir review of draft-ietf-mpls-p2mp-lsp-ping
>=20
> Hello,
>=20
> I've reviewed this document as part of the transport area
directorate's
> ongoing effort to review key IETF documents. These comments were
written
> primarily for the transport area directors, but are copied to the
> document's authors for their information and to allow them to address
> any issues raised. The authors should consider this review together
with
> any other last-call comments they receive. Please always CC
> tsv-dir@ietf.org if you reply to or forward this review.
>=20
> Disclaimer: Please note that I am a transport protocol researcher and
> thus not familiar with details of the MPLS OAM mechanisms.
>=20
> This draft is basically ready for publication, but there is an issue
> that should be fixed before publication.
>=20
>=20
> Content:
> --------
>=20
> The LSP ping relies on the "Echo Jitter TLV" to deal with the
implosion
> of feedback messages, which is important in order to avoid congestion.
> However, there seems to be a SHOULD/MUST mismatch concerning the
> required reaction:
>=20
> - Section 3.3: "A responding node SHOULD wait a random amount of time
> between zero milliseconds and the value specified in this field."
>=20
> - Section 4.1.2: "If this TLV is present, the responding LSR MUST
delay
> sending a response for a random amount of time between zero
milliseconds
> and the value indicated in the TLV."
>=20
>=20
>=20
> Editorial:
> ----------
>=20
> Section 4.2.1.3:  s/like an combination/like a combination/
>=20
>=20
>=20
> Best regards
>=20
> Michael

