From tcpm-bounces@ietf.org  Mon Sep  1 20:49:14 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CA8FD3A685E;
	Mon,  1 Sep 2008 20:49:14 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 401513A685E
	for <tcpm@core3.amsl.com>; Mon,  1 Sep 2008 20:49:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id pwZJnlcxVe2m for <tcpm@core3.amsl.com>;
	Mon,  1 Sep 2008 20:49:13 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id E3B183A6781
	for <tcpm@ietf.org>; Mon,  1 Sep 2008 20:49:12 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,312,1217808000"; d="scan'208";a="150688951"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 02 Sep 2008 03:49:19 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m823nIRc022110; 
	Mon, 1 Sep 2008 20:49:18 -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.13.8/8.13.8) with ESMTP id m823nIvX021506;
	Tue, 2 Sep 2008 03:49:18 GMT
Received: from xmb-sjc-21c.amer.cisco.com ([171.70.151.176]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 1 Sep 2008 20:48:48 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 1 Sep 2008 20:47:32 -0700
Message-ID: <0C53DCFB700D144284A584F54711EC5805BB9166@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <48B86C64.6070903@isi.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
Thread-Index: AckKH87Hm4JbvPD0SnWQn+6wtcVnBACjDHyw
References: <FE34F27F-8DDF-4C94-BC6E-E2ABF6000309@windriver.com>
	<B5A5E01F9387F4409E67604C0257C71E409513@NDJSEVS25A.ndc.nasa.gov>
	<24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>
	<200808282159.m7SLx23E013917@venus.xmundo.net>
	<0C53DCFB700D144284A584F54711EC5805B5019B@xmb-sjc-21c.amer.cisco.com>
	<200808291948.m7TJmWUS006817@venus.xmundo.net>
	<48B86C64.6070903@isi.edu>
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: "Joe Touch" <touch@ISI.EDU>, "Fernando Gont" <fernando@gont.com.ar>
X-OriginalArrivalTime: 02 Sep 2008 03:48:48.0491 (UTC)
	FILETIME=[CE7CFBB0:01C90CAE]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1269; t=1220327358;
	x=1221191358; c=relaxed/simple; s=sjdkim4002;
	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[tcpm]=20WGLC=3A=20draft-ietf-tcpm-tcps
	ecure-10.txt |Sender:=20;
	bh=IKfzumCzRq013evMyaPi/EK5JjVArAJ8VCLAbWSOSgA=;
	b=haUk1CsN2MzK7EU7H2ktoXdXLbc+WocSYaDeliexv7/oeRSswV7FKwj8l1
	4CmWQ7d0eicjPDC6aA8UQcQiXPoxgI9GEDNrTU1laJZyHEl/8KV2lnNnpiDC
	/AMZFKQWAt;
Authentication-Results: sj-dkim-4; header.From=ananth@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: rrs@cisco.com, tcpm@ietf.org, David Borman <david.borman@windriver.com>,
	"Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

Joe,
 
> 
> However, I would be glad to credit Ananth with the large 
> number of 'attacks' on Postel's RFC793 design principle, "be 
> liberal in what you accept from others" from 1981. ;-)

Now, don't put me in attacker's shoes! :-) 

My point was : TCP secure has been hanging around for about 3 years and
other drafts which have been published later (some of which have become
RFC), all of them seem to want to add/change/modify a reference to those
in TCP secure, which keeps popping up now and then! I have no issues,
whatsoever, for putting relevant references, it is just that it it is
beginning to feel like a routine thing and that prompted my response to
Fernando about citing TCP secure as a reference in some of the those
drafts. 

I also agree that Watson's document should be mentioned in all these
drafts since it is the one which started talking about "slipping in the
window RST's......."

-Anantha

-Anantha
> 
> Joe
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iEYEARECAAYFAki4bGQACgkQE5f5cImnZrs5igCeKhNfbUiHweoYHQTvJDaxn/8L
> s7QAoMQvLTK91Nxg95tPnccyYwGULhp9
> =Ou+1
> -----END PGP SIGNATURE-----
> 
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Tue Sep  2 15:08:41 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E0ED83A69A9;
	Tue,  2 Sep 2008 15:08:41 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 847DC3A69A9
	for <tcpm@core3.amsl.com>; Tue,  2 Sep 2008 15:08:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, J_CHICKENPOX_33=0.6]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ECE9gqstYNm0 for <tcpm@core3.amsl.com>;
	Tue,  2 Sep 2008 15:08:39 -0700 (PDT)
Received: from owa.neterion.com (mx.neterion.com [72.1.205.142])
	by core3.amsl.com (Postfix) with ESMTP id A79C13A67FE
	for <tcpm@ietf.org>; Tue,  2 Sep 2008 15:08:39 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 2 Sep 2008 18:08:23 -0400
Message-ID: <78C9135A3D2ECE4B8162EBDCE82CAD770432FBD6@nekter>
In-Reply-To: <48b8a650.1cba720a.6f95.27a7@mx.google.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BULK]  [tcpm] TCP-AO: A position on NAT-T support
Thread-Index: AckKQnQ1dN7b/e4iTI2w136xvHCzewDBVatA
References: <48b8a650.1cba720a.6f95.27a7@mx.google.com>
From: "Caitlin Bestler" <Caitlin.Bestler@neterion.com>
To: "Gregory M. Lebovitz" <gregory.ietf@gmail.com>,
	<tcpm@ietf.org>
Subject: Re: [tcpm] [BULK]   TCP-AO: A position on NAT-T support
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

Gregory Lebovitz wrote:
> 
> 2. Not Every Protocol MUST Fill Every Requirement
> The IETF MUST give every app a way to simultaneously traverse NATs
> AND be authenticated. However, it does not necessarily follow that
> every protocol must have a way to simultaneously provide apps with
> NAT-T and authentication. As long as at least one or more protocols
> does allow a specific app to accomplish NAT-T + Authentication, we
> have succeeded. In other words, we need not burden every protocol
> with every use case. In the case of TCP connections, IKE+ESP can
> simultaneously provide NAT-T and Authentication, though at a costs of
> more processing and layering and configuration complexity.
> 

I agree.

TCP-AO should be kept simple and focused very specifically
on being a drop-in replacement for TCP-MD5. There should be
no expansion of its functionality unless it can be shown that
the additional application scenarios are NOT served by other
security solutions, and that the changes to the other
services would not be practical.

In my opinion that criteria would not be met by TCP-AO as
a whole, if there were not already applications finely tuned
to this specific security model. But those are *existing*
applications. New features are not used by existing applications,
and so the applications are free to use solutions other than
TCP-AO. We should encourage them to do so, rather than expanding
TCP-AO to be yet another "full service" security solution.

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Fri Sep  5 19:03:59 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D86293A6965;
	Fri,  5 Sep 2008 19:03:59 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 350153A6965
	for <tcpm@core3.amsl.com>; Fri,  5 Sep 2008 19:03:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id bi71JIp51l1k for <tcpm@core3.amsl.com>;
	Fri,  5 Sep 2008 19:03:53 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by core3.amsl.com (Postfix) with ESMTP id 6D5FE3A68A1
	for <tcpm@ietf.org>; Fri,  5 Sep 2008 19:03:53 -0700 (PDT)
Received: from zod.isi.edu (zod.isi.edu [128.9.168.221])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m861cX2s022703
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Fri, 5 Sep 2008 18:40:37 -0700 (PDT)
Received: (from faber@localhost)
	by zod.isi.edu (8.14.3/8.14.2/Submit) id m861cWhj030581;
	Fri, 5 Sep 2008 18:38:32 -0700 (PDT) (envelope-from faber)
Date: Fri, 5 Sep 2008 18:38:32 -0700
From: Ted Faber <faber@ISI.EDU>
To: David Borman <david.borman@windriver.com>
Message-ID: <20080906013831.GD2074@zod.isi.edu>
References: <FE34F27F-8DDF-4C94-BC6E-E2ABF6000309@windriver.com>
	<B5A5E01F9387F4409E67604C0257C71E409513@NDJSEVS25A.ndc.nasa.gov>
	<24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>
Mime-Version: 1.0
In-Reply-To: <24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>
User-Agent: Mutt/1.4.2.3i
X-url: http://www.isi.edu/~faber
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: faber@zod.isi.edu
Cc: rrs@cisco.com, tcpm@ietf.org,
	"Anantha Ramaiah \(ananth\)" <ananth@cisco.com>, mdalal@cisco.com
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1440093475=="
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org


--===============1440093475==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="5xSkJheCpeK0RUEJ"
Content-Disposition: inline


--5xSkJheCpeK0RUEJ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Aug 21, 2008 at 12:40:43PM -0500, David Borman wrote:
>=20
> Wes and I would like to start the WG Last Call for:
>=20
>  Title           : Improving TCP's Robustness to Blind In-Window =20
> Attacks'
>  Author(s)       : A. Ramaiah, R. Stewart & M. Dalal
>  Filename        : draft-ietf-tcpm-tcpsecure-10.txt
>  Pages           : 27
>  Date            : July 9, 2008
>  Intended Status : Proposed Standard
>=20
> http://www.ietf.org/internet-drafts/draft-ietf-tcpm-tcpsecure-10.txt
>=20
> It is our understanding that all the feedback has been incorporated =20
> into this latest version and that there are no known outstanding =20
> issues with this document.
>=20
> Please send feedback to the list, even if it is just a "yes, go ahead =20
> and publish".
>=20
> The WGLC will end on Friday, September 5, 2009.

Overall I think this is a good draft and should advance.  I have
comments, which I'll present in page order:

Probably the most technical comment I have is the objection to the
"There was no sound technical reasoning for choosing the Data mitigation
as MAY", which is on P15.

P2:
The 4-tuple is called a socket pair in 793.  Even if you don't want to
adopt that terminology, it's probably worth mentioning.  I also don't
like "RST, SYN or DATA segment."  These are TCP segments with the RST or
SYN flag set and I'd describe them that way.  ONce you've had a chance
to define "RST segment" as a segment with the RST bit set, you can use
the short form.

I'd delete "either" from "This can cause the connection to either abort
or possibly cause data corruption."  I'd consider deleting "possibly" as
well.

P4:

"The TCP spoofing attacks, which are seen in the Internet today," - I'd
say "The off-path TCP spoofing attacks".  We're still describing the
problem, so let's be clear.  The next paragraph starts with a
description of the attacks this draft cares about, but until then be
precise.

"... making the odds of guessing correctly the 4-tuple..."  I think
"correctly guessing" is more common.  I'd actually suggest "... making
it much easier to guess the 4-tuple."

P5:

"One of the important things to note is that, for the attack to succeed
the RST..." -> delete the comma.

"A slight enhancement to the TCP's segment processing" -> delete the
"the".

P6:

"Every application has control of a number of factors that effect
drastically the probability of a successful spoofing attack."  You mean
"affect" not "effect".  I'd also use "drastically affect" rather than
"affect drastically".  The order of the adverb is a matter of style,
using "affect" changes the meaning of the sentence to the one you
intend.

On the figures in the "To successfully inject a spoofed packet..."
paragraph:

1. Use parens, not [].
2. Finish the math.  If you want to say 1/2 * 2^32 =3D 2^31 rather than
just dropping 2^31 that's fine, but we're going to be comparing these
requirements, so don't hide the results.  "[SITW] shows that the mean
number of tries needed to inject a RST command is (2^31/window) rather
than the 2^31 assumed before."


P7:

"...please refer to draft [RFC4953]" -> "please refer to [RFC4953]"
It's not a draft any more.

P8:

Why use 1) and 2) and A), B), C)?  Pick one.

"The previous text, quoted from [RFC0793], woould thus become:" -> That
sounds a lot like we're mandating the change rather than it being a
SHOULD.  Do we really need this restatement at all?

P13:

"...so the chances of successfully injecting data into a connection are
1 in (2^32/RCV.WND *2)."  In describing the RST attacks, we spoke in
terms of mean number of tries, and I'd be consistent here.  Similarly
I'd do the math all the way: " ... so the mean number of tries needed to
inject data successfully is  2*2^32/RWND =3D 2^33/RCV.WND."

This section used a) and b) instead of either A) and B) or 1) and 2)
(used earlier for the same purpose). Again, pick one.

P15:

"There was no strong technical reasoning for choosing the Data mitigation
as MAY."
First, everywhere else the you use "DATA", I'd use it here.

Second, if I failed to make the case before, let me make it now.  The
DATA injection is 4 times less likely than either the RST or the SYN
attacks (2^33 vs 2^31) and may be visible to the application as garbled
data.  If the attack is visible an application can gracefully
terminate the connection and re-establish the conversation - unlike the
RST/SYN cases.  As the attack is harder to carry out, and a successful
attack may be easier to recover from, I recommend a MAY.  I don't care
if you repeat that argument, but I do believe that there are sound
technical reasons for the MAY, and I'd like to see the sentence that
started this comment elided.

P16:

"Currently there is no known bad behavior that can be attributed to the
lack of ACK throttling, but as a general principle, if ever invoked,
something incorrect is occurring and such a mechanism will act as a
failsafe that protects both the sender and the network." -> "While we
have not encountered a case where the lack of ACK throttling can be
exploited, as a fail-safe mechanism we recommend its use.  An
implementation may take an excessive number of invocations of the
throttling mechanism as an indication that network conditions are
unusual or hostile."

P18:

"...the middle box design does not comply to [RFC0793]."   No middlebox
complies with RFC793; I suggest "...the middle box is generating packets
a conformant TCP endpoint would not generate."

P22:

"ACK throttling was introduced to this document bt combining the
suggestions from the tcpm working group."  That seems out of place in
"Contributors".  That section is to acknowledge the efforts of
individuals.

P24:

Why are RFC's 4302 and 4303 normative?  And if they are why isn't
RFC2385?  They're all referred to as possible mitigations.  My
preference is making 4302 and 4303 non-normative, but it's very likely
that I'm missing a rule here.

Quotation marks are misplaced on the Medina05 reference.

The NISCC reference lacks a date.

P25:

Quotation marks are misplaced on the SITW reference.

--=20
Ted Faber
http://www.isi.edu/~faber           PGP: http://www.isi.edu/~faber/pubkeys.=
asc
Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#=
SIG

--5xSkJheCpeK0RUEJ
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkjB3xcACgkQaUz3f+Zf+Xu+NQCgriltzwFFDnPfgSqvcBpFYLQp
ijgAoMjUsHBL0sTY4gTP39ii+mkuapBN
=5AUt
-----END PGP SIGNATURE-----

--5xSkJheCpeK0RUEJ--

--===============1440093475==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm

--===============1440093475==--


From tcpm-bounces@ietf.org  Sun Sep  7 18:42:22 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0D0E03A6958;
	Sun,  7 Sep 2008 18:42:22 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B71CB3A68F0
	for <tcpm@core3.amsl.com>; Sun,  7 Sep 2008 18:42:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.253
X-Spam-Level: 
X-Spam-Status: No, score=-2.253 tagged_above=-999 required=5
	tests=[AWL=-3.207, BAYES_50=0.001, J_CHICKENPOX_23=0.6,
	J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_MED=-4, TVD_STOCK1=3.753]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Klq+8gL05tEL for <tcpm@core3.amsl.com>;
	Sun,  7 Sep 2008 18:42:18 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87])
	by core3.amsl.com (Postfix) with ESMTP id 1BBDD3A68E4
	for <tcpm@ietf.org>; Sun,  7 Sep 2008 18:42:18 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,354,1217808000"; d="scan'208";a="44713189"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-5.cisco.com with ESMTP; 08 Sep 2008 01:42:18 +0000
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m881gIMW028900; 
	Sun, 7 Sep 2008 18:42:18 -0700
Received: from dwingwxp01 ([10.32.240.194])
	by sj-core-4.cisco.com (8.13.8/8.13.8) with ESMTP id m881gIFc000614;
	Mon, 8 Sep 2008 01:42:18 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Gregory M. Lebovitz'" <gregory.ietf@gmail.com>, <tcpm@ietf.org>
References: <48b8a650.1cba720a.6f95.27a7@mx.google.com>
Date: Sun, 7 Sep 2008 18:42:18 -0700
Message-ID: <064c01c91154$21222260$c2f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-Mimeole: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: AckKQipECXFzb5+ASPOtbQjlNrdIxQHEYwAg
In-Reply-To: <48b8a650.1cba720a.6f95.27a7@mx.google.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=6374; t=1220838138;
	x=1221702138; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[tcpm]=20TCP-AO=3A=20A=20position=20on=
	20NAT-T=20support |Sender:=20;
	bh=DfLGjC7FtiOUmik2rxfYHGYd/UUCdM9MnfSRqeStAH8=;
	b=gp7Xhb++bF+gTUq0gm33blbjnpX89tu7MXL0tXgzIypn860Yenbh1pC2n0
	gHDBfQ//l5cNLPLdpuEnPJwTmE+JFIuNUn9JDyRTTX5JXEqtiDtQhUYMoFuN
	XCcg4QJW/V;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Subject: Re: [tcpm] TCP-AO: A position on NAT-T support
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

 

> -----Original Message-----
> From: tcpm-bounces@ietf.org [mailto:tcpm-bounces@ietf.org] On 
> Behalf Of Gregory M. Lebovitz
> Sent: Friday, August 29, 2008 6:46 PM
> To: tcpm@ietf.org
> Subject: [tcpm] TCP-AO: A position on NAT-T support
> 
> The question about whether or not TCP-AO should be designed for 
> NAT/NAPT traversal (NAT-T) has been bandied about some on the list. 
> My position: we SHOULD NOT design to support NAT-T. If NAT-T is a 
> requirement for an application, then TCP-AO is the wrong choice for 
> authentication protection. The application will need to be tunneled 
> over IPsec using IKE+ESP. The logic for this position follows.
> 
> 1. NAT-T Support is an Appropriate Requirement
> NATs exist. We may not want or like them, but they are there in the 
> network. Applications want to fulfill the simultaneous requirements 
> of being confidential and authenticated AND traversing NATs. The 
> standards must allow for the apps to do both simultaneously. On its 
> own, the requirement is sane and healthy.
> 
> 2. Not Every Protocol MUST Fill Every Requirement
> The IETF MUST give every app a way to simultaneously traverse NATs 
> AND be authenticated. However, it does not necessarily follow that 
> every protocol must have a way to simultaneously provide apps with 
> NAT-T and authentication. As long as at least one or more protocols 
> does allow a specific app to accomplish NAT-T + Authentication, we 
> have succeeded. In other words, we need not burden every protocol 
> with every use case. In the case of TCP connections, IKE+ESP can 
> simultaneously provide NAT-T and Authentication, though at a costs of 
> more processing and layering and configuration complexity.
> 
> 3. Designing for NAT-T in TCP-AO without tunneling MAY be impossible
> Supporting NAT-T means we design with the expectation that IP's and 
> ports will be changed in flight. However, we do not relax other 
> security requirements like replay protection. We need to solve for 
> both inter-connection replay attacks and intra-connection replay 
> attacks. In order to do this, we need to compute the integrity MAC 
> across something that includes message uniqueness at time "T", and do 
> so in a way that it would be almost impossible for the uniqueness to 
> be duplicated at some other time T-n. Today in AO we are going to use 
> Initial Sequence Numbers combined with Extended Sequence Numbers and 
> a MAC over the 5 tuple to ensure uniqueness of the session. In 
> essence, we use I/ESNs + src/dst IP + proto + src/dst Port as a 
> "connection ID". In order to support NAT-T we must remove src/dst IP 
> + src/dst Port from this calculation, because they may change after 
> NATing. What do we replace it with? After reviewing the few options 
> that do not include tunneling, one concludes that a fairly large (8 
> octets in ESP's case) unique Connection_ID integer is required to be 
> included in the Option header, covered by the MAC, along with 
> something else connection specific, like ISN. However, due to size 
> constraints on TCP Option header lengths, most agree we cannot afford 
> 8 octets for a Connection_ID field unless we also agree to change the 
> size of the Data Offset field itself in the TCP header. changing TCP 
> header fields is too big a hassle to be practically considered; the 
> cost-benefit analysis makes no sense in this case.
> 
> 4. Tunneling Works, and a Specification Exists
> If we can't change the bits in AO to allow for NAT-T directly, then 
> we fall back to creating a tunneling mechanism. In a tunneling 
> mechanism we MAC over the original IPs/Proto/Ports, and then we 
> encapsulate all that into another header that we know will easily get 
> through NATs, like UDP. We negotiate all this using a Key Management 
> Protocol (KMP). This would give us something like 
> APP-in-TCP-in-IP-in-FOO-in-IP. We process the MAC over the inner 
> packet and its 5-tuple, and leave the outer FOO-IP untouched. And it 
> works; NAT won't break things and we get integrity checking that 
> allows us to leverage the 5-tuple for connection identification 
> uniqueness. The downside is that the tunnel adds a processing stack 
> layer above the original solution, and complexity to the overall 
> configuration. The routing community has been averse to adding 
> another stack above the BGP-TCP, given that processing models for 
> BGP-TCP are now so well understood and so highly tuned on networking 
> devices. And it has been averse to the added complexity of the 
> tunneling mechanism. Should we conquer the tunneling aversion, we 
> already have a specified way to do integrity checks with a NAT-T 
> supporting tunneling mechanism: IKE+ESP with NULL-encryption. Since 
> we have a solution to the "create-a-tunnel" problem already, we need 
> not create another one.
> 
> 5. Summary of Options to support NAT-T
>   - Add Connection_ID field to AO and make the required change to the 
> Data Offset field in the TCP header. There appears to be VERY little 
> appetite for this option.
>   - Tunnel the IP+TCP in something in deployments where you need 
> NAT-T. In this case, employ tunnel and integrity check using 
> IKE+ESP-NULL.
> 
> 6. Recommendation:
> Do nothing wrt NAT-T support in TCP-AO. Add a section to TCP-AO spec 
> instructing those needing NAT-T to either tunnel in IKE + ESP-NULL, 
> or re-architect to remove the NAT and use TCP-AO.
> 
> Thoughts?

To your Recommendation, I would also add that, in the future, it may
be deemed important to make TCP-AO work, and that at this point in
time it seemed the best path forward would be an additional 8 bytes
of connection-id, and say such a design is 'for future study'.


Tunneling brings another drawbacks which you didn't mention -- it
breaks VJ header compression and breaks ROHC (RFC3095 and successors).  
Compressing headers is important on bandwidth constrained links (e.g.,
satellite, mobile wireless).

-d


> Gregory
> 
> +++++++++++++++++++++++
> IETF-related email from
> Gregory M. Lebovitz
> Juniper Networks
> g r e go r  y d o t  i e tf a t  g m a i l  do t c o  m 
> 
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Tue Sep  9 12:30:05 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 54AB93A6D57;
	Tue,  9 Sep 2008 12:30:05 -0700 (PDT)
X-Original-To: tcpm@ietf.org
Delivered-To: tcpm@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 7B7DB3A6A47; Tue,  9 Sep 2008 12:30:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20080909193001.7B7DB3A6A47@core3.amsl.com>
Date: Tue,  9 Sep 2008 12:30:01 -0700 (PDT)
Cc: tcpm@ietf.org
Subject: [tcpm] I-D Action:draft-ietf-tcpm-rfc4138bis-03.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-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 TCP Maintenance and Minor Extensions Working Group of the IETF.


	Title           : Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCP
	Author(s)       : P. Sarolahti, et al.
	Filename        : draft-ietf-tcpm-rfc4138bis-03.txt
	Pages           : 21
	Date            : 2008-09-09

Spurious retransmission timeouts cause suboptimal TCP performance
 because they often result in unnecessary retransmission of the last
 window of data.  This document describes the F-RTO detection
 algorithm for detecting spurious TCP retransmission timeouts.  F-RTO
 is a TCP sender-only algorithm that does not require any TCP options
 to operate.  After retransmitting the first unacknowledged segment
 triggered by a timeout, the F-RTO algorithm of the TCP sender
 monitors the incoming acknowledgments to determine whether the
 timeout was spurious.  It then decides whether to send new segments
 or retransmit unacknowledged segments.  The algorithm effectively
 helps to avoid additional unnecessary retransmissions and thereby
 improves TCP performance in the case of a spurious timeout.

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

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-tcpm-rfc4138bis-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-09-09121833.I-D@ietf.org>


--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm

--NextPart--


From tcpm-bounces@ietf.org  Fri Sep 12 13:35:01 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1DBD33A6846;
	Fri, 12 Sep 2008 13:35:01 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 284C63A6846
	for <tcpm@core3.amsl.com>; Fri, 12 Sep 2008 13:35:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Mh-Hwk4opYEU for <tcpm@core3.amsl.com>;
	Fri, 12 Sep 2008 13:34:59 -0700 (PDT)
Received: from mail.wrs.com (mail.windriver.com [147.11.1.11])
	by core3.amsl.com (Postfix) with ESMTP id 718203A6842
	for <tcpm@ietf.org>; Fri, 12 Sep 2008 13:34:58 -0700 (PDT)
Received: from ALA-MAIL03.corp.ad.wrs.com (ala-mail03 [147.11.57.144])
	by mail.wrs.com (8.13.6/8.13.6) with ESMTP id m8CKZ64M014751
	for <tcpm@ietf.org>; Fri, 12 Sep 2008 13:35:06 -0700 (PDT)
Received: from ala-mail06.corp.ad.wrs.com ([147.11.57.147]) by
	ALA-MAIL03.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 12 Sep 2008 13:35:04 -0700
Received: from dab-restive.wrs.com ([192.168.117.73]) by
	ala-mail06.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 12 Sep 2008 13:35:05 -0700
Message-Id: <86E8803E-B027-42A2-99B1-CCA255F1F775@windriver.com>
From: David Borman <david.borman@windriver.com>
To: tcpm@ietf.org
Mime-Version: 1.0 (Apple Message framework v926)
Date: Fri, 12 Sep 2008 15:35:03 -0500
References: <20080912164811.74CF63A6C4E@core3.amsl.com>
X-Mailer: Apple Mail (2.926)
X-OriginalArrivalTime: 12 Sep 2008 20:35:06.0195 (UTC)
	FILETIME=[0A88FA30:01C91517]
Subject: [tcpm] Fwd: Nomcom call for candidates
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

Apologies for duplicates.  It was requested that WG chairs forward  
this message to their WG mailing lists to get wider exposure.
			-David Borman

Begin forwarded message:

> The 2008-9 IETF Nominating Committee needs your help.
> We have started getting candidates.
> If we are going to do our job in time, we have only 3 more weeks to  
> get
> enough candidates to have a reasonable pool for all the jobs.
> At the moment, we do not have a reasonable pool for any jobs.
>
> If you are willing to serve, please nominate yourself.
> If there is someone you think would do a good job, please nominate  
> them.
>
> The web site at:
>    http://wiki.tools.ietf.org/group/nomcom/08
> Has the list of positions we are seeking people for, as well as  
> tools for
> providing both nominations and feedback.
>
> Alternatively, you can submit nominations by sending email to me.
>
> Please help us.
>
> Thank you,
> Joel M. Halpern
> jmh@joelhalpern.com
> nomcom-chair@ietf.org

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Tue Sep 16 11:38:05 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DE1EA28C0D6;
	Tue, 16 Sep 2008 11:38:05 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3A8103A6B54
	for <tcpm@core3.amsl.com>; Tue, 16 Sep 2008 11:38:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.629
X-Spam-Level: 
X-Spam-Status: No, score=-0.629 tagged_above=-999 required=5
	tests=[AWL=-0.141, BAYES_05=-1.11, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id iXM1JrGkUq0R for <tcpm@core3.amsl.com>;
	Tue, 16 Sep 2008 11:38:03 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.174])
	by core3.amsl.com (Postfix) with ESMTP id 4B8273A68CC
	for <tcpm@ietf.org>; Tue, 16 Sep 2008 11:38:02 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 27so2680920wfd.31
	for <tcpm@ietf.org>; Tue, 16 Sep 2008 11:38:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender
	:to:subject:mime-version:content-type:content-transfer-encoding
	:content-disposition:x-google-sender-auth;
	bh=qJqD8yJeraXXQ3JYxF2pwOxq2DEWXZ7Wro41viXVa38=;
	b=Emh2rfIhRDWuuPKrOKcZa0bn5q+MYxX+u9Zu7tdcUEjQrTAwF1vq4b/yvBi3Upl1b+
	9MR8/xfnQJD0bOyGbomX+Sd/C3MZc4hSYW2lBGeaRFb2PMoRyHlkX65FnGPUH5b5je1/
	bwAfLz0G6fS7tfLLTeVMuGbsgcQtdjQ67Mfjg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:mime-version:content-type
	:content-transfer-encoding:content-disposition:x-google-sender-auth;
	b=Q6Bdam4xpvjftn1ffM2Gwkej2+48iojdYY2KcVLIEHZRsvhPc3emD16aI/tG8C+oN2
	ZWNQV9iz0K+z6wUUKA/4+ER8AByrahQlnf5F2EWJqEgb9GmOVsNL6PwO/16xRh27xrtk
	7x87rtFmzlR9ZF9q4UQpsV1P7zF43T1N3v+A4=
Received: by 10.140.201.21 with SMTP id y21mr5888702rvf.259.1221590289158;
	Tue, 16 Sep 2008 11:38:09 -0700 (PDT)
Received: by 10.141.37.3 with HTTP; Tue, 16 Sep 2008 11:38:09 -0700 (PDT)
Message-ID: <396556a20809161138m26cd2e80q52006d2d795d9cb1@mail.gmail.com>
Date: Tue, 16 Sep 2008 11:38:09 -0700
From: "Adam Langley" <agl@imperialviolet.org>
To: tcpm@ietf.org
MIME-Version: 1.0
Content-Disposition: inline
X-Google-Sender-Auth: 8de952328af7dc8e
Subject: [tcpm] Probing the viability of TCP extensions
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

For my own gratification, if nothing else, I ran an experiment probing
for a few TCP behaviours on common webservers. Greg Chesson encouraged
me to write it up:

Abstract:

TCP was designed with extendibility in mind, chiefly re-
flected in the options mechanism. However, there have been
repeated observations of misbehaving middleware that have
hampered the deployment of beneficial TCP extensions.

This paper reports on an experiment to determine how preva-
lent three types of behaviour are. We find that 9.08% of
hosts don't respond to SYN frames with payloads, 0.17% of
hosts don't respond to SYN frames with non-standard op-
tions and 0.56% of hosts don't respond to SYN frames which
attempt to negotiate ECN.

http://www.imperialviolet.org/binary/ecntest.pdf

Comments welcome. If anyone thinks it worthwhile, I may submit it somewhere.


Cheers

AGL

-- 
Adam Langley agl@imperialviolet.org http://www.imperialviolet.org
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Tue Sep 16 14:30:03 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 782E328C265;
	Tue, 16 Sep 2008 14:30:03 -0700 (PDT)
X-Original-To: tcpm@ietf.org
Delivered-To: tcpm@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 9801228C1DF; Tue, 16 Sep 2008 14:30:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20080916213001.9801228C1DF@core3.amsl.com>
Date: Tue, 16 Sep 2008 14:30:01 -0700 (PDT)
Cc: tcpm@ietf.org
Subject: [tcpm] I-D ACTION:draft-ietf-tcpm-early-rexmt-00.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-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 TCP Maintenance and Minor Extensions Working Group of the IETF.

	Title		: Early Retransmit for TCP and SCTP
	Author(s)	: M. Allman, K. Avrachenkov, U. Ayesta, E. Blanton, P. Hurtig
	Filename	: draft-ietf-tcpm-early-rexmt-00.txt
	Pages		: 12
	Date		: 2008-8-28
	
This document proposes a new mechanism for TCP and SCTP that can be
    used to recover lost segments when a connection's congestion window
    is small.  The "Early Retransmit" mechanism allows the transport to
    reduce, in certain special circumstances, the number of duplicate
    acknowledgments required to trigger a fast retransmission.  This
    allows the transport to use fast retransmit to recover packet losses
    that would otherwise require a lengthy retransmission timeout.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tcpm-early-rexmt-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-tcpm-early-rexmt-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-9-16141919.I-D@ietf.org>


--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm

--NextPart--



From tcpm-bounces@ietf.org  Tue Sep 16 16:20:00 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6737E3A6809;
	Tue, 16 Sep 2008 16:20:00 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4FEA43A6452
	for <tcpm@core3.amsl.com>; Tue, 16 Sep 2008 16:19:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Level: 
X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5
	tests=[BAYES_20=-0.74]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id u6yvWE70154X for <tcpm@core3.amsl.com>;
	Tue, 16 Sep 2008 16:19:57 -0700 (PDT)
Received: from asmtpout012.mac.com (asmtpout012.mac.com [17.148.16.87])
	by core3.amsl.com (Postfix) with ESMTP id 70AA23A6809
	for <tcpm@ietf.org>; Tue, 16 Sep 2008 16:19:57 -0700 (PDT)
MIME-version: 1.0
Received: from [192.168.1.132] ([70.132.10.161])
	by asmtp012.mac.com (Sun Java(tm) System Messaging Server 6.3-7.03
	(built Aug
	7 2008; 32bit)) with ESMTPSA id <0K7B0061IA549FA0@asmtp012.mac.com> for
	tcpm@ietf.org; Tue, 16 Sep 2008 16:19:53 -0700 (PDT)
Message-id: <ECA34A8D-25B2-427F-AE18-DD6805D65323@mac.com>
From: Sally Floyd <sallyfloyd@mac.com>
To: Adam Langley <agl@imperialviolet.org>
In-reply-to: <396556a20809161138m26cd2e80q52006d2d795d9cb1@mail.gmail.com>
Date: Tue, 16 Sep 2008 16:19:52 -0700
References: <396556a20809161138m26cd2e80q52006d2d795d9cb1@mail.gmail.com>
X-Mailer: Apple Mail (2.928.1)
Cc: tcpm@ietf.org
Subject: Re: [tcpm] Probing the viability of TCP extensions
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

Adam -

 >For my own gratification, if nothing else, I ran an experiment probing
 >for a few TCP behaviours on common webservers. Greg Chesson encouraged
 >me to write it up:
...
> http://www.imperialviolet.org/binary/ecntest.pdf
...

Thanks.
I added a pointer to the paper on the TBIT web page
(TCP Behavior Inference) at
   "http://www.icir.org/tbit/".

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

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Thu Sep 18 05:42:53 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F096E3A6E2D;
	Thu, 18 Sep 2008 05:42:52 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 255CA3A6B5E;
	Thu, 18 Sep 2008 05:42:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.32
X-Spam-Level: 
X-Spam-Status: No, score=-6.32 tagged_above=-999 required=5 tests=[AWL=0.279, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id LqmECywaFxTS; Thu, 18 Sep 2008 05:42:45 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230])
	by core3.amsl.com (Postfix) with ESMTP id 1796C3A6E2B;
	Thu, 18 Sep 2008 05:42:44 -0700 (PDT)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m8ICfVeD000763; Thu, 18 Sep 2008 15:41:37 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 18 Sep 2008 15:41:31 +0300
Received: from dhcp137.dagstuhl.de ([10.241.184.208]) by
	esebh102.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.3959); Thu, 18 Sep 2008 15:41:30 +0300
Message-Id: <31E6C091-0710-4E63-9E93-AFA3C1417C03@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
To: "ext Black_David@emc.com" <Black_David@emc.com>
In-Reply-To: <9FA859626025B64FBC2AF149D97C944A3C6EEA@CORPUSMX80A.corp.emc.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 18 Sep 2008 14:41:24 +0200
References: <9FA859626025B64FBC2AF149D97C944A3C6EEA@CORPUSMX80A.corp.emc.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 18 Sep 2008 12:41:31.0394 (UTC)
	FILETIME=[E078EE20:01C9198B]
X-Nokia-AV: Clean
Cc: tcpm@ietf.org, david.borman@windriver.com, ietf@ietf.org, gen-art@ietf.org,
	fernando@gont.com.ar, weddy@grc.nasa.gov
Subject: Re: [tcpm] Gen-ART review of draft-ietf-tcpm-tcp-soft-errors-08.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

Hi,

I believe the gen-art comments need to be discussed before this  
document can move before the IESG.

Lars

On 2008-8-21, at 23:30, ext Black_David@emc.com wrote:

> I have been selected as the General Area Review Team (Gen-ART)
> reviewer for this draft (for background on Gen-ART, please see
> http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document: draft-ietf-tcpm-tcp-soft-errors-08.txt
> Reviewer: David L. Black
> Review Date: 21 August 2008
> IETF LC End Date: 26 August 2008
>
> Summary:
> This draft is on the right track, but has open issues, described
> in the review.
>
> Comments:
> This is a good draft reporting on problems encountered in practice
> with TCP's handling of ICMP errors and what has been done about
> them.  This draft has received extensive discussion in the Transport
> Area, and I believe it is wise to defer to the Transport Area decision
> that this draft will not make any changes to the TCP standard.
>
> While the draft is in generally good shape, I did find three open
> issues:
>
> (1) The I-D Tracker says that the v6ops-v6onbydefault draft is Dead.
> Relevant portions of that draft should be reproduced or otherwise
> explained in Section 3.2.  As part of doing this, please state
> whether trying v6 and v4 connections in parallel is a good idea or
> not and why.
>
> (2) Section 4.1 describes a mechanism from RFC 3168 that retransmits a
> modified SYN when an RST is received in response to an ECN-setup SYN,
> and suggests that this mechanism is applicable to ICMP errors received
> in response to an ECN-setup SYN.  This mechanism was specified in
> RFC 3168 because there were known deployed middleboxes with this
> problem-causing RST behavior, and the mechanism was necessary to deal
> with them.  Are there any known middleboxes that send an ICMP error
> in response to a SYN that signals ECN capability?
> - If yes, state the specific ICMP error(s) that is(are) used and limit
> 	the recommendation to the actual error(s).
> - If no, remove this entire RFC 3168 discussion as speculative, or
> 	describe it as a possible response should this problem scenario
> 	ever arise in practice.
>
> (3) Section 5.3 describes a NAT behavior that causes a host TCP  
> problem
> and then suggests changing the NAT to fix it.  While that's a good  
> idea
> in an ideal world (and needs to be stated in the draft), in practice,
> deployed NATs have to be dealt with as-is.  In addition to  
> recommending
> fixing the NAT, please discuss what could be done when the NAT cannot
> be fixed.
>
> Nits:
>
> Section 1 - reduce generality of this text.
> OLD:
>   This document analyzes the fault recovery strategy of TCP [RFC0793],
>   and the problems that may arise due to TCP's reaction to ICMP soft
>   errors.
> NEW:
>   This document analyzes problems that may arise due to TCP [RFC0793]
>   fault recovery reactions to ICMP soft errors.
>
> It would be good to provide the text expansion of the codes in
> Figure 1, as was done in the text before the figure.
>
> In section 4, please provide the expansion of TCPM WG (TCP Maintenance
> Working Group).
>
> idnits 2.08.10 ran clean.
>
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> 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
> ----------------------------------------------------

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Fri Sep 19 07:39:00 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DEAD43A6862;
	Fri, 19 Sep 2008 07:39:00 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 05B9A3A67EF
	for <tcpm@core3.amsl.com>; Fri, 19 Sep 2008 07:39:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id I9MNmSd+G3E7 for <tcpm@core3.amsl.com>;
	Fri, 19 Sep 2008 07:38:55 -0700 (PDT)
Received: from mail.wrs.com (mail.windriver.com [147.11.1.11])
	by core3.amsl.com (Postfix) with ESMTP id 2F1313A6887
	for <tcpm@ietf.org>; Fri, 19 Sep 2008 07:38:55 -0700 (PDT)
Received: from ALA-MAIL03.corp.ad.wrs.com (ala-mail03 [147.11.57.144])
	by mail.wrs.com (8.13.6/8.13.6) with ESMTP id m8JEd9f8010475;
	Fri, 19 Sep 2008 07:39:09 -0700 (PDT)
Received: from ala-mail06.corp.ad.wrs.com ([147.11.57.147]) by
	ALA-MAIL03.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 19 Sep 2008 07:39:08 -0700
Received: from dab-restive.wrs.com ([192.168.117.73]) by
	ala-mail06.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 19 Sep 2008 07:39:08 -0700
Message-Id: <8B8A001A-CA85-407B-9F1A-0FB1D847C21C@windriver.com>
From: David Borman <david.borman@windriver.com>
To: "Anantha Ramaiah (ananth)" <ananth@cisco.com>, rrs@cisco.com,
	mdalal@cisco.com
In-Reply-To: <20080906013831.GD2074@zod.isi.edu>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 19 Sep 2008 09:39:06 -0500
References: <FE34F27F-8DDF-4C94-BC6E-E2ABF6000309@windriver.com>
	<B5A5E01F9387F4409E67604C0257C71E409513@NDJSEVS25A.ndc.nasa.gov>
	<24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>
	<20080906013831.GD2074@zod.isi.edu>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 19 Sep 2008 14:39:08.0589 (UTC)
	FILETIME=[794D2DD0:01C91A65]
Cc: tcpm@ietf.org, Ted Faber <faber@isi.edu>
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

Hi,

I haven't seen any response from the authors on Ted's message.  We are  
well past the WGLC, but I would like the authors to address the issues  
that Ted brings up, and submit a new version of the draft before we  
pass this up to the IESG.  I haven't seen any other comments on this  
draft, so we are assuming that everyone else is happy with this  
version, after Ted's comments are addressed.

Once there is a new version available addressing Ted's comments, we'll  
pass this on to the IESG for publication as an RFC.  So, if anyone has  
further comments and neglected to speak up, now is the time to do so!

			-David Borman & Wes Eddy
			TCPM WG co-chairs

On Sep 5, 2008, at 8:38 PM, Ted Faber wrote:

> On Thu, Aug 21, 2008 at 12:40:43PM -0500, David Borman wrote:
>>
>> Wes and I would like to start the WG Last Call for:
>>
>> Title           : Improving TCP's Robustness to Blind In-Window
>> Attacks'
>> Author(s)       : A. Ramaiah, R. Stewart & M. Dalal
>> Filename        : draft-ietf-tcpm-tcpsecure-10.txt
>> Pages           : 27
>> Date            : July 9, 2008
>> Intended Status : Proposed Standard
>>
>> http://www.ietf.org/internet-drafts/draft-ietf-tcpm-tcpsecure-10.txt
>>
>> It is our understanding that all the feedback has been incorporated
>> into this latest version and that there are no known outstanding
>> issues with this document.
>>
>> Please send feedback to the list, even if it is just a "yes, go ahead
>> and publish".
>>
>> The WGLC will end on Friday, September 5, 2009.
>
> Overall I think this is a good draft and should advance.  I have
> comments, which I'll present in page order:
>
> Probably the most technical comment I have is the objection to the
> "There was no sound technical reasoning for choosing the Data  
> mitigation
> as MAY", which is on P15.
>
> P2:
> The 4-tuple is called a socket pair in 793.  Even if you don't want to
> adopt that terminology, it's probably worth mentioning.  I also don't
> like "RST, SYN or DATA segment."  These are TCP segments with the  
> RST or
> SYN flag set and I'd describe them that way.  ONce you've had a chance
> to define "RST segment" as a segment with the RST bit set, you can use
> the short form.
>
> I'd delete "either" from "This can cause the connection to either  
> abort
> or possibly cause data corruption."  I'd consider deleting  
> "possibly" as
> well.
>
> P4:
>
> "The TCP spoofing attacks, which are seen in the Internet today," -  
> I'd
> say "The off-path TCP spoofing attacks".  We're still describing the
> problem, so let's be clear.  The next paragraph starts with a
> description of the attacks this draft cares about, but until then be
> precise.
>
> "... making the odds of guessing correctly the 4-tuple..."  I think
> "correctly guessing" is more common.  I'd actually suggest "... making
> it much easier to guess the 4-tuple."
>
> P5:
>
> "One of the important things to note is that, for the attack to  
> succeed
> the RST..." -> delete the comma.
>
> "A slight enhancement to the TCP's segment processing" -> delete the
> "the".
>
> P6:
>
> "Every application has control of a number of factors that effect
> drastically the probability of a successful spoofing attack."  You  
> mean
> "affect" not "effect".  I'd also use "drastically affect" rather than
> "affect drastically".  The order of the adverb is a matter of style,
> using "affect" changes the meaning of the sentence to the one you
> intend.
>
> On the figures in the "To successfully inject a spoofed packet..."
> paragraph:
>
> 1. Use parens, not [].
> 2. Finish the math.  If you want to say 1/2 * 2^32 = 2^31 rather than
> just dropping 2^31 that's fine, but we're going to be comparing these
> requirements, so don't hide the results.  "[SITW] shows that the mean
> number of tries needed to inject a RST command is (2^31/window) rather
> than the 2^31 assumed before."
>
>
> P7:
>
> "...please refer to draft [RFC4953]" -> "please refer to [RFC4953]"
> It's not a draft any more.
>
> P8:
>
> Why use 1) and 2) and A), B), C)?  Pick one.
>
> "The previous text, quoted from [RFC0793], woould thus become:" ->  
> That
> sounds a lot like we're mandating the change rather than it being a
> SHOULD.  Do we really need this restatement at all?
>
> P13:
>
> "...so the chances of successfully injecting data into a connection  
> are
> 1 in (2^32/RCV.WND *2)."  In describing the RST attacks, we spoke in
> terms of mean number of tries, and I'd be consistent here.  Similarly
> I'd do the math all the way: " ... so the mean number of tries  
> needed to
> inject data successfully is  2*2^32/RWND = 2^33/RCV.WND."
>
> This section used a) and b) instead of either A) and B) or 1) and 2)
> (used earlier for the same purpose). Again, pick one.
>
> P15:
>
> "There was no strong technical reasoning for choosing the Data  
> mitigation
> as MAY."
> First, everywhere else the you use "DATA", I'd use it here.
>
> Second, if I failed to make the case before, let me make it now.  The
> DATA injection is 4 times less likely than either the RST or the SYN
> attacks (2^33 vs 2^31) and may be visible to the application as  
> garbled
> data.  If the attack is visible an application can gracefully
> terminate the connection and re-establish the conversation - unlike  
> the
> RST/SYN cases.  As the attack is harder to carry out, and a successful
> attack may be easier to recover from, I recommend a MAY.  I don't care
> if you repeat that argument, but I do believe that there are sound
> technical reasons for the MAY, and I'd like to see the sentence that
> started this comment elided.
>
> P16:
>
> "Currently there is no known bad behavior that can be attributed to  
> the
> lack of ACK throttling, but as a general principle, if ever invoked,
> something incorrect is occurring and such a mechanism will act as a
> failsafe that protects both the sender and the network." -> "While we
> have not encountered a case where the lack of ACK throttling can be
> exploited, as a fail-safe mechanism we recommend its use.  An
> implementation may take an excessive number of invocations of the
> throttling mechanism as an indication that network conditions are
> unusual or hostile."
>
> P18:
>
> "...the middle box design does not comply to [RFC0793]."   No  
> middlebox
> complies with RFC793; I suggest "...the middle box is generating  
> packets
> a conformant TCP endpoint would not generate."
>
> P22:
>
> "ACK throttling was introduced to this document bt combining the
> suggestions from the tcpm working group."  That seems out of place in
> "Contributors".  That section is to acknowledge the efforts of
> individuals.
>
> P24:
>
> Why are RFC's 4302 and 4303 normative?  And if they are why isn't
> RFC2385?  They're all referred to as possible mitigations.  My
> preference is making 4302 and 4303 non-normative, but it's very likely
> that I'm missing a rule here.
>
> Quotation marks are misplaced on the Medina05 reference.
>
> The NISCC reference lacks a date.
>
> P25:
>
> Quotation marks are misplaced on the SITW reference.
>
> -- 
> Ted Faber
> http://www.isi.edu/~faber           PGP: http://www.isi.edu/~faber/pubkeys.asc
> Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#SIG

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Fri Sep 19 08:47:11 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CB59A28C160;
	Fri, 19 Sep 2008 08:47:11 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D3CE628C114
	for <tcpm@core3.amsl.com>; Fri, 19 Sep 2008 08:47:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 2zKMLoT5DjgN for <tcpm@core3.amsl.com>;
	Fri, 19 Sep 2008 08:47:04 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id CDC4728C160
	for <tcpm@ietf.org>; Fri, 19 Sep 2008 08:47:04 -0700 (PDT)
Received: from [128.9.168.63] (bet.isi.edu [128.9.168.63])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m8JFhDh3013916
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Fri, 19 Sep 2008 08:43:15 -0700 (PDT)
Message-ID: <48D3C90A.5050301@isi.edu>
Date: Fri, 19 Sep 2008 08:45:14 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: David Borman <david.borman@windriver.com>
References: <FE34F27F-8DDF-4C94-BC6E-E2ABF6000309@windriver.com>	<B5A5E01F9387F4409E67604C0257C71E409513@NDJSEVS25A.ndc.nasa.gov>	<24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>	<20080906013831.GD2074@zod.isi.edu>
	<8B8A001A-CA85-407B-9F1A-0FB1D847C21C@windriver.com>
In-Reply-To: <8B8A001A-CA85-407B-9F1A-0FB1D847C21C@windriver.com>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tcpm@ietf.org, rrs@cisco.com, mdalal@cisco.com,
	"Anantha Ramaiah \(ananth\)" <ananth@cisco.com>, Ted Faber <faber@ISI.EDU>
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

One issue I'd like to re-confirm: we have, in this document, a
hierarchical use of the RFC2119 terms of MUST/SHOULD/MAY, i.e.:

whole doc: SHOULD
	certain portions are listed as MUST

i.e., "if SHOULD, then MUST..."

This is, based on recent discussions I've had with others while
explaining this off-list, an uncommon use of 2119 language AFAICT.

It would be useful to get IESG guidance on this; if such use is common,
then the doc can be left in its current form. If its use is uncommon but
desired, then we need to explain the issue in some detail (i.e., a whole
paragraph called out as a section, IMO). If its use is not desired by
the IESG, then we need to adjust the recommendations accordingly (i.e.,
all MUSTs would drop to SHOULDs).

Joe

David Borman wrote:
> Hi,
> 
> I haven't seen any response from the authors on Ted's message.  We are  
> well past the WGLC, but I would like the authors to address the issues  
> that Ted brings up, and submit a new version of the draft before we  
> pass this up to the IESG.  I haven't seen any other comments on this  
> draft, so we are assuming that everyone else is happy with this  
> version, after Ted's comments are addressed.
> 
> Once there is a new version available addressing Ted's comments, we'll  
> pass this on to the IESG for publication as an RFC.  So, if anyone has  
> further comments and neglected to speak up, now is the time to do so!
> 
> 			-David Borman & Wes Eddy
> 			TCPM WG co-chairs
> 
> On Sep 5, 2008, at 8:38 PM, Ted Faber wrote:
> 
>> On Thu, Aug 21, 2008 at 12:40:43PM -0500, David Borman wrote:
>>> Wes and I would like to start the WG Last Call for:
>>>
>>> Title           : Improving TCP's Robustness to Blind In-Window
>>> Attacks'
>>> Author(s)       : A. Ramaiah, R. Stewart & M. Dalal
>>> Filename        : draft-ietf-tcpm-tcpsecure-10.txt
>>> Pages           : 27
>>> Date            : July 9, 2008
>>> Intended Status : Proposed Standard
>>>
>>> http://www.ietf.org/internet-drafts/draft-ietf-tcpm-tcpsecure-10.txt
>>>
>>> It is our understanding that all the feedback has been incorporated
>>> into this latest version and that there are no known outstanding
>>> issues with this document.
>>>
>>> Please send feedback to the list, even if it is just a "yes, go ahead
>>> and publish".
>>>
>>> The WGLC will end on Friday, September 5, 2009.
>> Overall I think this is a good draft and should advance.  I have
>> comments, which I'll present in page order:
>>
>> Probably the most technical comment I have is the objection to the
>> "There was no sound technical reasoning for choosing the Data  
>> mitigation
>> as MAY", which is on P15.
>>
>> P2:
>> The 4-tuple is called a socket pair in 793.  Even if you don't want to
>> adopt that terminology, it's probably worth mentioning.  I also don't
>> like "RST, SYN or DATA segment."  These are TCP segments with the  
>> RST or
>> SYN flag set and I'd describe them that way.  ONce you've had a chance
>> to define "RST segment" as a segment with the RST bit set, you can use
>> the short form.
>>
>> I'd delete "either" from "This can cause the connection to either  
>> abort
>> or possibly cause data corruption."  I'd consider deleting  
>> "possibly" as
>> well.
>>
>> P4:
>>
>> "The TCP spoofing attacks, which are seen in the Internet today," -  
>> I'd
>> say "The off-path TCP spoofing attacks".  We're still describing the
>> problem, so let's be clear.  The next paragraph starts with a
>> description of the attacks this draft cares about, but until then be
>> precise.
>>
>> "... making the odds of guessing correctly the 4-tuple..."  I think
>> "correctly guessing" is more common.  I'd actually suggest "... making
>> it much easier to guess the 4-tuple."
>>
>> P5:
>>
>> "One of the important things to note is that, for the attack to  
>> succeed
>> the RST..." -> delete the comma.
>>
>> "A slight enhancement to the TCP's segment processing" -> delete the
>> "the".
>>
>> P6:
>>
>> "Every application has control of a number of factors that effect
>> drastically the probability of a successful spoofing attack."  You  
>> mean
>> "affect" not "effect".  I'd also use "drastically affect" rather than
>> "affect drastically".  The order of the adverb is a matter of style,
>> using "affect" changes the meaning of the sentence to the one you
>> intend.
>>
>> On the figures in the "To successfully inject a spoofed packet..."
>> paragraph:
>>
>> 1. Use parens, not [].
>> 2. Finish the math.  If you want to say 1/2 * 2^32 = 2^31 rather than
>> just dropping 2^31 that's fine, but we're going to be comparing these
>> requirements, so don't hide the results.  "[SITW] shows that the mean
>> number of tries needed to inject a RST command is (2^31/window) rather
>> than the 2^31 assumed before."
>>
>>
>> P7:
>>
>> "...please refer to draft [RFC4953]" -> "please refer to [RFC4953]"
>> It's not a draft any more.
>>
>> P8:
>>
>> Why use 1) and 2) and A), B), C)?  Pick one.
>>
>> "The previous text, quoted from [RFC0793], woould thus become:" ->  
>> That
>> sounds a lot like we're mandating the change rather than it being a
>> SHOULD.  Do we really need this restatement at all?
>>
>> P13:
>>
>> "...so the chances of successfully injecting data into a connection  
>> are
>> 1 in (2^32/RCV.WND *2)."  In describing the RST attacks, we spoke in
>> terms of mean number of tries, and I'd be consistent here.  Similarly
>> I'd do the math all the way: " ... so the mean number of tries  
>> needed to
>> inject data successfully is  2*2^32/RWND = 2^33/RCV.WND."
>>
>> This section used a) and b) instead of either A) and B) or 1) and 2)
>> (used earlier for the same purpose). Again, pick one.
>>
>> P15:
>>
>> "There was no strong technical reasoning for choosing the Data  
>> mitigation
>> as MAY."
>> First, everywhere else the you use "DATA", I'd use it here.
>>
>> Second, if I failed to make the case before, let me make it now.  The
>> DATA injection is 4 times less likely than either the RST or the SYN
>> attacks (2^33 vs 2^31) and may be visible to the application as  
>> garbled
>> data.  If the attack is visible an application can gracefully
>> terminate the connection and re-establish the conversation - unlike  
>> the
>> RST/SYN cases.  As the attack is harder to carry out, and a successful
>> attack may be easier to recover from, I recommend a MAY.  I don't care
>> if you repeat that argument, but I do believe that there are sound
>> technical reasons for the MAY, and I'd like to see the sentence that
>> started this comment elided.
>>
>> P16:
>>
>> "Currently there is no known bad behavior that can be attributed to  
>> the
>> lack of ACK throttling, but as a general principle, if ever invoked,
>> something incorrect is occurring and such a mechanism will act as a
>> failsafe that protects both the sender and the network." -> "While we
>> have not encountered a case where the lack of ACK throttling can be
>> exploited, as a fail-safe mechanism we recommend its use.  An
>> implementation may take an excessive number of invocations of the
>> throttling mechanism as an indication that network conditions are
>> unusual or hostile."
>>
>> P18:
>>
>> "...the middle box design does not comply to [RFC0793]."   No  
>> middlebox
>> complies with RFC793; I suggest "...the middle box is generating  
>> packets
>> a conformant TCP endpoint would not generate."
>>
>> P22:
>>
>> "ACK throttling was introduced to this document bt combining the
>> suggestions from the tcpm working group."  That seems out of place in
>> "Contributors".  That section is to acknowledge the efforts of
>> individuals.
>>
>> P24:
>>
>> Why are RFC's 4302 and 4303 normative?  And if they are why isn't
>> RFC2385?  They're all referred to as possible mitigations.  My
>> preference is making 4302 and 4303 non-normative, but it's very likely
>> that I'm missing a rule here.
>>
>> Quotation marks are misplaced on the Medina05 reference.
>>
>> The NISCC reference lacks a date.
>>
>> P25:
>>
>> Quotation marks are misplaced on the SITW reference.
>>
>> -- 
>> Ted Faber
>> http://www.isi.edu/~faber           PGP: http://www.isi.edu/~faber/pubkeys.asc
>> Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#SIG
> 
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFI08kKE5f5cImnZrsRAuMoAJ43+3GJLSi5p7zEOkvLZtuzYfeV0gCg5x7N
yqGeykNAk2sBFupRaFqmo3s=
=VG60
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Fri Sep 19 09:34:01 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4A1873A68E7;
	Fri, 19 Sep 2008 09:34:01 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3A3AD3A6843
	for <tcpm@core3.amsl.com>; Fri, 19 Sep 2008 09:34:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ioIGRULjMYb1 for <tcpm@core3.amsl.com>;
	Fri, 19 Sep 2008 09:33:52 -0700 (PDT)
Received: from mail.wrs.com (mail.windriver.com [147.11.1.11])
	by core3.amsl.com (Postfix) with ESMTP id 556453A68E7
	for <tcpm@ietf.org>; Fri, 19 Sep 2008 09:33:51 -0700 (PDT)
Received: from ALA-MAIL03.corp.ad.wrs.com (ala-mail03 [147.11.57.144])
	by mail.wrs.com (8.13.6/8.13.6) with ESMTP id m8JGXUgD001111;
	Fri, 19 Sep 2008 09:33:30 -0700 (PDT)
Received: from ala-mail06.corp.ad.wrs.com ([147.11.57.147]) by
	ALA-MAIL03.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 19 Sep 2008 09:33:30 -0700
Received: from dab-restive.wrs.com ([192.168.117.73]) by
	ala-mail06.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 19 Sep 2008 09:33:29 -0700
Message-Id: <0D2F6D02-8018-4684-B156-9ACC49D5B4E4@windriver.com>
From: David Borman <david.borman@windriver.com>
To: Joe Touch <touch@isi.edu>
In-Reply-To: <48D3C90A.5050301@isi.edu>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 19 Sep 2008 11:33:27 -0500
References: <FE34F27F-8DDF-4C94-BC6E-E2ABF6000309@windriver.com>	<B5A5E01F9387F4409E67604C0257C71E409513@NDJSEVS25A.ndc.nasa.gov>	<24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>	<20080906013831.GD2074@zod.isi.edu>
	<8B8A001A-CA85-407B-9F1A-0FB1D847C21C@windriver.com>
	<48D3C90A.5050301@isi.edu>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 19 Sep 2008 16:33:29.0861 (UTC)
	FILETIME=[72F03350:01C91A75]
Cc: tcpm@ietf.org, rrs@cisco.com, mdalal@cisco.com,
	"Anantha Ramaiah \(ananth\)" <ananth@cisco.com>, Ted Faber <faber@isi.edu>
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

(WG chair hat off)

The SHOULD/MAY in the applicability statement is about who benefits  
most from tcpsecure, and in the rest of the document the MUST/SHOULD/ 
MAY are about implementing tcpsecure.  We (the WG) wanted the  
distinction in the applicability statement about which situations will  
benefit the most from tcpsecure.

So for this issue, I think the document is fine as is.

			-David Borman

On Sep 19, 2008, at 10:45 AM, Joe Touch wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> One issue I'd like to re-confirm: we have, in this document, a
> hierarchical use of the RFC2119 terms of MUST/SHOULD/MAY, i.e.:
>
> whole doc: SHOULD
> 	certain portions are listed as MUST
>
> i.e., "if SHOULD, then MUST..."
>
> This is, based on recent discussions I've had with others while
> explaining this off-list, an uncommon use of 2119 language AFAICT.
>
> It would be useful to get IESG guidance on this; if such use is  
> common,
> then the doc can be left in its current form. If its use is uncommon  
> but
> desired, then we need to explain the issue in some detail (i.e., a  
> whole
> paragraph called out as a section, IMO). If its use is not desired by
> the IESG, then we need to adjust the recommendations accordingly  
> (i.e.,
> all MUSTs would drop to SHOULDs).
>
> Joe
>
> David Borman wrote:
>> Hi,
>>
>> I haven't seen any response from the authors on Ted's message.  We  
>> are
>> well past the WGLC, but I would like the authors to address the  
>> issues
>> that Ted brings up, and submit a new version of the draft before we
>> pass this up to the IESG.  I haven't seen any other comments on this
>> draft, so we are assuming that everyone else is happy with this
>> version, after Ted's comments are addressed.
>>
>> Once there is a new version available addressing Ted's comments,  
>> we'll
>> pass this on to the IESG for publication as an RFC.  So, if anyone  
>> has
>> further comments and neglected to speak up, now is the time to do so!
>>
>> 			-David Borman & Wes Eddy
>> 			TCPM WG co-chairs
>>
>> On Sep 5, 2008, at 8:38 PM, Ted Faber wrote:
>>
>>> On Thu, Aug 21, 2008 at 12:40:43PM -0500, David Borman wrote:
>>>> Wes and I would like to start the WG Last Call for:
>>>>
>>>> Title           : Improving TCP's Robustness to Blind In-Window
>>>> Attacks'
>>>> Author(s)       : A. Ramaiah, R. Stewart & M. Dalal
>>>> Filename        : draft-ietf-tcpm-tcpsecure-10.txt
>>>> Pages           : 27
>>>> Date            : July 9, 2008
>>>> Intended Status : Proposed Standard
>>>>
>>>> http://www.ietf.org/internet-drafts/draft-ietf-tcpm- 
>>>> tcpsecure-10.txt
>>>>
>>>> It is our understanding that all the feedback has been incorporated
>>>> into this latest version and that there are no known outstanding
>>>> issues with this document.
>>>>
>>>> Please send feedback to the list, even if it is just a "yes, go  
>>>> ahead
>>>> and publish".
>>>>
>>>> The WGLC will end on Friday, September 5, 2009.
>>> Overall I think this is a good draft and should advance.  I have
>>> comments, which I'll present in page order:
>>>
>>> Probably the most technical comment I have is the objection to the
>>> "There was no sound technical reasoning for choosing the Data
>>> mitigation
>>> as MAY", which is on P15.
>>>
>>> P2:
>>> The 4-tuple is called a socket pair in 793.  Even if you don't  
>>> want to
>>> adopt that terminology, it's probably worth mentioning.  I also  
>>> don't
>>> like "RST, SYN or DATA segment."  These are TCP segments with the
>>> RST or
>>> SYN flag set and I'd describe them that way.  ONce you've had a  
>>> chance
>>> to define "RST segment" as a segment with the RST bit set, you can  
>>> use
>>> the short form.
>>>
>>> I'd delete "either" from "This can cause the connection to either
>>> abort
>>> or possibly cause data corruption."  I'd consider deleting
>>> "possibly" as
>>> well.
>>>
>>> P4:
>>>
>>> "The TCP spoofing attacks, which are seen in the Internet today," -
>>> I'd
>>> say "The off-path TCP spoofing attacks".  We're still describing the
>>> problem, so let's be clear.  The next paragraph starts with a
>>> description of the attacks this draft cares about, but until then be
>>> precise.
>>>
>>> "... making the odds of guessing correctly the 4-tuple..."  I think
>>> "correctly guessing" is more common.  I'd actually suggest "...  
>>> making
>>> it much easier to guess the 4-tuple."
>>>
>>> P5:
>>>
>>> "One of the important things to note is that, for the attack to
>>> succeed
>>> the RST..." -> delete the comma.
>>>
>>> "A slight enhancement to the TCP's segment processing" -> delete the
>>> "the".
>>>
>>> P6:
>>>
>>> "Every application has control of a number of factors that effect
>>> drastically the probability of a successful spoofing attack."  You
>>> mean
>>> "affect" not "effect".  I'd also use "drastically affect" rather  
>>> than
>>> "affect drastically".  The order of the adverb is a matter of style,
>>> using "affect" changes the meaning of the sentence to the one you
>>> intend.
>>>
>>> On the figures in the "To successfully inject a spoofed packet..."
>>> paragraph:
>>>
>>> 1. Use parens, not [].
>>> 2. Finish the math.  If you want to say 1/2 * 2^32 = 2^31 rather  
>>> than
>>> just dropping 2^31 that's fine, but we're going to be comparing  
>>> these
>>> requirements, so don't hide the results.  "[SITW] shows that the  
>>> mean
>>> number of tries needed to inject a RST command is (2^31/window)  
>>> rather
>>> than the 2^31 assumed before."
>>>
>>>
>>> P7:
>>>
>>> "...please refer to draft [RFC4953]" -> "please refer to [RFC4953]"
>>> It's not a draft any more.
>>>
>>> P8:
>>>
>>> Why use 1) and 2) and A), B), C)?  Pick one.
>>>
>>> "The previous text, quoted from [RFC0793], woould thus become:" ->
>>> That
>>> sounds a lot like we're mandating the change rather than it being a
>>> SHOULD.  Do we really need this restatement at all?
>>>
>>> P13:
>>>
>>> "...so the chances of successfully injecting data into a connection
>>> are
>>> 1 in (2^32/RCV.WND *2)."  In describing the RST attacks, we spoke in
>>> terms of mean number of tries, and I'd be consistent here.   
>>> Similarly
>>> I'd do the math all the way: " ... so the mean number of tries
>>> needed to
>>> inject data successfully is  2*2^32/RWND = 2^33/RCV.WND."
>>>
>>> This section used a) and b) instead of either A) and B) or 1) and 2)
>>> (used earlier for the same purpose). Again, pick one.
>>>
>>> P15:
>>>
>>> "There was no strong technical reasoning for choosing the Data
>>> mitigation
>>> as MAY."
>>> First, everywhere else the you use "DATA", I'd use it here.
>>>
>>> Second, if I failed to make the case before, let me make it now.   
>>> The
>>> DATA injection is 4 times less likely than either the RST or the SYN
>>> attacks (2^33 vs 2^31) and may be visible to the application as
>>> garbled
>>> data.  If the attack is visible an application can gracefully
>>> terminate the connection and re-establish the conversation - unlike
>>> the
>>> RST/SYN cases.  As the attack is harder to carry out, and a  
>>> successful
>>> attack may be easier to recover from, I recommend a MAY.  I don't  
>>> care
>>> if you repeat that argument, but I do believe that there are sound
>>> technical reasons for the MAY, and I'd like to see the sentence that
>>> started this comment elided.
>>>
>>> P16:
>>>
>>> "Currently there is no known bad behavior that can be attributed to
>>> the
>>> lack of ACK throttling, but as a general principle, if ever invoked,
>>> something incorrect is occurring and such a mechanism will act as a
>>> failsafe that protects both the sender and the network." -> "While  
>>> we
>>> have not encountered a case where the lack of ACK throttling can be
>>> exploited, as a fail-safe mechanism we recommend its use.  An
>>> implementation may take an excessive number of invocations of the
>>> throttling mechanism as an indication that network conditions are
>>> unusual or hostile."
>>>
>>> P18:
>>>
>>> "...the middle box design does not comply to [RFC0793]."   No
>>> middlebox
>>> complies with RFC793; I suggest "...the middle box is generating
>>> packets
>>> a conformant TCP endpoint would not generate."
>>>
>>> P22:
>>>
>>> "ACK throttling was introduced to this document bt combining the
>>> suggestions from the tcpm working group."  That seems out of place  
>>> in
>>> "Contributors".  That section is to acknowledge the efforts of
>>> individuals.
>>>
>>> P24:
>>>
>>> Why are RFC's 4302 and 4303 normative?  And if they are why isn't
>>> RFC2385?  They're all referred to as possible mitigations.  My
>>> preference is making 4302 and 4303 non-normative, but it's very  
>>> likely
>>> that I'm missing a rule here.
>>>
>>> Quotation marks are misplaced on the Medina05 reference.
>>>
>>> The NISCC reference lacks a date.
>>>
>>> P25:
>>>
>>> Quotation marks are misplaced on the SITW reference.
>>>
>>> -- 
>>> Ted Faber
>>> http://www.isi.edu/~faber           PGP: http://www.isi.edu/~faber/pubkeys.asc
>>> Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#SIG
>>
>> _______________________________________________
>> tcpm mailing list
>> tcpm@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcpm
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFI08kKE5f5cImnZrsRAuMoAJ43+3GJLSi5p7zEOkvLZtuzYfeV0gCg5x7N
> yqGeykNAk2sBFupRaFqmo3s=
> =VG60
> -----END PGP SIGNATURE-----

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Fri Sep 19 10:04:21 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BD5FF3A6A4C;
	Fri, 19 Sep 2008 10:04:21 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2B4633A6A4C
	for <tcpm@core3.amsl.com>; Fri, 19 Sep 2008 10:04:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.099
X-Spam-Level: 
X-Spam-Status: No, score=-7.099 tagged_above=-999 required=5
	tests=[AWL=-0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id A6gZJNcXsu4f for <tcpm@core3.amsl.com>;
	Fri, 19 Sep 2008 10:04:15 -0700 (PDT)
Received: from ndjsnpf03.ndc.nasa.gov (ndjsnpf03.ndc.nasa.gov [198.117.1.123])
	by core3.amsl.com (Postfix) with ESMTP id E40763A6B01
	for <tcpm@ietf.org>; Fri, 19 Sep 2008 10:04:12 -0700 (PDT)
Received: from ndjsppt02.ndc.nasa.gov (ndjsppt02.ndc.nasa.gov [198.117.1.101])
	by ndjsnpf03.ndc.nasa.gov (Postfix) with ESMTP id B4D1B2D818D;
	Fri, 19 Sep 2008 12:04:23 -0500 (CDT)
Received: from ndjsxgw03.ndc.nasa.gov (ndjsxgw03.ndc.nasa.gov [129.166.32.111])
	by ndjsppt02.ndc.nasa.gov (8.14.1/8.14.1) with ESMTP id m8JH4SWZ015464; 
	Fri, 19 Sep 2008 12:04:28 -0500
Received: from NDJSEVS25A.ndc.nasa.gov ([129.166.32.124]) by
	ndjsxgw03.ndc.nasa.gov with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 19 Sep 2008 12:04:27 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 19 Sep 2008 12:04:26 -0500
Message-ID: <B5A5E01F9387F4409E67604C0257C71E503124@NDJSEVS25A.ndc.nasa.gov>
In-Reply-To: <0D2F6D02-8018-4684-B156-9ACC49D5B4E4@windriver.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
Thread-Index: AckadaWGB4AuzLKJT66VOgiwEN0qVwAAzWRA
References: <FE34F27F-8DDF-4C94-BC6E-E2ABF6000309@windriver.com>	<B5A5E01F9387F4409E67604C0257C71E409513@NDJSEVS25A.ndc.nasa.gov>	<24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>	<20080906013831.GD2074@zod.isi.edu><8B8A001A-CA85-407B-9F1A-0FB1D847C21C@windriver.com><48D3C90A.5050301@isi.edu>
	<0D2F6D02-8018-4684-B156-9ACC49D5B4E4@windriver.com>
From: "Eddy, Wesley M. (GRC-RCN0)[VZ]" <Wesley.M.Eddy@nasa.gov>
To: "David Borman" <david.borman@windriver.com>, "Joe Touch" <touch@isi.edu>
X-OriginalArrivalTime: 19 Sep 2008 17:04:27.0723 (UTC)
	FILETIME=[C64F71B0:01C91A79]
Cc: Ted Faber <faber@isi.edu>, rrs@cisco.com, tcpm@ietf.org,
	"Anantha Ramaiah \(ananth\)" <ananth@cisco.com>, mdalal@cisco.com
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

>-----Original Message-----
>From: tcpm-bounces@ietf.org [mailto:tcpm-bounces@ietf.org] On 
>Behalf Of David Borman
>Sent: Friday, September 19, 2008 12:33 PM
>
>(WG chair hat off)
>
>The SHOULD/MAY in the applicability statement is about who benefits  
>most from tcpsecure, and in the rest of the document the MUST/SHOULD/ 
>MAY are about implementing tcpsecure.  We (the WG) wanted the  
>distinction in the applicability statement about which 
>situations will  
>benefit the most from tcpsecure.
>
>So for this issue, I think the document is fine as is.


I'm personally in agreement.  I don't find it confusing at all, since
it's clear that if you choose not to take the upper SHOULD path, then
the set of dependent MUSTs don't apply; but I also read requirements
documents frequently, so YMMV :).

I don't, personally, think this issue is worth fretting over.
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Fri Sep 19 10:13:48 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4C2BF28B797;
	Fri, 19 Sep 2008 10:13:48 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E4A8C3A6B69
	for <tcpm@core3.amsl.com>; Fri, 19 Sep 2008 10:13:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id hhaxFGBLolcs for <tcpm@core3.amsl.com>;
	Fri, 19 Sep 2008 10:13:46 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id 6C3923A6B5F
	for <tcpm@ietf.org>; Fri, 19 Sep 2008 10:13:46 -0700 (PDT)
Received: from [128.9.168.63] (bet.isi.edu [128.9.168.63])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m8JHCctC010981
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Fri, 19 Sep 2008 10:12:40 -0700 (PDT)
Message-ID: <48D3DE00.4060307@isi.edu>
Date: Fri, 19 Sep 2008 10:14:40 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: David Borman <david.borman@windriver.com>
References: <FE34F27F-8DDF-4C94-BC6E-E2ABF6000309@windriver.com>	<B5A5E01F9387F4409E67604C0257C71E409513@NDJSEVS25A.ndc.nasa.gov>	<24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>	<20080906013831.GD2074@zod.isi.edu>
	<8B8A001A-CA85-407B-9F1A-0FB1D847C21C@windriver.com>
	<48D3C90A.5050301@isi.edu>
	<0D2F6D02-8018-4684-B156-9ACC49D5B4E4@windriver.com>
In-Reply-To: <0D2F6D02-8018-4684-B156-9ACC49D5B4E4@windriver.com>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tcpm@ietf.org, rrs@cisco.com, mdalal@cisco.com,
	"Anantha Ramaiah \(ananth\)" <ananth@cisco.com>, Ted Faber <faber@ISI.EDU>
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



David Borman wrote:
> (WG chair hat off)
> 
> The SHOULD/MAY in the applicability statement is about who benefits most
> from tcpsecure, and in the rest of the document the MUST/SHOULD/MAY are
> about implementing tcpsecure.  We (the WG) wanted the distinction in the
> applicability statement about which situations will benefit the most
> from tcpsecure.

Yes, we agreed on that, but that distinction is, AFAICT, unusual in the
IETF. I.e., most people I talked to expected the component
recommendations to reflect the overall context; they were extremely
surprised at our view that a hierarchy of recommendations was how
standards were written.

I'd like to suggest we get advice on this matter from outside the WG,
since this isn't an internal issue.

Joe

> 
> So for this issue, I think the document is fine as is.
> 
>             -David Borman
> 
> On Sep 19, 2008, at 10:45 AM, Joe Touch wrote:
> 
> One issue I'd like to re-confirm: we have, in this document, a
> hierarchical use of the RFC2119 terms of MUST/SHOULD/MAY, i.e.:
> 
> whole doc: SHOULD
>     certain portions are listed as MUST
> 
> i.e., "if SHOULD, then MUST..."
> 
> This is, based on recent discussions I've had with others while
> explaining this off-list, an uncommon use of 2119 language AFAICT.
> 
> It would be useful to get IESG guidance on this; if such use is common,
> then the doc can be left in its current form. If its use is uncommon but
> desired, then we need to explain the issue in some detail (i.e., a whole
> paragraph called out as a section, IMO). If its use is not desired by
> the IESG, then we need to adjust the recommendations accordingly (i.e.,
> all MUSTs would drop to SHOULDs).
> 
> Joe
> 
> David Borman wrote:
>>>> Hi,
>>>>
>>>> I haven't seen any response from the authors on Ted's message.  We are
>>>> well past the WGLC, but I would like the authors to address the issues
>>>> that Ted brings up, and submit a new version of the draft before we
>>>> pass this up to the IESG.  I haven't seen any other comments on this
>>>> draft, so we are assuming that everyone else is happy with this
>>>> version, after Ted's comments are addressed.
>>>>
>>>> Once there is a new version available addressing Ted's comments, we'll
>>>> pass this on to the IESG for publication as an RFC.  So, if anyone has
>>>> further comments and neglected to speak up, now is the time to do so!
>>>>
>>>>             -David Borman & Wes Eddy
>>>>             TCPM WG co-chairs
>>>>
>>>> On Sep 5, 2008, at 8:38 PM, Ted Faber wrote:
>>>>
>>>>> On Thu, Aug 21, 2008 at 12:40:43PM -0500, David Borman wrote:
>>>>>> Wes and I would like to start the WG Last Call for:
>>>>>>
>>>>>> Title           : Improving TCP's Robustness to Blind In-Window
>>>>>> Attacks'
>>>>>> Author(s)       : A. Ramaiah, R. Stewart & M. Dalal
>>>>>> Filename        : draft-ietf-tcpm-tcpsecure-10.txt
>>>>>> Pages           : 27
>>>>>> Date            : July 9, 2008
>>>>>> Intended Status : Proposed Standard
>>>>>>
>>>>>> http://www.ietf.org/internet-drafts/draft-ietf-tcpm-tcpsecure-10.txt
>>>>>>
>>>>>> It is our understanding that all the feedback has been incorporated
>>>>>> into this latest version and that there are no known outstanding
>>>>>> issues with this document.
>>>>>>
>>>>>> Please send feedback to the list, even if it is just a "yes, go ahead
>>>>>> and publish".
>>>>>>
>>>>>> The WGLC will end on Friday, September 5, 2009.
>>>>> Overall I think this is a good draft and should advance.  I have
>>>>> comments, which I'll present in page order:
>>>>>
>>>>> Probably the most technical comment I have is the objection to the
>>>>> "There was no sound technical reasoning for choosing the Data
>>>>> mitigation
>>>>> as MAY", which is on P15.
>>>>>
>>>>> P2:
>>>>> The 4-tuple is called a socket pair in 793.  Even if you don't want to
>>>>> adopt that terminology, it's probably worth mentioning.  I also don't
>>>>> like "RST, SYN or DATA segment."  These are TCP segments with the
>>>>> RST or
>>>>> SYN flag set and I'd describe them that way.  ONce you've had a chance
>>>>> to define "RST segment" as a segment with the RST bit set, you can use
>>>>> the short form.
>>>>>
>>>>> I'd delete "either" from "This can cause the connection to either
>>>>> abort
>>>>> or possibly cause data corruption."  I'd consider deleting
>>>>> "possibly" as
>>>>> well.
>>>>>
>>>>> P4:
>>>>>
>>>>> "The TCP spoofing attacks, which are seen in the Internet today," -
>>>>> I'd
>>>>> say "The off-path TCP spoofing attacks".  We're still describing the
>>>>> problem, so let's be clear.  The next paragraph starts with a
>>>>> description of the attacks this draft cares about, but until then be
>>>>> precise.
>>>>>
>>>>> "... making the odds of guessing correctly the 4-tuple..."  I think
>>>>> "correctly guessing" is more common.  I'd actually suggest "... making
>>>>> it much easier to guess the 4-tuple."
>>>>>
>>>>> P5:
>>>>>
>>>>> "One of the important things to note is that, for the attack to
>>>>> succeed
>>>>> the RST..." -> delete the comma.
>>>>>
>>>>> "A slight enhancement to the TCP's segment processing" -> delete the
>>>>> "the".
>>>>>
>>>>> P6:
>>>>>
>>>>> "Every application has control of a number of factors that effect
>>>>> drastically the probability of a successful spoofing attack."  You
>>>>> mean
>>>>> "affect" not "effect".  I'd also use "drastically affect" rather than
>>>>> "affect drastically".  The order of the adverb is a matter of style,
>>>>> using "affect" changes the meaning of the sentence to the one you
>>>>> intend.
>>>>>
>>>>> On the figures in the "To successfully inject a spoofed packet..."
>>>>> paragraph:
>>>>>
>>>>> 1. Use parens, not [].
>>>>> 2. Finish the math.  If you want to say 1/2 * 2^32 = 2^31 rather than
>>>>> just dropping 2^31 that's fine, but we're going to be comparing these
>>>>> requirements, so don't hide the results.  "[SITW] shows that the mean
>>>>> number of tries needed to inject a RST command is (2^31/window) rather
>>>>> than the 2^31 assumed before."
>>>>>
>>>>>
>>>>> P7:
>>>>>
>>>>> "...please refer to draft [RFC4953]" -> "please refer to [RFC4953]"
>>>>> It's not a draft any more.
>>>>>
>>>>> P8:
>>>>>
>>>>> Why use 1) and 2) and A), B), C)?  Pick one.
>>>>>
>>>>> "The previous text, quoted from [RFC0793], woould thus become:" ->
>>>>> That
>>>>> sounds a lot like we're mandating the change rather than it being a
>>>>> SHOULD.  Do we really need this restatement at all?
>>>>>
>>>>> P13:
>>>>>
>>>>> "...so the chances of successfully injecting data into a connection
>>>>> are
>>>>> 1 in (2^32/RCV.WND *2)."  In describing the RST attacks, we spoke in
>>>>> terms of mean number of tries, and I'd be consistent here.  Similarly
>>>>> I'd do the math all the way: " ... so the mean number of tries
>>>>> needed to
>>>>> inject data successfully is  2*2^32/RWND = 2^33/RCV.WND."
>>>>>
>>>>> This section used a) and b) instead of either A) and B) or 1) and 2)
>>>>> (used earlier for the same purpose). Again, pick one.
>>>>>
>>>>> P15:
>>>>>
>>>>> "There was no strong technical reasoning for choosing the Data
>>>>> mitigation
>>>>> as MAY."
>>>>> First, everywhere else the you use "DATA", I'd use it here.
>>>>>
>>>>> Second, if I failed to make the case before, let me make it now.  The
>>>>> DATA injection is 4 times less likely than either the RST or the SYN
>>>>> attacks (2^33 vs 2^31) and may be visible to the application as
>>>>> garbled
>>>>> data.  If the attack is visible an application can gracefully
>>>>> terminate the connection and re-establish the conversation - unlike
>>>>> the
>>>>> RST/SYN cases.  As the attack is harder to carry out, and a successful
>>>>> attack may be easier to recover from, I recommend a MAY.  I don't care
>>>>> if you repeat that argument, but I do believe that there are sound
>>>>> technical reasons for the MAY, and I'd like to see the sentence that
>>>>> started this comment elided.
>>>>>
>>>>> P16:
>>>>>
>>>>> "Currently there is no known bad behavior that can be attributed to
>>>>> the
>>>>> lack of ACK throttling, but as a general principle, if ever invoked,
>>>>> something incorrect is occurring and such a mechanism will act as a
>>>>> failsafe that protects both the sender and the network." -> "While we
>>>>> have not encountered a case where the lack of ACK throttling can be
>>>>> exploited, as a fail-safe mechanism we recommend its use.  An
>>>>> implementation may take an excessive number of invocations of the
>>>>> throttling mechanism as an indication that network conditions are
>>>>> unusual or hostile."
>>>>>
>>>>> P18:
>>>>>
>>>>> "...the middle box design does not comply to [RFC0793]."   No
>>>>> middlebox
>>>>> complies with RFC793; I suggest "...the middle box is generating
>>>>> packets
>>>>> a conformant TCP endpoint would not generate."
>>>>>
>>>>> P22:
>>>>>
>>>>> "ACK throttling was introduced to this document bt combining the
>>>>> suggestions from the tcpm working group."  That seems out of place in
>>>>> "Contributors".  That section is to acknowledge the efforts of
>>>>> individuals.
>>>>>
>>>>> P24:
>>>>>
>>>>> Why are RFC's 4302 and 4303 normative?  And if they are why isn't
>>>>> RFC2385?  They're all referred to as possible mitigations.  My
>>>>> preference is making 4302 and 4303 non-normative, but it's very likely
>>>>> that I'm missing a rule here.
>>>>>
>>>>> Quotation marks are misplaced on the Medina05 reference.
>>>>>
>>>>> The NISCC reference lacks a date.
>>>>>
>>>>> P25:
>>>>>
>>>>> Quotation marks are misplaced on the SITW reference.
>>>>>
>>>>> -- 
>>>>> Ted Faber
>>>>> http://www.isi.edu/~faber           PGP:
>>>>> http://www.isi.edu/~faber/pubkeys.asc
>>>>> Unexpected attachment on this mail? See
>>>>> http://www.isi.edu/~faber/FAQ.html#SIG
>>>>
>>>> _______________________________________________
>>>> tcpm mailing list
>>>> tcpm@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/tcpm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFI094AE5f5cImnZrsRAtw3AKCs7g9FCoAKb0DS9QCNRrRIEIKSjgCglgnl
wsD07E8spIc9N5fh0w/Po1w=
=lDym
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Fri Sep 19 10:33:34 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 606333A6B7D;
	Fri, 19 Sep 2008 10:33:34 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 888A63A6B7C
	for <tcpm@core3.amsl.com>; Fri, 19 Sep 2008 10:33:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id regcS07ldF0w for <tcpm@core3.amsl.com>;
	Fri, 19 Sep 2008 10:33:25 -0700 (PDT)
Received: from mail.wrs.com (mail.windriver.com [147.11.1.11])
	by core3.amsl.com (Postfix) with ESMTP id 6FB403A6B80
	for <tcpm@ietf.org>; Fri, 19 Sep 2008 10:33:25 -0700 (PDT)
Received: from ALA-MAIL03.corp.ad.wrs.com (ala-mail03 [147.11.57.144])
	by mail.wrs.com (8.13.6/8.13.6) with ESMTP id m8JHXYMB027843;
	Fri, 19 Sep 2008 10:33:34 -0700 (PDT)
Received: from ala-mail06.corp.ad.wrs.com ([147.11.57.147]) by
	ALA-MAIL03.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 19 Sep 2008 10:33:34 -0700
Received: from [172.25.34.41] ([172.25.34.41]) by ala-mail06.corp.ad.wrs.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 19 Sep 2008 10:33:33 -0700
Message-Id: <98FC2F4C-9AB5-499F-850F-B73E899851FF@windriver.com>
From: David Borman <david.borman@windriver.com>
To: Joe Touch <touch@isi.edu>
In-Reply-To: <48D3DE00.4060307@isi.edu>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 19 Sep 2008 12:33:31 -0500
References: <FE34F27F-8DDF-4C94-BC6E-E2ABF6000309@windriver.com>	<B5A5E01F9387F4409E67604C0257C71E409513@NDJSEVS25A.ndc.nasa.gov>	<24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>	<20080906013831.GD2074@zod.isi.edu>
	<8B8A001A-CA85-407B-9F1A-0FB1D847C21C@windriver.com>
	<48D3C90A.5050301@isi.edu>
	<0D2F6D02-8018-4684-B156-9ACC49D5B4E4@windriver.com>
	<48D3DE00.4060307@isi.edu>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 19 Sep 2008 17:33:34.0008 (UTC)
	FILETIME=[D72D6380:01C91A7D]
Cc: tcpm@ietf.org, rrs@cisco.com, mdalal@cisco.com,
	"Anantha Ramaiah \(ananth\)" <ananth@cisco.com>, Ted Faber <faber@isi.edu>
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

Joe,

I don't view it as a hierarchy.  The SHOULD/MAY in the applicability  
statement is about giving clarity to what situations tcpsecure is most  
applicable.  The rest is about how you implement tcpsecure.

But even if you do view it as a hierarchy, it is nothing out of the  
ordinary.  No optional standard is going to be a MUST for who needs to  
implement it, but then the rest of the standard itself will have still  
have MUSTs in it for how to do the implementation.  The only thing  
that might be unique here is that the applicability statement has an  
explicit SHOULD/MAY in it; they could be changed to should/may and I  
don't think anything would be lost, but I also think it is fine as it  
is.

			-David (still with WG chair hat off)

On Sep 19, 2008, at 12:14 PM, Joe Touch wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> David Borman wrote:
>> (WG chair hat off)
>>
>> The SHOULD/MAY in the applicability statement is about who benefits  
>> most
>> from tcpsecure, and in the rest of the document the MUST/SHOULD/MAY  
>> are
>> about implementing tcpsecure.  We (the WG) wanted the distinction  
>> in the
>> applicability statement about which situations will benefit the most
>> from tcpsecure.
>
> Yes, we agreed on that, but that distinction is, AFAICT, unusual in  
> the
> IETF. I.e., most people I talked to expected the component
> recommendations to reflect the overall context; they were extremely
> surprised at our view that a hierarchy of recommendations was how
> standards were written.
>
> I'd like to suggest we get advice on this matter from outside the WG,
> since this isn't an internal issue.
>
> Joe
>
>>
>> So for this issue, I think the document is fine as is.
>>
>>            -David Borman
>>
>> On Sep 19, 2008, at 10:45 AM, Joe Touch wrote:
>>
>> One issue I'd like to re-confirm: we have, in this document, a
>> hierarchical use of the RFC2119 terms of MUST/SHOULD/MAY, i.e.:
>>
>> whole doc: SHOULD
>>    certain portions are listed as MUST
>>
>> i.e., "if SHOULD, then MUST..."
>>
>> This is, based on recent discussions I've had with others while
>> explaining this off-list, an uncommon use of 2119 language AFAICT.
>>
>> It would be useful to get IESG guidance on this; if such use is  
>> common,
>> then the doc can be left in its current form. If its use is  
>> uncommon but
>> desired, then we need to explain the issue in some detail (i.e., a  
>> whole
>> paragraph called out as a section, IMO). If its use is not desired by
>> the IESG, then we need to adjust the recommendations accordingly  
>> (i.e.,
>> all MUSTs would drop to SHOULDs).
>>
>> Joe
>>
>> David Borman wrote:
>>>>> Hi,
>>>>>
>>>>> I haven't seen any response from the authors on Ted's message.   
>>>>> We are
>>>>> well past the WGLC, but I would like the authors to address the  
>>>>> issues
>>>>> that Ted brings up, and submit a new version of the draft before  
>>>>> we
>>>>> pass this up to the IESG.  I haven't seen any other comments on  
>>>>> this
>>>>> draft, so we are assuming that everyone else is happy with this
>>>>> version, after Ted's comments are addressed.
>>>>>
>>>>> Once there is a new version available addressing Ted's comments,  
>>>>> we'll
>>>>> pass this on to the IESG for publication as an RFC.  So, if  
>>>>> anyone has
>>>>> further comments and neglected to speak up, now is the time to  
>>>>> do so!
>>>>>
>>>>>            -David Borman & Wes Eddy
>>>>>            TCPM WG co-chairs
>>>>>
>>>>> On Sep 5, 2008, at 8:38 PM, Ted Faber wrote:
>>>>>
>>>>>> On Thu, Aug 21, 2008 at 12:40:43PM -0500, David Borman wrote:
>>>>>>> Wes and I would like to start the WG Last Call for:
>>>>>>>
>>>>>>> Title           : Improving TCP's Robustness to Blind In-Window
>>>>>>> Attacks'
>>>>>>> Author(s)       : A. Ramaiah, R. Stewart & M. Dalal
>>>>>>> Filename        : draft-ietf-tcpm-tcpsecure-10.txt
>>>>>>> Pages           : 27
>>>>>>> Date            : July 9, 2008
>>>>>>> Intended Status : Proposed Standard
>>>>>>>
>>>>>>> http://www.ietf.org/internet-drafts/draft-ietf-tcpm-tcpsecure-10.txt
>>>>>>>
>>>>>>> It is our understanding that all the feedback has been  
>>>>>>> incorporated
>>>>>>> into this latest version and that there are no known outstanding
>>>>>>> issues with this document.
>>>>>>>
>>>>>>> Please send feedback to the list, even if it is just a "yes,  
>>>>>>> go ahead
>>>>>>> and publish".
>>>>>>>
>>>>>>> The WGLC will end on Friday, September 5, 2009.
>>>>>> Overall I think this is a good draft and should advance.  I have
>>>>>> comments, which I'll present in page order:
>>>>>>
>>>>>> Probably the most technical comment I have is the objection to  
>>>>>> the
>>>>>> "There was no sound technical reasoning for choosing the Data
>>>>>> mitigation
>>>>>> as MAY", which is on P15.
>>>>>>
>>>>>> P2:
>>>>>> The 4-tuple is called a socket pair in 793.  Even if you don't  
>>>>>> want to
>>>>>> adopt that terminology, it's probably worth mentioning.  I also  
>>>>>> don't
>>>>>> like "RST, SYN or DATA segment."  These are TCP segments with the
>>>>>> RST or
>>>>>> SYN flag set and I'd describe them that way.  ONce you've had a  
>>>>>> chance
>>>>>> to define "RST segment" as a segment with the RST bit set, you  
>>>>>> can use
>>>>>> the short form.
>>>>>>
>>>>>> I'd delete "either" from "This can cause the connection to either
>>>>>> abort
>>>>>> or possibly cause data corruption."  I'd consider deleting
>>>>>> "possibly" as
>>>>>> well.
>>>>>>
>>>>>> P4:
>>>>>>
>>>>>> "The TCP spoofing attacks, which are seen in the Internet  
>>>>>> today," -
>>>>>> I'd
>>>>>> say "The off-path TCP spoofing attacks".  We're still  
>>>>>> describing the
>>>>>> problem, so let's be clear.  The next paragraph starts with a
>>>>>> description of the attacks this draft cares about, but until  
>>>>>> then be
>>>>>> precise.
>>>>>>
>>>>>> "... making the odds of guessing correctly the 4-tuple..."  I  
>>>>>> think
>>>>>> "correctly guessing" is more common.  I'd actually suggest "...  
>>>>>> making
>>>>>> it much easier to guess the 4-tuple."
>>>>>>
>>>>>> P5:
>>>>>>
>>>>>> "One of the important things to note is that, for the attack to
>>>>>> succeed
>>>>>> the RST..." -> delete the comma.
>>>>>>
>>>>>> "A slight enhancement to the TCP's segment processing" ->  
>>>>>> delete the
>>>>>> "the".
>>>>>>
>>>>>> P6:
>>>>>>
>>>>>> "Every application has control of a number of factors that effect
>>>>>> drastically the probability of a successful spoofing attack."   
>>>>>> You
>>>>>> mean
>>>>>> "affect" not "effect".  I'd also use "drastically affect"  
>>>>>> rather than
>>>>>> "affect drastically".  The order of the adverb is a matter of  
>>>>>> style,
>>>>>> using "affect" changes the meaning of the sentence to the one you
>>>>>> intend.
>>>>>>
>>>>>> On the figures in the "To successfully inject a spoofed  
>>>>>> packet..."
>>>>>> paragraph:
>>>>>>
>>>>>> 1. Use parens, not [].
>>>>>> 2. Finish the math.  If you want to say 1/2 * 2^32 = 2^31  
>>>>>> rather than
>>>>>> just dropping 2^31 that's fine, but we're going to be comparing  
>>>>>> these
>>>>>> requirements, so don't hide the results.  "[SITW] shows that  
>>>>>> the mean
>>>>>> number of tries needed to inject a RST command is (2^31/window)  
>>>>>> rather
>>>>>> than the 2^31 assumed before."
>>>>>>
>>>>>>
>>>>>> P7:
>>>>>>
>>>>>> "...please refer to draft [RFC4953]" -> "please refer to  
>>>>>> [RFC4953]"
>>>>>> It's not a draft any more.
>>>>>>
>>>>>> P8:
>>>>>>
>>>>>> Why use 1) and 2) and A), B), C)?  Pick one.
>>>>>>
>>>>>> "The previous text, quoted from [RFC0793], woould thus become:"  
>>>>>> ->
>>>>>> That
>>>>>> sounds a lot like we're mandating the change rather than it  
>>>>>> being a
>>>>>> SHOULD.  Do we really need this restatement at all?
>>>>>>
>>>>>> P13:
>>>>>>
>>>>>> "...so the chances of successfully injecting data into a  
>>>>>> connection
>>>>>> are
>>>>>> 1 in (2^32/RCV.WND *2)."  In describing the RST attacks, we  
>>>>>> spoke in
>>>>>> terms of mean number of tries, and I'd be consistent here.   
>>>>>> Similarly
>>>>>> I'd do the math all the way: " ... so the mean number of tries
>>>>>> needed to
>>>>>> inject data successfully is  2*2^32/RWND = 2^33/RCV.WND."
>>>>>>
>>>>>> This section used a) and b) instead of either A) and B) or 1)  
>>>>>> and 2)
>>>>>> (used earlier for the same purpose). Again, pick one.
>>>>>>
>>>>>> P15:
>>>>>>
>>>>>> "There was no strong technical reasoning for choosing the Data
>>>>>> mitigation
>>>>>> as MAY."
>>>>>> First, everywhere else the you use "DATA", I'd use it here.
>>>>>>
>>>>>> Second, if I failed to make the case before, let me make it  
>>>>>> now.  The
>>>>>> DATA injection is 4 times less likely than either the RST or  
>>>>>> the SYN
>>>>>> attacks (2^33 vs 2^31) and may be visible to the application as
>>>>>> garbled
>>>>>> data.  If the attack is visible an application can gracefully
>>>>>> terminate the connection and re-establish the conversation -  
>>>>>> unlike
>>>>>> the
>>>>>> RST/SYN cases.  As the attack is harder to carry out, and a  
>>>>>> successful
>>>>>> attack may be easier to recover from, I recommend a MAY.  I  
>>>>>> don't care
>>>>>> if you repeat that argument, but I do believe that there are  
>>>>>> sound
>>>>>> technical reasons for the MAY, and I'd like to see the sentence  
>>>>>> that
>>>>>> started this comment elided.
>>>>>>
>>>>>> P16:
>>>>>>
>>>>>> "Currently there is no known bad behavior that can be  
>>>>>> attributed to
>>>>>> the
>>>>>> lack of ACK throttling, but as a general principle, if ever  
>>>>>> invoked,
>>>>>> something incorrect is occurring and such a mechanism will act  
>>>>>> as a
>>>>>> failsafe that protects both the sender and the network." ->  
>>>>>> "While we
>>>>>> have not encountered a case where the lack of ACK throttling  
>>>>>> can be
>>>>>> exploited, as a fail-safe mechanism we recommend its use.  An
>>>>>> implementation may take an excessive number of invocations of the
>>>>>> throttling mechanism as an indication that network conditions are
>>>>>> unusual or hostile."
>>>>>>
>>>>>> P18:
>>>>>>
>>>>>> "...the middle box design does not comply to [RFC0793]."   No
>>>>>> middlebox
>>>>>> complies with RFC793; I suggest "...the middle box is generating
>>>>>> packets
>>>>>> a conformant TCP endpoint would not generate."
>>>>>>
>>>>>> P22:
>>>>>>
>>>>>> "ACK throttling was introduced to this document bt combining the
>>>>>> suggestions from the tcpm working group."  That seems out of  
>>>>>> place in
>>>>>> "Contributors".  That section is to acknowledge the efforts of
>>>>>> individuals.
>>>>>>
>>>>>> P24:
>>>>>>
>>>>>> Why are RFC's 4302 and 4303 normative?  And if they are why isn't
>>>>>> RFC2385?  They're all referred to as possible mitigations.  My
>>>>>> preference is making 4302 and 4303 non-normative, but it's very  
>>>>>> likely
>>>>>> that I'm missing a rule here.
>>>>>>
>>>>>> Quotation marks are misplaced on the Medina05 reference.
>>>>>>
>>>>>> The NISCC reference lacks a date.
>>>>>>
>>>>>> P25:
>>>>>>
>>>>>> Quotation marks are misplaced on the SITW reference.
>>>>>>
>>>>>> -- 
>>>>>> Ted Faber
>>>>>> http://www.isi.edu/~faber           PGP:
>>>>>> http://www.isi.edu/~faber/pubkeys.asc
>>>>>> Unexpected attachment on this mail? See
>>>>>> http://www.isi.edu/~faber/FAQ.html#SIG
>>>>>
>>>>> _______________________________________________
>>>>> tcpm mailing list
>>>>> tcpm@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/tcpm
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFI094AE5f5cImnZrsRAtw3AKCs7g9FCoAKb0DS9QCNRrRIEIKSjgCglgnl
> wsD07E8spIc9N5fh0w/Po1w=
> =lDym
> -----END PGP SIGNATURE-----

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Fri Sep 19 12:02:57 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E11E93A6972;
	Fri, 19 Sep 2008 12:02:57 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 75C733A6972
	for <tcpm@core3.amsl.com>; Fri, 19 Sep 2008 12:02:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id xOincgz1hIpg for <tcpm@core3.amsl.com>;
	Fri, 19 Sep 2008 12:02:54 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id D5BE73A6858
	for <tcpm@ietf.org>; Fri, 19 Sep 2008 12:02:54 -0700 (PDT)
Received: from [128.9.168.63] (bet.isi.edu [128.9.168.63])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m8JJ2iNu015166
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Fri, 19 Sep 2008 12:02:46 -0700 (PDT)
Message-ID: <48D3F7CD.8060006@isi.edu>
Date: Fri, 19 Sep 2008 12:04:45 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: David Borman <david.borman@windriver.com>
References: <FE34F27F-8DDF-4C94-BC6E-E2ABF6000309@windriver.com>	<B5A5E01F9387F4409E67604C0257C71E409513@NDJSEVS25A.ndc.nasa.gov>	<24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>	<20080906013831.GD2074@zod.isi.edu>
	<8B8A001A-CA85-407B-9F1A-0FB1D847C21C@windriver.com>
	<48D3C90A.5050301@isi.edu>
	<0D2F6D02-8018-4684-B156-9ACC49D5B4E4@windriver.com>
	<48D3DE00.4060307@isi.edu>
	<98FC2F4C-9AB5-499F-850F-B73E899851FF@windriver.com>
In-Reply-To: <98FC2F4C-9AB5-499F-850F-B73E899851FF@windriver.com>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tcpm@ietf.org, rrs@cisco.com, mdalal@cisco.com,
	"Anantha Ramaiah \(ananth\)" <ananth@cisco.com>, Ted Faber <faber@ISI.EDU>
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



David Borman wrote:
> Joe,
> 
> I don't view it as a hierarchy.  The SHOULD/MAY in the applicability
> statement is about giving clarity to what situations tcpsecure is most
> applicable.  The rest is about how you implement tcpsecure.

I agree that we all understand our intent, and I agree with the intent.

> But even if you do view it as a hierarchy, it is nothing out of the
> ordinary.  No optional standard is going to be a MUST for who needs to
> implement it, but then the rest of the standard itself will have still
> have MUSTs in it for how to do the implementation.  

This is the part that others have commented to me on, and the primary
point of my note. If we can point to an optional standard that has MUSTs
therein, fine. If not, we're blazing new ground.

> The only thing that
> might be unique here is that the applicability statement has an explicit
> SHOULD/MAY in it; they could be changed to should/may and I don't think
> anything would be lost, but I also think it is fine as it is.

It would definitely be lost; the doc would then have only MUSTs for
certain items, which are not MUSTs if the overall document is a SHOULD.

This is the punchline; i.e., if we feel that we can't make document-wide
recommendations at different levels than individual items, then the
document-wide concern needs to be reflected in the level of individual
items, and then I would claim that the current MUSTs should be converted
to SHOULDs. (I don't see other impacts).

Joe

> On Sep 19, 2008, at 12:14 PM, Joe Touch wrote:
> 
> 
> 
> David Borman wrote:
>>>> (WG chair hat off)
>>>>
>>>> The SHOULD/MAY in the applicability statement is about who benefits most
>>>> from tcpsecure, and in the rest of the document the MUST/SHOULD/MAY are
>>>> about implementing tcpsecure.  We (the WG) wanted the distinction in the
>>>> applicability statement about which situations will benefit the most
>>>> from tcpsecure.
> 
> Yes, we agreed on that, but that distinction is, AFAICT, unusual in the
> IETF. I.e., most people I talked to expected the component
> recommendations to reflect the overall context; they were extremely
> surprised at our view that a hierarchy of recommendations was how
> standards were written.
> 
> I'd like to suggest we get advice on this matter from outside the WG,
> since this isn't an internal issue.
> 
> Joe
> 
>>>>
>>>> So for this issue, I think the document is fine as is.
>>>>
>>>>            -David Borman
>>>>
>>>> On Sep 19, 2008, at 10:45 AM, Joe Touch wrote:
>>>>
>>>> One issue I'd like to re-confirm: we have, in this document, a
>>>> hierarchical use of the RFC2119 terms of MUST/SHOULD/MAY, i.e.:
>>>>
>>>> whole doc: SHOULD
>>>>    certain portions are listed as MUST
>>>>
>>>> i.e., "if SHOULD, then MUST..."
>>>>
>>>> This is, based on recent discussions I've had with others while
>>>> explaining this off-list, an uncommon use of 2119 language AFAICT.
>>>>
>>>> It would be useful to get IESG guidance on this; if such use is common,
>>>> then the doc can be left in its current form. If its use is uncommon but
>>>> desired, then we need to explain the issue in some detail (i.e., a whole
>>>> paragraph called out as a section, IMO). If its use is not desired by
>>>> the IESG, then we need to adjust the recommendations accordingly (i.e.,
>>>> all MUSTs would drop to SHOULDs).
>>>>
>>>> Joe
>>>>
>>>> David Borman wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I haven't seen any response from the authors on Ted's message.  We
>>>>>>> are
>>>>>>> well past the WGLC, but I would like the authors to address the
>>>>>>> issues
>>>>>>> that Ted brings up, and submit a new version of the draft before we
>>>>>>> pass this up to the IESG.  I haven't seen any other comments on this
>>>>>>> draft, so we are assuming that everyone else is happy with this
>>>>>>> version, after Ted's comments are addressed.
>>>>>>>
>>>>>>> Once there is a new version available addressing Ted's comments,
>>>>>>> we'll
>>>>>>> pass this on to the IESG for publication as an RFC.  So, if anyone
>>>>>>> has
>>>>>>> further comments and neglected to speak up, now is the time to do so!
>>>>>>>
>>>>>>>            -David Borman & Wes Eddy
>>>>>>>            TCPM WG co-chairs
>>>>>>>
>>>>>>> On Sep 5, 2008, at 8:38 PM, Ted Faber wrote:
>>>>>>>
>>>>>>>> On Thu, Aug 21, 2008 at 12:40:43PM -0500, David Borman wrote:
>>>>>>>>> Wes and I would like to start the WG Last Call for:
>>>>>>>>>
>>>>>>>>> Title           : Improving TCP's Robustness to Blind In-Window
>>>>>>>>> Attacks'
>>>>>>>>> Author(s)       : A. Ramaiah, R. Stewart & M. Dalal
>>>>>>>>> Filename        : draft-ietf-tcpm-tcpsecure-10.txt
>>>>>>>>> Pages           : 27
>>>>>>>>> Date            : July 9, 2008
>>>>>>>>> Intended Status : Proposed Standard
>>>>>>>>>
>>>>>>>>> http://www.ietf.org/internet-drafts/draft-ietf-tcpm-tcpsecure-10.txt
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> It is our understanding that all the feedback has been incorporated
>>>>>>>>> into this latest version and that there are no known outstanding
>>>>>>>>> issues with this document.
>>>>>>>>>
>>>>>>>>> Please send feedback to the list, even if it is just a "yes, go
>>>>>>>>> ahead
>>>>>>>>> and publish".
>>>>>>>>>
>>>>>>>>> The WGLC will end on Friday, September 5, 2009.
>>>>>>>> Overall I think this is a good draft and should advance.  I have
>>>>>>>> comments, which I'll present in page order:
>>>>>>>>
>>>>>>>> Probably the most technical comment I have is the objection to the
>>>>>>>> "There was no sound technical reasoning for choosing the Data
>>>>>>>> mitigation
>>>>>>>> as MAY", which is on P15.
>>>>>>>>
>>>>>>>> P2:
>>>>>>>> The 4-tuple is called a socket pair in 793.  Even if you don't
>>>>>>>> want to
>>>>>>>> adopt that terminology, it's probably worth mentioning.  I also
>>>>>>>> don't
>>>>>>>> like "RST, SYN or DATA segment."  These are TCP segments with the
>>>>>>>> RST or
>>>>>>>> SYN flag set and I'd describe them that way.  ONce you've had a
>>>>>>>> chance
>>>>>>>> to define "RST segment" as a segment with the RST bit set, you
>>>>>>>> can use
>>>>>>>> the short form.
>>>>>>>>
>>>>>>>> I'd delete "either" from "This can cause the connection to either
>>>>>>>> abort
>>>>>>>> or possibly cause data corruption."  I'd consider deleting
>>>>>>>> "possibly" as
>>>>>>>> well.
>>>>>>>>
>>>>>>>> P4:
>>>>>>>>
>>>>>>>> "The TCP spoofing attacks, which are seen in the Internet today," -
>>>>>>>> I'd
>>>>>>>> say "The off-path TCP spoofing attacks".  We're still describing the
>>>>>>>> problem, so let's be clear.  The next paragraph starts with a
>>>>>>>> description of the attacks this draft cares about, but until then be
>>>>>>>> precise.
>>>>>>>>
>>>>>>>> "... making the odds of guessing correctly the 4-tuple..."  I think
>>>>>>>> "correctly guessing" is more common.  I'd actually suggest "...
>>>>>>>> making
>>>>>>>> it much easier to guess the 4-tuple."
>>>>>>>>
>>>>>>>> P5:
>>>>>>>>
>>>>>>>> "One of the important things to note is that, for the attack to
>>>>>>>> succeed
>>>>>>>> the RST..." -> delete the comma.
>>>>>>>>
>>>>>>>> "A slight enhancement to the TCP's segment processing" -> delete the
>>>>>>>> "the".
>>>>>>>>
>>>>>>>> P6:
>>>>>>>>
>>>>>>>> "Every application has control of a number of factors that effect
>>>>>>>> drastically the probability of a successful spoofing attack."  You
>>>>>>>> mean
>>>>>>>> "affect" not "effect".  I'd also use "drastically affect" rather
>>>>>>>> than
>>>>>>>> "affect drastically".  The order of the adverb is a matter of style,
>>>>>>>> using "affect" changes the meaning of the sentence to the one you
>>>>>>>> intend.
>>>>>>>>
>>>>>>>> On the figures in the "To successfully inject a spoofed packet..."
>>>>>>>> paragraph:
>>>>>>>>
>>>>>>>> 1. Use parens, not [].
>>>>>>>> 2. Finish the math.  If you want to say 1/2 * 2^32 = 2^31 rather
>>>>>>>> than
>>>>>>>> just dropping 2^31 that's fine, but we're going to be comparing
>>>>>>>> these
>>>>>>>> requirements, so don't hide the results.  "[SITW] shows that the
>>>>>>>> mean
>>>>>>>> number of tries needed to inject a RST command is (2^31/window)
>>>>>>>> rather
>>>>>>>> than the 2^31 assumed before."
>>>>>>>>
>>>>>>>>
>>>>>>>> P7:
>>>>>>>>
>>>>>>>> "...please refer to draft [RFC4953]" -> "please refer to [RFC4953]"
>>>>>>>> It's not a draft any more.
>>>>>>>>
>>>>>>>> P8:
>>>>>>>>
>>>>>>>> Why use 1) and 2) and A), B), C)?  Pick one.
>>>>>>>>
>>>>>>>> "The previous text, quoted from [RFC0793], woould thus become:" ->
>>>>>>>> That
>>>>>>>> sounds a lot like we're mandating the change rather than it being a
>>>>>>>> SHOULD.  Do we really need this restatement at all?
>>>>>>>>
>>>>>>>> P13:
>>>>>>>>
>>>>>>>> "...so the chances of successfully injecting data into a connection
>>>>>>>> are
>>>>>>>> 1 in (2^32/RCV.WND *2)."  In describing the RST attacks, we spoke in
>>>>>>>> terms of mean number of tries, and I'd be consistent here. 
>>>>>>>> Similarly
>>>>>>>> I'd do the math all the way: " ... so the mean number of tries
>>>>>>>> needed to
>>>>>>>> inject data successfully is  2*2^32/RWND = 2^33/RCV.WND."
>>>>>>>>
>>>>>>>> This section used a) and b) instead of either A) and B) or 1) and 2)
>>>>>>>> (used earlier for the same purpose). Again, pick one.
>>>>>>>>
>>>>>>>> P15:
>>>>>>>>
>>>>>>>> "There was no strong technical reasoning for choosing the Data
>>>>>>>> mitigation
>>>>>>>> as MAY."
>>>>>>>> First, everywhere else the you use "DATA", I'd use it here.
>>>>>>>>
>>>>>>>> Second, if I failed to make the case before, let me make it now. 
>>>>>>>> The
>>>>>>>> DATA injection is 4 times less likely than either the RST or the SYN
>>>>>>>> attacks (2^33 vs 2^31) and may be visible to the application as
>>>>>>>> garbled
>>>>>>>> data.  If the attack is visible an application can gracefully
>>>>>>>> terminate the connection and re-establish the conversation - unlike
>>>>>>>> the
>>>>>>>> RST/SYN cases.  As the attack is harder to carry out, and a
>>>>>>>> successful
>>>>>>>> attack may be easier to recover from, I recommend a MAY.  I don't
>>>>>>>> care
>>>>>>>> if you repeat that argument, but I do believe that there are sound
>>>>>>>> technical reasons for the MAY, and I'd like to see the sentence that
>>>>>>>> started this comment elided.
>>>>>>>>
>>>>>>>> P16:
>>>>>>>>
>>>>>>>> "Currently there is no known bad behavior that can be attributed to
>>>>>>>> the
>>>>>>>> lack of ACK throttling, but as a general principle, if ever invoked,
>>>>>>>> something incorrect is occurring and such a mechanism will act as a
>>>>>>>> failsafe that protects both the sender and the network." ->
>>>>>>>> "While we
>>>>>>>> have not encountered a case where the lack of ACK throttling can be
>>>>>>>> exploited, as a fail-safe mechanism we recommend its use.  An
>>>>>>>> implementation may take an excessive number of invocations of the
>>>>>>>> throttling mechanism as an indication that network conditions are
>>>>>>>> unusual or hostile."
>>>>>>>>
>>>>>>>> P18:
>>>>>>>>
>>>>>>>> "...the middle box design does not comply to [RFC0793]."   No
>>>>>>>> middlebox
>>>>>>>> complies with RFC793; I suggest "...the middle box is generating
>>>>>>>> packets
>>>>>>>> a conformant TCP endpoint would not generate."
>>>>>>>>
>>>>>>>> P22:
>>>>>>>>
>>>>>>>> "ACK throttling was introduced to this document bt combining the
>>>>>>>> suggestions from the tcpm working group."  That seems out of
>>>>>>>> place in
>>>>>>>> "Contributors".  That section is to acknowledge the efforts of
>>>>>>>> individuals.
>>>>>>>>
>>>>>>>> P24:
>>>>>>>>
>>>>>>>> Why are RFC's 4302 and 4303 normative?  And if they are why isn't
>>>>>>>> RFC2385?  They're all referred to as possible mitigations.  My
>>>>>>>> preference is making 4302 and 4303 non-normative, but it's very
>>>>>>>> likely
>>>>>>>> that I'm missing a rule here.
>>>>>>>>
>>>>>>>> Quotation marks are misplaced on the Medina05 reference.
>>>>>>>>
>>>>>>>> The NISCC reference lacks a date.
>>>>>>>>
>>>>>>>> P25:
>>>>>>>>
>>>>>>>> Quotation marks are misplaced on the SITW reference.
>>>>>>>>
>>>>>>>> -- 
>>>>>>>> Ted Faber
>>>>>>>> http://www.isi.edu/~faber           PGP:
>>>>>>>> http://www.isi.edu/~faber/pubkeys.asc
>>>>>>>> Unexpected attachment on this mail? See
>>>>>>>> http://www.isi.edu/~faber/FAQ.html#SIG
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> tcpm mailing list
>>>>>>> tcpm@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/tcpm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFI0/fNE5f5cImnZrsRAo5pAKC9YZZyAhatDzzhfdeiw19fG3UCMACeNKMJ
Apoc0LIuJSuH8xo9PyqcQsM=
=el20
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Fri Sep 19 13:00:54 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 852D63A68F1;
	Fri, 19 Sep 2008 13:00:54 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DCBD93A68F1
	for <tcpm@core3.amsl.com>; Fri, 19 Sep 2008 13:00:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id pTgF7CvzWMl9 for <tcpm@core3.amsl.com>;
	Fri, 19 Sep 2008 13:00:53 -0700 (PDT)
Received: from mail.wrs.com (mail.windriver.com [147.11.1.11])
	by core3.amsl.com (Postfix) with ESMTP id 20F993A685F
	for <tcpm@ietf.org>; Fri, 19 Sep 2008 13:00:52 -0700 (PDT)
Received: from ALA-MAIL03.corp.ad.wrs.com (ala-mail03 [147.11.57.144])
	by mail.wrs.com (8.13.6/8.13.6) with ESMTP id m8JK16tk026877;
	Fri, 19 Sep 2008 13:01:06 -0700 (PDT)
Received: from ala-mail06.corp.ad.wrs.com ([147.11.57.147]) by
	ALA-MAIL03.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 19 Sep 2008 13:01:05 -0700
Received: from [172.25.34.41] ([172.25.34.41]) by ala-mail06.corp.ad.wrs.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 19 Sep 2008 13:01:05 -0700
Message-Id: <984843C7-BC33-4E48-AC75-414AE86152EF@windriver.com>
From: David Borman <david.borman@windriver.com>
To: Joe Touch <touch@isi.edu>
In-Reply-To: <48D3F7CD.8060006@isi.edu>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 19 Sep 2008 15:01:03 -0500
References: <FE34F27F-8DDF-4C94-BC6E-E2ABF6000309@windriver.com>	<B5A5E01F9387F4409E67604C0257C71E409513@NDJSEVS25A.ndc.nasa.gov>	<24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>	<20080906013831.GD2074@zod.isi.edu>
	<8B8A001A-CA85-407B-9F1A-0FB1D847C21C@windriver.com>
	<48D3C90A.5050301@isi.edu>
	<0D2F6D02-8018-4684-B156-9ACC49D5B4E4@windriver.com>
	<48D3DE00.4060307@isi.edu>
	<98FC2F4C-9AB5-499F-850F-B73E899851FF@windriver.com>
	<48D3F7CD.8060006@isi.edu>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 19 Sep 2008 20:01:06.0303 (UTC)
	FILETIME=[738E68F0:01C91A92]
Cc: tcpm@ietf.org, rrs@cisco.com, mdalal@cisco.com,
	"Anantha Ramaiah \(ananth\)" <ananth@cisco.com>, Ted Faber <faber@isi.edu>
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org


On Sep 19, 2008, at 2:04 PM, Joe Touch wrote:

...
>> But even if you do view it as a hierarchy, it is nothing out of the
>> ordinary.  No optional standard is going to be a MUST for who needs  
>> to
>> implement it, but then the rest of the standard itself will have  
>> still
>> have MUSTs in it for how to do the implementation.
>
> This is the part that others have commented to me on, and the primary
> point of my note. If we can point to an optional standard that has  
> MUSTs
> therein, fine. If not, we're blazing new ground.

That's easy, just look at any optional standards track RFC.  Here are  
a few recent RFCs that I just picked at random:

RFC 5001 "DNS Name Server Identifier (NSID) Option"
RFC 5007 "DHCPv6 Leasequery"
RFC 5010 "The Dynamic Host Configuration Protocol Version 4 (DHCPv4)  
Relay Agent Flags Suboption"
RFC 5044 "Marker PDU Aligned Framing for TCP Specification"

None of these are mandatory, so at best they would be SHOULD for the  
overall document, and yet they all have MUSTs in them.  Need I go on?   
The only difference I can see is that these standards don't have  
explicit SHOULD/MAY in their applicability sections.


>> The only thing that
>> might be unique here is that the applicability statement has an  
>> explicit
>> SHOULD/MAY in it; they could be changed to should/may and I don't  
>> think
>> anything would be lost, but I also think it is fine as it is.
>
> It would definitely be lost; the doc would then have only MUSTs for
> certain items, which are not MUSTs if the overall document is a  
> SHOULD.
>
> This is the punchline; i.e., if we feel that we can't make document- 
> wide
> recommendations at different levels than individual items, then the
> document-wide concern needs to be reflected in the level of individual
> items, and then I would claim that the current MUSTs should be  
> converted
> to SHOULDs. (I don't see other impacts).

Again, the SHOULD/MAY in the applicability section is about who can  
benefit from tcpsecure, and has nothing to do with how to implement  
tcpsecure.  The other MUST/SHOULD/MAYs in tcpsecure are about how to  
implement tcpsecure.

It's "you SHOULD/MAY implement this, but if you do, you MUST do it  
this way".  That's just normal standards stuff.

			-David Borman

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Fri Sep 19 13:26:51 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 167293A687D;
	Fri, 19 Sep 2008 13:26:51 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A48F83A685A
	for <tcpm@core3.amsl.com>; Fri, 19 Sep 2008 13:26:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id U5y27qZZ4bkM for <tcpm@core3.amsl.com>;
	Fri, 19 Sep 2008 13:26:48 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id BAEFA3A67D8
	for <tcpm@ietf.org>; Fri, 19 Sep 2008 13:26:48 -0700 (PDT)
Received: from [128.9.168.63] (bet.isi.edu [128.9.168.63])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m8JKQGX8009004
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Fri, 19 Sep 2008 13:26:17 -0700 (PDT)
Message-ID: <48D40B61.7060201@isi.edu>
Date: Fri, 19 Sep 2008 13:28:17 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: David Borman <david.borman@windriver.com>
References: <FE34F27F-8DDF-4C94-BC6E-E2ABF6000309@windriver.com>	<B5A5E01F9387F4409E67604C0257C71E409513@NDJSEVS25A.ndc.nasa.gov>	<24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>	<20080906013831.GD2074@zod.isi.edu>
	<8B8A001A-CA85-407B-9F1A-0FB1D847C21C@windriver.com>
	<48D3C90A.5050301@isi.edu>
	<0D2F6D02-8018-4684-B156-9ACC49D5B4E4@windriver.com>
	<48D3DE00.4060307@isi.edu>
	<98FC2F4C-9AB5-499F-850F-B73E899851FF@windriver.com>
	<48D3F7CD.8060006@isi.edu>
	<984843C7-BC33-4E48-AC75-414AE86152EF@windriver.com>
In-Reply-To: <984843C7-BC33-4E48-AC75-414AE86152EF@windriver.com>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tcpm@ietf.org, rrs@cisco.com, mdalal@cisco.com,
	"Anantha Ramaiah \(ananth\)" <ananth@cisco.com>, Ted Faber <faber@ISI.EDU>
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi, David,

If we have docs we can point to, we're fine. I had questions from others
on this point; if we have precedent, we're set.

Joe

David Borman wrote:
> 
> On Sep 19, 2008, at 2:04 PM, Joe Touch wrote:
> 
> ...
>>> But even if you do view it as a hierarchy, it is nothing out of the
>>> ordinary.  No optional standard is going to be a MUST for who needs to
>>> implement it, but then the rest of the standard itself will have still
>>> have MUSTs in it for how to do the implementation.
>>
>> This is the part that others have commented to me on, and the primary
>> point of my note. If we can point to an optional standard that has MUSTs
>> therein, fine. If not, we're blazing new ground.
> 
> That's easy, just look at any optional standards track RFC.  Here are a
> few recent RFCs that I just picked at random:
> 
> RFC 5001 "DNS Name Server Identifier (NSID) Option"
> RFC 5007 "DHCPv6 Leasequery"
> RFC 5010 "The Dynamic Host Configuration Protocol Version 4 (DHCPv4)
> Relay Agent Flags Suboption"
> RFC 5044 "Marker PDU Aligned Framing for TCP Specification"
> 
> None of these are mandatory, so at best they would be SHOULD for the
> overall document, and yet they all have MUSTs in them.  Need I go on? 
> The only difference I can see is that these standards don't have
> explicit SHOULD/MAY in their applicability sections.
> 
> 
>>> The only thing that
>>> might be unique here is that the applicability statement has an explicit
>>> SHOULD/MAY in it; they could be changed to should/may and I don't think
>>> anything would be lost, but I also think it is fine as it is.
>>
>> It would definitely be lost; the doc would then have only MUSTs for
>> certain items, which are not MUSTs if the overall document is a SHOULD.
>>
>> This is the punchline; i.e., if we feel that we can't make document-wide
>> recommendations at different levels than individual items, then the
>> document-wide concern needs to be reflected in the level of individual
>> items, and then I would claim that the current MUSTs should be converted
>> to SHOULDs. (I don't see other impacts).
> 
> Again, the SHOULD/MAY in the applicability section is about who can
> benefit from tcpsecure, and has nothing to do with how to implement
> tcpsecure.  The other MUST/SHOULD/MAYs in tcpsecure are about how to
> implement tcpsecure.
> 
> It's "you SHOULD/MAY implement this, but if you do, you MUST do it this
> way".  That's just normal standards stuff.
> 
>             -David Borman
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFI1AthE5f5cImnZrsRAmTuAJ9reCQq4gM4b9Yzbidr61YRrFvbQwCfSkr9
uf1SV+aHEvZkmsUr9TUIf8A=
=iUCX
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Fri Sep 19 13:34:29 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D16433A69F3;
	Fri, 19 Sep 2008 13:34:29 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5B7683A69F3
	for <tcpm@core3.amsl.com>; Fri, 19 Sep 2008 13:34:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6KbLN1j2uOEy for <tcpm@core3.amsl.com>;
	Fri, 19 Sep 2008 13:34:27 -0700 (PDT)
Received: from mail.wrs.com (mail.windriver.com [147.11.1.11])
	by core3.amsl.com (Postfix) with ESMTP id 705F63A688B
	for <tcpm@ietf.org>; Fri, 19 Sep 2008 13:34:27 -0700 (PDT)
Received: from ALA-MAIL03.corp.ad.wrs.com (ala-mail03 [147.11.57.144])
	by mail.wrs.com (8.13.6/8.13.6) with ESMTP id m8JKYWld010079;
	Fri, 19 Sep 2008 13:34:34 -0700 (PDT)
Received: from ala-mail06.corp.ad.wrs.com ([147.11.57.147]) by
	ALA-MAIL03.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 19 Sep 2008 13:34:34 -0700
Received: from [172.25.34.41] ([172.25.34.41]) by ala-mail06.corp.ad.wrs.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 19 Sep 2008 13:34:33 -0700
Message-Id: <D403C6B4-9570-46C9-907D-B83734B39F61@windriver.com>
From: David Borman <david.borman@windriver.com>
To: Joe Touch <touch@isi.edu>
In-Reply-To: <48D40B61.7060201@isi.edu>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 19 Sep 2008 15:34:31 -0500
References: <FE34F27F-8DDF-4C94-BC6E-E2ABF6000309@windriver.com>	<B5A5E01F9387F4409E67604C0257C71E409513@NDJSEVS25A.ndc.nasa.gov>	<24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>	<20080906013831.GD2074@zod.isi.edu>
	<8B8A001A-CA85-407B-9F1A-0FB1D847C21C@windriver.com>
	<48D3C90A.5050301@isi.edu>
	<0D2F6D02-8018-4684-B156-9ACC49D5B4E4@windriver.com>
	<48D3DE00.4060307@isi.edu>
	<98FC2F4C-9AB5-499F-850F-B73E899851FF@windriver.com>
	<48D3F7CD.8060006@isi.edu>
	<984843C7-BC33-4E48-AC75-414AE86152EF@windriver.com>
	<48D40B61.7060201@isi.edu>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 19 Sep 2008 20:34:34.0154 (UTC)
	FILETIME=[205428A0:01C91A97]
Cc: tcpm@ietf.org, rrs@cisco.com, mdalal@cisco.com,
	"Anantha Ramaiah \(ananth\)" <ananth@cisco.com>, Ted Faber <faber@isi.edu>
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

Ok,

(WG chair hat on)

It looks like we have consensus on this.  The wording in the  
Applicability section with SHOULD/MUST is fine, and when I write up  
the proto for passing tcpsecure on to the IESG, I'll include a comment  
that this issue was brought up during WGLC and cite references to  
other RFCs as examples.

			-David Borman

On Sep 19, 2008, at 3:28 PM, Joe Touch wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi, David,
>
> If we have docs we can point to, we're fine. I had questions from  
> others
> on this point; if we have precedent, we're set.
>
> Joe
>
> David Borman wrote:
>>
>> On Sep 19, 2008, at 2:04 PM, Joe Touch wrote:
>>
>> ...
>>>> But even if you do view it as a hierarchy, it is nothing out of the
>>>> ordinary.  No optional standard is going to be a MUST for who  
>>>> needs to
>>>> implement it, but then the rest of the standard itself will have  
>>>> still
>>>> have MUSTs in it for how to do the implementation.
>>>
>>> This is the part that others have commented to me on, and the  
>>> primary
>>> point of my note. If we can point to an optional standard that has  
>>> MUSTs
>>> therein, fine. If not, we're blazing new ground.
>>
>> That's easy, just look at any optional standards track RFC.  Here  
>> are a
>> few recent RFCs that I just picked at random:
>>
>> RFC 5001 "DNS Name Server Identifier (NSID) Option"
>> RFC 5007 "DHCPv6 Leasequery"
>> RFC 5010 "The Dynamic Host Configuration Protocol Version 4 (DHCPv4)
>> Relay Agent Flags Suboption"
>> RFC 5044 "Marker PDU Aligned Framing for TCP Specification"
>>
>> None of these are mandatory, so at best they would be SHOULD for the
>> overall document, and yet they all have MUSTs in them.  Need I go on?
>> The only difference I can see is that these standards don't have
>> explicit SHOULD/MAY in their applicability sections.
>>
>>
>>>> The only thing that
>>>> might be unique here is that the applicability statement has an  
>>>> explicit
>>>> SHOULD/MAY in it; they could be changed to should/may and I don't  
>>>> think
>>>> anything would be lost, but I also think it is fine as it is.
>>>
>>> It would definitely be lost; the doc would then have only MUSTs for
>>> certain items, which are not MUSTs if the overall document is a  
>>> SHOULD.
>>>
>>> This is the punchline; i.e., if we feel that we can't make  
>>> document-wide
>>> recommendations at different levels than individual items, then the
>>> document-wide concern needs to be reflected in the level of  
>>> individual
>>> items, and then I would claim that the current MUSTs should be  
>>> converted
>>> to SHOULDs. (I don't see other impacts).
>>
>> Again, the SHOULD/MAY in the applicability section is about who can
>> benefit from tcpsecure, and has nothing to do with how to implement
>> tcpsecure.  The other MUST/SHOULD/MAYs in tcpsecure are about how to
>> implement tcpsecure.
>>
>> It's "you SHOULD/MAY implement this, but if you do, you MUST do it  
>> this
>> way".  That's just normal standards stuff.
>>
>>            -David Borman
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFI1AthE5f5cImnZrsRAmTuAJ9reCQq4gM4b9Yzbidr61YRrFvbQwCfSkr9
> uf1SV+aHEvZkmsUr9TUIf8A=
> =iUCX
> -----END PGP SIGNATURE-----

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Sat Sep 20 16:05:06 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ECFBE3A68FD;
	Sat, 20 Sep 2008 16:05:05 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 19CE83A6814
	for <tcpm@core3.amsl.com>; Sat, 20 Sep 2008 16:05:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.389
X-Spam-Level: *
X-Spam-Status: No, score=1.389 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FRT_STOCK2=3.988]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id f5gRtAltiPMS for <tcpm@core3.amsl.com>;
	Sat, 20 Sep 2008 16:05:04 -0700 (PDT)
Received: from mx-out.forthnet.gr (mx-out.forthnet.gr [193.92.150.104])
	by core3.amsl.com (Postfix) with ESMTP id EC16F3A68FD
	for <tcpm@ietf.org>; Sat, 20 Sep 2008 16:05:03 -0700 (PDT)
Received: from mx-av-03.forthnet.gr (mx-av.forthnet.gr [193.92.150.27])
	by mx-out-03.forthnet.gr (8.14.3/8.14.3) with ESMTP id m8KN5nOr014893; 
	Sun, 21 Sep 2008 02:05:49 +0300
Received: from MX-IN-01.forthnet.gr (mx-in-01.forthnet.gr [193.92.150.23])
	by mx-av-03.forthnet.gr (8.14.3/8.14.3) with ESMTP id m8KN5Ijq005834;
	Sun, 21 Sep 2008 02:05:18 +0300
Received: from hell.hell.gr (adsl70-48.lsf.forthnet.gr [79.103.197.48])
	by MX-IN-01.forthnet.gr (8.14.3/8.14.3) with ESMTP id m8KN58OM027407;
	Sun, 21 Sep 2008 02:05:10 +0300
Authentication-Results: MX-IN-01.forthnet.gr smtp.mail=v13@v13.gr; spf=neutral
Authentication-Results: MX-IN-01.forthnet.gr header.from=v13@v13.gr;
	sender-id=neutral
From: Stefanos Harhalakis <v13@v13.gr>
To: tcpm@ietf.org
Date: Sun, 21 Sep 2008 02:05:08 +0300
User-Agent: KMail/1.9.9
References: <396556a20807311252j67b1ab26mf6511dbdae780fdd@mail.gmail.com>
	<4895B1F0.3070102@isi.edu>
	<396556a20808031106q18f6145cu7f6911ad8277d60c@mail.gmail.com>
In-Reply-To: <396556a20808031106q18f6145cu7f6911ad8277d60c@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200809210205.08232.v13@v13.gr>
Cc: Adam Langley <agl@imperialviolet.org>, Joe Touch <touch@isi.edu>
Subject: Re: [tcpm] Faster application handshakes with SYN/ACK payloads
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

Hello Adam,

I've just looked again at this. Its 1.5 month late but time runs fast.

> However, it appears that I've not made the case for the option yet. To
> do this, let me take HTTP as an example.
>
> HTTP is very latency sensitive[1]. Because of this, and guided by the
> sockets API, the client starts the exchange. Thus, if the client
> wishes to probe for optional features (like TLS upgrade: RFC2817) the
> exchange works like this:
>   Client --- OPTIONS ---> Server
>   Client <--- 101 Switching --- Server
>   Client --- GET ---> Server

AFAIKT, you're proposing that whenever the server side detects the SA option 
it switches to a different protocol behavior. Why not extend this even more 
and provide a generalized framework for more advanced customization?

I believe that this was not proposed before so here it goes:

Add a generic 'user data' option for SYN fields that would carry user data. 
Something like this:

KIND | LENGTH | DATA

Most of the time it should be: 

KIND | 3 | "1 Byte of data"

This is easy to implement (at the client side) and will allow for premature 
negotiation. For example this could include the client side application layer 
protocol capabilities. It can also be symmetric so that server side also 
sents some out-of-band data but most probably this should not be required 
with SA data (but an echo/acknowledge is required).

The implementation at the client will just require a setsockopt() that would 
set the extra header data and perhaps a getsockopt() that would get the reply 
(if any). This part needs some working.

> If HTTP sent a banner, like SMTP servers, then my life would be a lot
> easier! The banner could advertise all the extensions supported.
> However, without SYNACK payloads, this banner would cost another round
> trip.

Such a solution would allow the HTTP protocol to switch to HTTP-with-banner as 
you wished, without braking compatibility. Of course there can be many other 
uses for it. It is also 100% TCP friendly since a receiver that doesn't 
support such an option will just ignore it.
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Sat Sep 20 23:17:45 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BC4573A6933;
	Sat, 20 Sep 2008 23:17:45 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 16EE13A6933
	for <tcpm@core3.amsl.com>; Sat, 20 Sep 2008 23:17:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.417
X-Spam-Level: 
X-Spam-Status: No, score=-0.417 tagged_above=-999 required=5
	tests=[AWL=-1.806, BAYES_00=-2.599, FRT_STOCK2=3.988]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id EnF1PN2QPN36 for <tcpm@core3.amsl.com>;
	Sat, 20 Sep 2008 23:17:43 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id 15FB63A677D
	for <tcpm@ietf.org>; Sat, 20 Sep 2008 23:17:43 -0700 (PDT)
Received: from [192.168.1.45] (pool-71-106-119-240.lsanca.dsl-w.verizon.net
	[71.106.119.240])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m8L6Hi1m020885
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Sat, 20 Sep 2008 23:17:46 -0700 (PDT)
Message-ID: <48D5E708.4000006@isi.edu>
Date: Sat, 20 Sep 2008 23:17:44 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: Stefanos Harhalakis <v13@v13.gr>
References: <396556a20807311252j67b1ab26mf6511dbdae780fdd@mail.gmail.com>
	<4895B1F0.3070102@isi.edu>
	<396556a20808031106q18f6145cu7f6911ad8277d60c@mail.gmail.com>
	<200809210205.08232.v13@v13.gr>
In-Reply-To: <200809210205.08232.v13@v13.gr>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Adam Langley <agl@imperialviolet.org>, tcpm@ietf.org
Subject: Re: [tcpm] Faster application handshakes with SYN/ACK payloads
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi, Stefanos,

Stefanos Harhalakis wrote:
> Hello Adam,
> 
> I've just looked again at this. Its 1.5 month late but time runs fast.
> 
>> However, it appears that I've not made the case for the option yet. To
>> do this, let me take HTTP as an example.
>>
>> HTTP is very latency sensitive[1]. Because of this, and guided by the
>> sockets API, the client starts the exchange. Thus, if the client
>> wishes to probe for optional features (like TLS upgrade: RFC2817) the
>> exchange works like this:
>>   Client --- OPTIONS ---> Server
>>   Client <--- 101 Switching --- Server
>>   Client --- GET ---> Server
> 
> AFAIKT, you're proposing that whenever the server side detects the SA option 
> it switches to a different protocol behavior. Why not extend this even more 
> and provide a generalized framework for more advanced customization?
>
> I believe that this was not proposed before so here it goes:
> 
> Add a generic 'user data' option for SYN fields that would carry user data. 
> Something like this:
> 
> KIND | LENGTH | DATA
> 
> Most of the time it should be: 
> 
> KIND | 3 | "1 Byte of data"

I've been calling a a user data option for that reason, but I feel that
it changes TCP semantics. You're using a SYN option to change the
behavior of a service on a port. This requires substantial changes to
the interface as outlined in RFC793 (and implemented in sockets). In
particular, you need the server to be able to read the SYN options from
a socket before writing the response to a SYN-ACK.

This is outlined in previous emails to the list; it might be useful to
review them.

> This is easy to implement (at the client side) and will allow for premature 
> negotiation. 

As per above and in previous emails, it seems impossible to implement in
existing stacks without substantial modification of the socket interface.

> For example this could include the client side application layer 
> protocol capabilities. It can also be symmetric so that server side also 
> sents some out-of-band data but most probably this should not be required 
> with SA data (but an echo/acknowledge is required).
> 
> The implementation at the client will just require a setsockopt() that would 
> set the extra header data and perhaps a getsockopt() that would get the reply 
> (if any). This part needs some working.

The issue is that the data is carried in the DATA of the SYN, not in the
option (in the SYN-ACK reply once negotiated). A different issue is that
TCP cannot ensure that data, once written, is solely in the SYN - it
could be retransmitted in subsequent data packets anyway, so it should
not be assumed to be inside the SYN.

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

iEYEARECAAYFAkjV5wcACgkQE5f5cImnZrsR8ACeML9+DyBNxhXLuf5us0N3tKwo
S4gAn1rbAq/h/j1tRU+7pVAXS6pelstk
=u3UW
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Sat Sep 20 23:38:05 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BF5D03A6A39;
	Sat, 20 Sep 2008 23:38:05 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 054DB3A6A40
	for <tcpm@core3.amsl.com>; Sat, 20 Sep 2008 23:38:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.466
X-Spam-Level: 
X-Spam-Status: No, score=-1.466 tagged_above=-999 required=5
	tests=[AWL=-0.355, BAYES_05=-1.11]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id HMQP-M2qKDei for <tcpm@core3.amsl.com>;
	Sat, 20 Sep 2008 23:38:04 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id 121D03A698E
	for <tcpm@ietf.org>; Sat, 20 Sep 2008 23:38:04 -0700 (PDT)
Received: from [192.168.1.45] (pool-71-106-119-240.lsanca.dsl-w.verizon.net
	[71.106.119.240])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m8L6c8oA027204
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Sat, 20 Sep 2008 23:38:10 -0700 (PDT)
Message-ID: <48D5EBCF.7060401@isi.edu>
Date: Sat, 20 Sep 2008 23:38:07 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: Joe Touch <touch@ISI.EDU>
References: <396556a20807311252j67b1ab26mf6511dbdae780fdd@mail.gmail.com>
	<4895B1F0.3070102@isi.edu>
	<396556a20808031106q18f6145cu7f6911ad8277d60c@mail.gmail.com>
	<200809210205.08232.v13@v13.gr> <48D5E708.4000006@isi.edu>
In-Reply-To: <48D5E708.4000006@isi.edu>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Adam Langley <agl@imperialviolet.org>, tcpm@ietf.org,
	Stefanos Harhalakis <v13@v13.gr>
Subject: Re: [tcpm] Faster application handshakes with SYN/ACK payloads
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stefanos,

Here's a more brief, self-contained reply:

Joe Touch wrote:
> Hi, Stefanos,
> 
> Stefanos Harhalakis wrote:
>> Hello Adam,
> 
...
>> I believe that this was not proposed before so here it goes:
> 
>> Add a generic 'user data' option for SYN fields that would carry user data. 

There are two reasons for doing this:

	1- to send an out-of-band signal

	2- to send a signal that the server acts on before the
	handshake completes

#2 violates TCP semantics, so the SYN-ACK cannot have application data
that depends on the SYN's user data option (which is the desired result
here). The signal can't be acted on at the application layer until the
handshake completes.

#1 changes TCP semantics as well, since TCP does not have an out-of-band
signal path, and this would add that. However, because it cannot be
acted on until after the handshake completes, it cannot modify
application behavior that isn't required to wait until the handshake
finishes - i.e., apps that can write to the socket before the handshake
completes (e.g., to write data available to a SYN-ACK) would never
change because of this signal. The utility of this feature depends on
application behavior, which cannot be known, and thus cannot be relied upon.

As a result, I cannot see how this feature can be used to extend TCP.

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

iEYEARECAAYFAkjV684ACgkQE5f5cImnZrubhACbBf4fbf2No0G1LfwUikcLg6+w
njoAn3a9wBkWD5ijcseuD2w/9I3lPyhv
=IjGv
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Sun Sep 21 02:44:26 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 73F553A6966;
	Sun, 21 Sep 2008 02:44:26 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 41E473A68B6
	for <tcpm@core3.amsl.com>; Sun, 21 Sep 2008 02:44:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.305
X-Spam-Level: 
X-Spam-Status: No, score=-0.305 tagged_above=-999 required=5 tests=[AWL=1.694, 
	BAYES_00=-2.599, J_CHICKENPOX_34=0.6]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6xlEA4Wrwmsb for <tcpm@core3.amsl.com>;
	Sun, 21 Sep 2008 02:44:19 -0700 (PDT)
Received: from mx-out.forthnet.gr (mx-out.forthnet.gr [193.92.150.104])
	by core3.amsl.com (Postfix) with ESMTP id F3C253A687C
	for <tcpm@ietf.org>; Sun, 21 Sep 2008 02:44:18 -0700 (PDT)
Received: from mx-av-05.forthnet.gr (mx-av.forthnet.gr [193.92.150.27])
	by mx-out-05.forthnet.gr (8.14.3/8.14.3) with ESMTP id m8L9iYRw018039; 
	Sun, 21 Sep 2008 12:44:34 +0300
Received: from MX-IN-05.forthnet.gr (mx-in-05.forthnet.gr [193.92.150.32])
	by mx-av-05.forthnet.gr (8.14.3/8.14.3) with ESMTP id m8L9iYce021293;
	Sun, 21 Sep 2008 12:44:34 +0300
Received: from hell.hell.gr (adsl70-48.lsf.forthnet.gr [79.103.197.48])
	by MX-IN-05.forthnet.gr (8.14.3/8.14.3) with ESMTP id m8L9iUex023988;
	Sun, 21 Sep 2008 12:44:31 +0300
Authentication-Results: MX-IN-05.forthnet.gr smtp.mail=v13@v13.gr; spf=neutral
Authentication-Results: MX-IN-05.forthnet.gr header.from=v13@v13.gr;
	sender-id=neutral
From: Stefanos Harhalakis <v13@v13.gr>
To: Joe Touch <touch@isi.edu>
Date: Sun, 21 Sep 2008 12:44:30 +0300
User-Agent: KMail/1.9.9
References: <396556a20807311252j67b1ab26mf6511dbdae780fdd@mail.gmail.com>
	<48D5E708.4000006@isi.edu> <48D5EBCF.7060401@isi.edu>
In-Reply-To: <48D5EBCF.7060401@isi.edu>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200809211244.30186.v13@v13.gr>
Cc: Adam Langley <agl@imperialviolet.org>, tcpm@ietf.org
Subject: Re: [tcpm] Faster application handshakes with SYN/ACK payloads
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

On Sunday 21 September 2008, Joe Touch wrote:
> > Stefanos Harhalakis wrote:
> >> Add a generic 'user data' option for SYN fields that would carry user
> >> data.
>
> There are two reasons for doing this:
>
> 	1- to send an out-of-band signal
>
> 	2- to send a signal that the server acts on before the
> 	handshake completes
>
> #2 violates TCP semantics, so the SYN-ACK cannot have application data
> that depends on the SYN's user data option (which is the desired result
> here). The signal can't be acted on at the application layer until the
> handshake completes.
>
> #1 changes TCP semantics as well, since TCP does not have an out-of-band
> signal path, and this would add that. However, because it cannot be
> acted on until after the handshake completes, it cannot modify
> application behavior that isn't required to wait until the handshake
> finishes - i.e., apps that can write to the socket before the handshake
> completes (e.g., to write data available to a SYN-ACK) would never
> change because of this signal. The utility of this feature depends on
> application behavior, which cannot be known, and thus cannot be relied
> upon.

What I proposed is what you describe in #1. It is different from the 
SA-with-data proposal and thus it hasn't to do anything with #2. As I said in 
the original mail, it has to do with what Adam said:

"If HTTP sent a banner, like SMTP servers, then my life would be a lot
easier! The banner could advertise all the extensions supported.
However, without SYNACK payloads, this banner would cost another round
trip."

and more specifically with the first sentence. Supposing that (a hypothetical) 
HTTP/1.3 would support an optional banner, such an option would allow the 
server side to send it without braking backwards compatibility:

Client --> SYN+DATA --> Server
Client <-- SYNACK+? <-- Server
Client -->   ACK    --> Server
Client <--  BANNER  <-- Server

Without changing current behavior (It is not required that data be sent with 
the SYNACK option).

Also, this is not exactly "data" as there is space for a very small amount of 
information (some bits). Considering the possibilities of this, it can be 
used in many situations such as:
* HTTP or other protocols that use a well-known-port, to negotiate different
  behavior without introducing a new port number (SSL over port 80?).
* Cryptographic applications
* Anything that someone out there can think of. 8 bits (or a little more) of 
  information can be used for many things.

Wrong?

p.s: I can write a draft if this would clarify things.
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Sun Sep 21 07:08:23 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 14ACD3A6B5D;
	Sun, 21 Sep 2008 07:08:23 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3716F3A6B5E
	for <tcpm@core3.amsl.com>; Sun, 21 Sep 2008 07:08:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.327
X-Spam-Level: 
X-Spam-Status: No, score=-1.327 tagged_above=-999 required=5 tests=[AWL=0.651, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id hegTOSfKZr12 for <tcpm@core3.amsl.com>;
	Sun, 21 Sep 2008 07:08:21 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.174])
	by core3.amsl.com (Postfix) with ESMTP id 520933A6B5D
	for <tcpm@ietf.org>; Sun, 21 Sep 2008 07:08:21 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 27so1245814wfd.31
	for <tcpm@ietf.org>; Sun, 21 Sep 2008 07:08:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender
	:to:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references
	:x-google-sender-auth;
	bh=Df18QeBFG7T21NIPtJwsbIVuDdXDHuhaqW3FfD92vng=;
	b=boTkvNwxR4UVopFPghuXj1M/zFNYTUkimgjWf1rBkCrwxi4zrpCiueex+DFYIRLJmm
	AcigYyDZ5wuW0c/sjY2lU45xNpkfGjU6CqQLTqVcIQ2l0QKWf0GIBCPvWQF7bSJmBC3r
	1/y253LTA74DeKKRRVzFck2ts+q9p6//YZvbM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references:x-google-sender-auth;
	b=yBTVSEJSKnuZB4u8s/j2B614sxamNJu0RDKUHN+BMTgV4/K7yRY7kacut/PmP1ueN3
	5rmj3/caCGIx4wivADkkvcFqNslBEP4X3vCML98Si4kM270pxBBRdiOuVGRHstusR53Y
	2XgN2maXheXfbGewIF8srq1suK2zaXLirNIXA=
Received: by 10.142.156.2 with SMTP id d2mr925985wfe.271.1222006118495;
	Sun, 21 Sep 2008 07:08:38 -0700 (PDT)
Received: by 10.142.213.20 with HTTP; Sun, 21 Sep 2008 07:08:38 -0700 (PDT)
Message-ID: <396556a20809210708k714f3218hed50a44b74189e84@mail.gmail.com>
Date: Sun, 21 Sep 2008 07:08:38 -0700
From: "Adam Langley" <agl@imperialviolet.org>
To: "Stefanos Harhalakis" <v13@v13.gr>
In-Reply-To: <200809211244.30186.v13@v13.gr>
MIME-Version: 1.0
Content-Disposition: inline
References: <396556a20807311252j67b1ab26mf6511dbdae780fdd@mail.gmail.com>
	<48D5E708.4000006@isi.edu> <48D5EBCF.7060401@isi.edu>
	<200809211244.30186.v13@v13.gr>
X-Google-Sender-Auth: 1003f02e3e029ed4
Cc: tcpm@ietf.org, Joe Touch <touch@isi.edu>
Subject: Re: [tcpm] Faster application handshakes with SYN/ACK payloads
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

On Sun, Sep 21, 2008 at 2:44 AM, Stefanos Harhalakis <v13@v13.gr> wrote:
> Also, this is not exactly "data" as there is space for a very small amount of
> information (some bits). Considering the possibilities of this, it can be
> used in many situations such as:
> * HTTP or other protocols that use a well-known-port, to negotiate different
>  behavior without introducing a new port number (SSL over port 80?).
> * Cryptographic applications
> * Anything that someone out there can think of. 8 bits (or a little more) of
>  information can be used for many things.

Firstly, one counterargument that several have used in the past is
that a round-trip-time is unimportant and any such scheme can be
achieved without TCP changes by burning an RTT. I disagree with this,
but I can't release any data to back up that assertion, so it's still
a reasonable counterargument.

I also wonder how much of an advantage 8 bits, as opposed to a single
bit, gives you. Although, once you have defined an option, 8 bits is
almost as cheap as a single bit, so 'why not' is a reasonable
position.

Just from a personal point of view. I'm now using information from DNS
and from previous connections to the same host to achieve this "early"
information entirely within userspace. However, I still needed a new
port because "transparent" proxies aren't very transparent when you
stop speaking HTTP over port 80.



AGL

-- 
Adam Langley agl@imperialviolet.org http://www.imperialviolet.org
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Sun Sep 21 09:30:51 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 99E033A6B35;
	Sun, 21 Sep 2008 09:30:51 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 25B893A6B16
	for <tcpm@core3.amsl.com>; Sun, 21 Sep 2008 09:30:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.874
X-Spam-Level: 
X-Spam-Status: No, score=-1.874 tagged_above=-999 required=5 tests=[AWL=0.125, 
	BAYES_00=-2.599, J_CHICKENPOX_34=0.6]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id BCYk5DLIe57C for <tcpm@core3.amsl.com>;
	Sun, 21 Sep 2008 09:30:48 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id A06E93A69E1
	for <tcpm@ietf.org>; Sun, 21 Sep 2008 09:30:48 -0700 (PDT)
Received: from [192.168.1.45] (pool-71-106-119-240.lsanca.dsl-w.verizon.net
	[71.106.119.240])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m8LGUeTw028986
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Sun, 21 Sep 2008 09:30:42 -0700 (PDT)
Message-ID: <48D676AF.5030509@isi.edu>
Date: Sun, 21 Sep 2008 09:30:39 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: Stefanos Harhalakis <v13@v13.gr>
References: <396556a20807311252j67b1ab26mf6511dbdae780fdd@mail.gmail.com>
	<48D5E708.4000006@isi.edu> <48D5EBCF.7060401@isi.edu>
	<200809211244.30186.v13@v13.gr>
In-Reply-To: <200809211244.30186.v13@v13.gr>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Adam Langley <agl@imperialviolet.org>, tcpm@ietf.org
Subject: Re: [tcpm] Faster application handshakes with SYN/ACK payloads
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Stefanos Harhalakis wrote:
> On Sunday 21 September 2008, Joe Touch wrote:
>>> Stefanos Harhalakis wrote:
>>>> Add a generic 'user data' option for SYN fields that would carry user
>>>> data.
>> There are two reasons for doing this:
>>
>> 	1- to send an out-of-band signal
>>
>> 	2- to send a signal that the server acts on before the
>> 	handshake completes
>>
>> #2 violates TCP semantics, so the SYN-ACK cannot have application data
>> that depends on the SYN's user data option (which is the desired result
>> here). The signal can't be acted on at the application layer until the
>> handshake completes.
>>
>> #1 changes TCP semantics as well, since TCP does not have an out-of-band
>> signal path, and this would add that. However, because it cannot be
>> acted on until after the handshake completes, it cannot modify
>> application behavior that isn't required to wait until the handshake
>> finishes - i.e., apps that can write to the socket before the handshake
>> completes (e.g., to write data available to a SYN-ACK) would never
>> change because of this signal. The utility of this feature depends on
>> application behavior, which cannot be known, and thus cannot be relied
>> upon.
> 
> What I proposed is what you describe in #1. It is different from the 
> SA-with-data proposal and thus it hasn't to do anything with #2. As I said in 
> the original mail, it has to do with what Adam said:
> 
> "If HTTP sent a banner, like SMTP servers, then my life would be a lot
> easier! The banner could advertise all the extensions supported.
> However, without SYNACK payloads, this banner would cost another round
> trip."

HTTP does send a banner of that type; the issue is that you want #2
above - if you don't act on the banner info until after the TWHS, you
"waste" an RTT waiting for the connection to be established before the
server can reply.

That's a **design feature** and requirement of TCP, not a "waste".

> and more specifically with the first sentence. Supposing that (a hypothetical) 
> HTTP/1.3 would support an optional banner, such an option would allow the 
> server side to send it without braking backwards compatibility:
> 
> Client --> SYN+DATA --> Server
> Client <-- SYNACK+? <-- Server
> Client -->   ACK    --> Server
> Client <--  BANNER  <-- Server

The server can start sending data before the TWHS completes (let's call
the above "sequence 1" and the below "sequence 2"):

Client --> SYN+DATA --> Server
Client <-- SYNACK+? <-- Server
Client <--  BANNER  <-- Server
Client -->   ACK    --> Server

In sequence 1, the banner can depend on the SYN+DATA data. In BOTH
sequences, however, the SYNACK+? "?" **cannot** depend on the SYN+DATA data.

> Without changing current behavior (It is not required that data be sent with 
> the SYNACK option).
> 
> Also, this is not exactly "data" as there is space for a very small amount of 
> information (some bits). Considering the possibilities of this, it can be 
> used in many situations such as:
> * HTTP or other protocols that use a well-known-port, to negotiate different
>   behavior without introducing a new port number (SSL over port 80?).
> * Cryptographic applications
> * Anything that someone out there can think of. 8 bits (or a little more) of 
>   information can be used for many things.
> 
> Wrong?
> 
> p.s: I can write a draft if this would clarify things.

I think you're exploring the space of the discussion that has already
been had on this list...

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

iEUEARECAAYFAkjWdq8ACgkQE5f5cImnZrttuwCY3gRvZM7rIEWn3Afu9O4aKEss
MgCdHhBYcwQPli47R7YfewyAKNoVPPo=
=xJ3F
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Sun Sep 21 11:39:43 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6F0EC3A6AFD;
	Sun, 21 Sep 2008 11:39:43 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 75EA53A6A8C
	for <tcpm@core3.amsl.com>; Sun, 21 Sep 2008 11:39:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.343
X-Spam-Level: 
X-Spam-Status: No, score=-0.343 tagged_above=-999 required=5
	tests=[AWL=-2.931, BAYES_00=-2.599, FRT_STOCK2=3.988,
	J_CHICKENPOX_101=0.6, J_CHICKENPOX_34=0.6]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id QUoQRINZ+-kr for <tcpm@core3.amsl.com>;
	Sun, 21 Sep 2008 11:39:41 -0700 (PDT)
Received: from mx-out.forthnet.gr (mx-out.forthnet.gr [193.92.150.104])
	by core3.amsl.com (Postfix) with ESMTP id 0260D3A6947
	for <tcpm@ietf.org>; Sun, 21 Sep 2008 11:39:40 -0700 (PDT)
Received: from mx-av-05.forthnet.gr (mx-av.forthnet.gr [193.92.150.27])
	by mx-out-03.forthnet.gr (8.14.3/8.14.3) with ESMTP id m8LIeR8O025520; 
	Sun, 21 Sep 2008 21:40:27 +0300
Received: from MX-IN-05.forthnet.gr (mx-in-05.forthnet.gr [193.92.150.32])
	by mx-av-05.forthnet.gr (8.14.3/8.14.3) with ESMTP id m8LIdu2V027684;
	Sun, 21 Sep 2008 21:39:56 +0300
Received: from hell.hell.gr (adsl70-48.lsf.forthnet.gr [79.103.197.48])
	by MX-IN-05.forthnet.gr (8.14.3/8.14.3) with ESMTP id m8LIdrxD012457;
	Sun, 21 Sep 2008 21:39:54 +0300
Authentication-Results: MX-IN-05.forthnet.gr smtp.mail=v13@v13.gr; spf=neutral
Authentication-Results: MX-IN-05.forthnet.gr header.from=v13@v13.gr;
	sender-id=neutral
From: Stefanos Harhalakis <v13@v13.gr>
To: Joe Touch <touch@isi.edu>
Date: Sun, 21 Sep 2008 21:39:53 +0300
User-Agent: KMail/1.9.9
References: <396556a20807311252j67b1ab26mf6511dbdae780fdd@mail.gmail.com>
	<200809211244.30186.v13@v13.gr> <48D676AF.5030509@isi.edu>
In-Reply-To: <48D676AF.5030509@isi.edu>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200809212139.53591.v13@v13.gr>
Cc: Adam Langley <agl@imperialviolet.org>, tcpm@ietf.org
Subject: Re: [tcpm] Faster application handshakes with SYN/ACK payloads
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

Hello,

I'm sending this reply mostly to clarify the things. Perhaps there is 
something that I don't understand or I don't express well. If it is so, 
please excuse the stubbornness of mine.

On Sunday 21 September 2008, Joe Touch wrote:
> HTTP does send a banner of that type; the issue is that you want #2
> above - if you don't act on the banner info until after the TWHS, you
> "waste" an RTT waiting for the connection to be established before the
> server can reply.
>
> That's a **design feature** and requirement of TCP, not a "waste".

I don't exactly understand what you mean by saying that HTTP sends a banner. 
An HTTP server will never send anything unless it is triggered to do so by a 
client request. Creating an HTTP version that sends an initial one-line (or 
more) will break backwards compatibility. (no?)

> > and more specifically with the first sentence. Supposing that (a
> > hypothetical) HTTP/1.3 would support an optional banner, such an option
> > would allow the server side to send it without braking backwards
> > compatibility:
> >
> > Client --> SYN+DATA --> Server
> > Client <-- SYNACK+? <-- Server
> > Client -->   ACK    --> Server
> > Client <--  BANNER  <-- Server
>
> The server can start sending data before the TWHS completes (let's call
> the above "sequence 1" and the below "sequence 2"):
>
> Client --> SYN+DATA --> Server
> Client <-- SYNACK+? <-- Server
> Client <--  BANNER  <-- Server
> Client -->   ACK    --> Server
>
> In sequence 1, the banner can depend on the SYN+DATA data. In BOTH
> sequences, however, the SYNACK+? "?" **cannot** depend on the SYN+DATA
> data.

I believe that I didn't describe well what I meant (or else I don't completely 
understand what you're saying).

I'm talking about (lets say) 8 bits of out-of-band information that the client 
can send to the server side and vice-versa. The server side application will 
most probably get those data after the TWHS completes. There is no placed 
requirement to do otherwise.

So, a complete trace (with most function arguments ommited or altered for 
simplicity, no error handling, etc etc :-) of a non-well thought proposal 
(there are issues) would be:

(C: Client, S: Server)

# Server side listens for connections, supports USER_DATA
S: s0=socket()
S: setsockopt(s0, SO_USER_DATA, 0x02)
S: bind(s0, 0.0.0.0, 80)
S: listen(s0)

# Client attempts connection. Sends USER_DATA
C: s=socket()
C: setsockopt(s, SO_USER_DATA, 0x01)
C: connect(1.2.3.4, 80)

# Connection is established. Remote USER_DATA is available to both ends
S: s=accept()
S: getsockopt(s, SO_REMOTE_USER_DATA, &mybuf)
C: getsockopt(s, SO_REMOTE_USER_DATA, &mybuf)

At this point, the client side has connected to the server side and they have 
exchanged one byte of out-of-band data (C->S: 0x01, S-C: 0x02). This is all 
done without messing with the TWHS.

>From the TCP's point of view, the above would look like:

* Client sends SYN with TCP option USER_DATA, length 1, data 0x01
* Server receives SYN, supports USER_DATA, responds with SYNACK with option 
USER_DATA length 1, data 0x02 and *no* data in the segment.
* Client receives SYNACK and responds with ACK
* Everything continues normally

The only difference with existing TCP behavior is that a 3-bytes TCP option is 
included in the SYN and SYNACK segments. There is no messing with user data 
in SYNACK at all. Perhaps the USER_DATA option name is confussing. USER_DATA 
is just an arbitrary name for a KIND of an option.

> > p.s: I can write a draft if this would clarify things.
>
> I think you're exploring the space of the discussion that has already
> been had on this list...

Adam's proposal was that data (outside of TCP options) would be sent with the 
SYNACK field. I still believe that the USER_DATA option is not related to 
that. Perhaps if I hadn't initially related this proposal with Adam's 
proposal (since it is related to his 'wish' and not to his proposal) it would 
be clearer?

I'm *really* sorry if what you say above is true and I just don't understand 
something. 

p.s. Do you know if there is a way to force the tcpm mailing list to send me 
duplicates for mails that are CC'd to me too? It seems that all mails that 
I'm CC'd are only sent directly and not via the list. I've set the "Avoid 
duplicate copies of messages?" to "No" in the mailman options but there was 
no change.
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Sun Sep 21 11:49:43 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0720C3A6A7F;
	Sun, 21 Sep 2008 11:49:43 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 474993A6A7F
	for <tcpm@core3.amsl.com>; Sun, 21 Sep 2008 11:49:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.35
X-Spam-Level: 
X-Spam-Status: No, score=-2.35 tagged_above=-999 required=5 tests=[AWL=0.249, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id qgcLl4MNOxof for <tcpm@core3.amsl.com>;
	Sun, 21 Sep 2008 11:49:40 -0700 (PDT)
Received: from mx-out.forthnet.gr (mx-out.forthnet.gr [193.92.150.104])
	by core3.amsl.com (Postfix) with ESMTP id DE9D73A68D6
	for <tcpm@ietf.org>; Sun, 21 Sep 2008 11:49:39 -0700 (PDT)
Received: from mx-av-05.forthnet.gr (mx-av.forthnet.gr [193.92.150.27])
	by mx-out-03.forthnet.gr (8.14.3/8.14.3) with ESMTP id m8LIoRPU027986; 
	Sun, 21 Sep 2008 21:50:27 +0300
Received: from MX-IN-05.forthnet.gr (mx-in-05.forthnet.gr [193.92.150.32])
	by mx-av-05.forthnet.gr (8.14.3/8.14.3) with ESMTP id m8LInuYH030966;
	Sun, 21 Sep 2008 21:49:56 +0300
Received: from hell.hell.gr (adsl70-48.lsf.forthnet.gr [79.103.197.48])
	by MX-IN-05.forthnet.gr (8.14.3/8.14.3) with ESMTP id m8LIntuM022757;
	Sun, 21 Sep 2008 21:49:55 +0300
Authentication-Results: MX-IN-05.forthnet.gr smtp.mail=v13@v13.gr; spf=neutral
Authentication-Results: MX-IN-05.forthnet.gr header.from=v13@v13.gr;
	sender-id=neutral
From: Stefanos Harhalakis <v13@v13.gr>
To: "Adam Langley" <agl@imperialviolet.org>
Date: Sun, 21 Sep 2008 21:49:54 +0300
User-Agent: KMail/1.9.9
References: <396556a20807311252j67b1ab26mf6511dbdae780fdd@mail.gmail.com>
	<200809211244.30186.v13@v13.gr>
	<396556a20809210708k714f3218hed50a44b74189e84@mail.gmail.com>
In-Reply-To: <396556a20809210708k714f3218hed50a44b74189e84@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200809212149.54848.v13@v13.gr>
Cc: tcpm@ietf.org, Joe Touch <touch@isi.edu>
Subject: Re: [tcpm] Faster application handshakes with SYN/ACK payloads
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

On Sunday 21 September 2008, Adam Langley wrote:
> On Sun, Sep 21, 2008 at 2:44 AM, Stefanos Harhalakis <v13@v13.gr> wrote:
> > Also, this is not exactly "data" as there is space for a very small
> > amount of information (some bits). Considering the possibilities of this,
> > it can be used in many situations such as:
> > * HTTP or other protocols that use a well-known-port, to negotiate
> > different behavior without introducing a new port number (SSL over port
> > 80?). * Cryptographic applications
> > * Anything that someone out there can think of. 8 bits (or a little more)
> > of information can be used for many things.
>
> Firstly, one counterargument that several have used in the past is
> that a round-trip-time is unimportant and any such scheme can be
> achieved without TCP changes by burning an RTT. I disagree with this,
> but I can't release any data to back up that assertion, so it's still
> a reasonable counterargument.

I don't believe that this is always possible when trying to keep backwards 
compatibility. Some (stupid ?) examples that just passed from my mind:
* (generic) Early protocol selection
* SSL over port 80, 25, etc
* Early virtualhost selection (with cooperation from the DNS)
* Hidden backdoors :P
* A kind of tunneling
* Anything that someone out there can imagine

> I also wonder how much of an advantage 8 bits, as opposed to a single
> bit, gives you. Although, once you have defined an option, 8 bits is
> almost as cheap as a single bit, so 'why not' is a reasonable
> position.

That's a good question that I don't have an answer for :-)
Indeed, everything that 8 bits can do can also be done with 1 bit and 
everything else in the data part. The only exception I can think of that of 
an intermediate firewall/NAT-box that may make a decision based on that 
field.

> Just from a personal point of view. I'm now using information from DNS
> and from previous connections to the same host to achieve this "early"
> information entirely within userspace. However, I still needed a new
> port because "transparent" proxies aren't very transparent when you
> stop speaking HTTP over port 80.

I don't see how transparent proxies will be affected by this. If they don't 
(want to) support the USER_DATA option then they will not reply to it and 
there will be no harm at all.
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Sun Sep 21 14:53:00 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3C40C28C193;
	Sun, 21 Sep 2008 14:53:00 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EA97D3A6C18
	for <tcpm@core3.amsl.com>; Sun, 21 Sep 2008 14:52:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.886
X-Spam-Level: 
X-Spam-Status: No, score=-1.886 tagged_above=-999 required=5 tests=[AWL=0.113, 
	BAYES_00=-2.599, J_CHICKENPOX_34=0.6]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id IcQwnPxiXN2I for <tcpm@core3.amsl.com>;
	Sun, 21 Sep 2008 14:52:58 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id 238A03A6877
	for <tcpm@ietf.org>; Sun, 21 Sep 2008 14:52:58 -0700 (PDT)
Received: from [192.168.1.45] (pool-71-106-119-240.lsanca.dsl-w.verizon.net
	[71.106.119.240])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m8LLqkRg028952
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Sun, 21 Sep 2008 14:52:48 -0700 (PDT)
Message-ID: <48D6C22E.9060705@isi.edu>
Date: Sun, 21 Sep 2008 14:52:46 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: Stefanos Harhalakis <v13@v13.gr>
References: <396556a20807311252j67b1ab26mf6511dbdae780fdd@mail.gmail.com>
	<200809211244.30186.v13@v13.gr> <48D676AF.5030509@isi.edu>
	<200809212139.53591.v13@v13.gr>
In-Reply-To: <200809212139.53591.v13@v13.gr>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Adam Langley <agl@imperialviolet.org>, tcpm@ietf.org
Subject: Re: [tcpm] Faster application handshakes with SYN/ACK payloads
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi, Stefanos,

Stefanos Harhalakis wrote:
> Hello,
> 
> I'm sending this reply mostly to clarify the things. Perhaps there is 
> something that I don't understand or I don't express well. If it is so, 
> please excuse the stubbornness of mine.
> 
> On Sunday 21 September 2008, Joe Touch wrote:
>> HTTP does send a banner of that type; the issue is that you want #2
>> above - if you don't act on the banner info until after the TWHS, you
>> "waste" an RTT waiting for the connection to be established before the
>> server can reply.
>>
>> That's a **design feature** and requirement of TCP, not a "waste".
> 
> I don't exactly understand what you mean by saying that HTTP sends a banner. 
> An HTTP server will never send anything unless it is triggered to do so by a 
> client request. Creating an HTTP version that sends an initial one-line (or 
> more) will break backwards compatibility. (no?)

Yes - that would be a different service, which is also why it should sit
on a different port.

>>> and more specifically with the first sentence. Supposing that (a
>>> hypothetical) HTTP/1.3 would support an optional banner, such an option
>>> would allow the server side to send it without braking backwards
>>> compatibility:
>>>
>>> Client --> SYN+DATA --> Server
>>> Client <-- SYNACK+? <-- Server
>>> Client -->   ACK    --> Server
>>> Client <--  BANNER  <-- Server
>> The server can start sending data before the TWHS completes (let's call
>> the above "sequence 1" and the below "sequence 2"):
>>
>> Client --> SYN+DATA --> Server
>> Client <-- SYNACK+? <-- Server
>> Client <--  BANNER  <-- Server
>> Client -->   ACK    --> Server
>>
>> In sequence 1, the banner can depend on the SYN+DATA data. In BOTH
>> sequences, however, the SYNACK+? "?" **cannot** depend on the SYN+DATA
>> data.
> 
> I believe that I didn't describe well what I meant (or else I don't completely 
> understand what you're saying).
> 
> I'm talking about (lets say) 8 bits of out-of-band information that the client 
> can send to the server side and vice-versa. The server side application will 
> most probably get those data after the TWHS completes. There is no placed 
> requirement to do otherwise.

If the data is "out of band", then the application needs to understand
what it means. TCP ports currently specify services with no out-of-band
information. If you want a service that understands that kind of
additional information, those would be a different service.

> So, a complete trace (with most function arguments ommited or altered for 
> simplicity, no error handling, etc etc :-) of a non-well thought proposal 
> (there are issues) would be:
...

Understood; you're setting up a second data channel, and ACKing it
separately.

First, that can't be used to help reduce the RTT as Adam has suggested
without changing the "app doesn't get data until the handshake
completes" semantics.

Second, that information can't be used by the app unless you change the
*service* semantics, which means these are different services.

TCP options are for changing TCP behavior, not changing application
semantics, IMO.

> p.s. Do you know if there is a way to force the tcpm mailing list to send me 
> duplicates for mails that are CC'd to me too? It seems that all mails that 
> I'm CC'd are only sent directly and not via the list. I've set the "Avoid 
> duplicate copies of messages?" to "No" in the mailman options but there was 
> no change.

You should take this up with the list manager; I'm not sure of how TCPM
is setup.

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

iEYEARECAAYFAkjWwi4ACgkQE5f5cImnZruBWwCgve+wUlxDLD7oMzxseHmuzw1q
Tr8Anjdh7tnzmJdoewsSzHTBgRriVo3L
=h2jo
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Fri Sep 26 08:56:16 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1A3303A6B2C;
	Fri, 26 Sep 2008 08:56:16 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2A3E03A6820
	for <tcpm@core3.amsl.com>; Fri, 26 Sep 2008 08:51:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.109
X-Spam-Level: 
X-Spam-Status: No, score=-1.109 tagged_above=-999 required=5
	tests=[BAYES_05=-1.11, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ZJTasP+VVbf0 for <tcpm@core3.amsl.com>;
	Fri, 26 Sep 2008 08:51:19 -0700 (PDT)
Received: from prod-mail-xrelay01.akamai.com (prod-mail-xrelay01.akamai.com
	[72.246.2.12]) by core3.amsl.com (Postfix) with ESMTP id 899693A67F6
	for <tcpm@ietf.org>; Fri, 26 Sep 2008 08:51:19 -0700 (PDT)
Received: from prod-mail-xrelay01.akamai.com (localhost [127.0.0.1])
	by postfix.imss70 (Postfix) with ESMTP id B01B1C00039F
	for <tcpm@ietf.org>; Fri, 26 Sep 2008 15:48:54 +0000 (GMT)
Received: from prod-mail-relay01.akamai.com (unknown [172.17.50.20])
	by prod-mail-xrelay01.akamai.com (Postfix) with ESMTP id 968C1C00039B
	for <tcpm@ietf.org>; Fri, 26 Sep 2008 15:48:54 +0000 (UTC)
Received: from USMA1EX-GATE1.kendall.corp.akamai.com
	(usma1ex-gate1.kendall.corp.akamai.com [172.17.0.215])
	by prod-mail-relay01.akamai.com (Postfix) with ESMTP id 89AAD1000089
	for <tcpm@ietf.org>; Fri, 26 Sep 2008 15:48:54 +0000 (GMT)
Received: from MAVS1.kendall.corp.akamai.com ([172.17.33.15]) by
	USMA1EX-GATE1.kendall.corp.akamai.com with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 26 Sep 2008 11:48:54 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 26 Sep 2008 11:48:53 -0400
Message-ID: <5342C364A2C3A6458B15BB147FB4B724AC479D@MAVS1.kendall.corp.akamai.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: End to End Proprietary Information Field - Request for a new TCP
	option
thread-index: Ackf72CobUdqY6YZQAOw49je82psVA==
From: "Ish Shalom, Ran" <rishshal@akamai.com>
To: <tcpm@ietf.org>
X-OriginalArrivalTime: 26 Sep 2008 15:48:54.0253 (UTC)
	FILETIME=[610B11D0:01C91FEF]
Subject: [tcpm] End to End Proprietary Information Field - Request for a new
	TCP option
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0886685776=="
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0886685776==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C91FEF.60BDACAF"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C91FEF.60BDACAF
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Increasingly businesses and their workforces are becoming more and more
distributed as they spread globally and move their offices to be closer
to their customers. At the same time, financial wisdom dictates strict
cost control. The combination of which pushed more business to use the
Internet as a transport medium for remote offices and/or employees.=20

IP addresses shortage, privacy and security concerns have generated a
myriad of solutions in the form of NATs, PATs, firewalls, etc. As a
result, local information such as private IP addresses, ports and
potentially additional local private information often gets rewritten
and lost when a session traverses these functions. Furthermore, some
gateway services might terminate sessions in order to carry them over a
different medium or using a different service. All of which result in
the same way - lost of end to end transparency. However, occasionally
applications and/or network administrators may need a means to
communicate local private IP information across the Internet domain so
that the far end may be able to process the session correctly.=20

I would like to propose creating a proprietary information channel using
a dedicated TCP option that can be used by such application to
communicate private local information across the internet. A flexible
end-to-end private channel will allow Service Providers and application
vendors to provide seamless communication across the Internet domain
despite the many intermediate functions that are in place today.

Sincerely,

Ran Ish-Shalom
Akamai technologies

------_=_NextPart_001_01C91FEF.60BDACAF
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>End to End Proprietary Information Field - Request for a new TCP =
option</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT FACE=3D"Times New Roman">Increasingly businesses and their =
workforces are becoming more and more distributed as they spread =
globally and move their offices to be closer to their customers. At the =
same time, financial wisdom dictates strict cost control. The =
combination of which pushed more business to use the Internet as a =
transport medium for remote offices and/or employees. </FONT></P>

<P><FONT FACE=3D"Times New Roman">IP addresses shortage, privacy and =
security concerns have generated a myriad of solutions in the form of =
NATs, PATs, firewalls, etc. As a result, local information such as =
private IP addresses, ports and potentially additional local private =
information often gets rewritten and lost when a session traverses these =
functions. Furthermore, some gateway services might terminate sessions =
in order to carry them over a different medium or using a different =
service. All of which result in the same way - lost of end to end =
transparency. However, occasionally applications and/or network =
administrators may need a means to communicate local private IP =
information across the Internet domain so that the far end may be able =
to process the session correctly. </FONT></P>

<P><FONT FACE=3D"Times New Roman">I would like to propose creating a =
proprietary information channel using a dedicated TCP option that can be =
used by such application to communicate private local information across =
the internet. A flexible end-to-end private channel will allow Service =
Providers and application vendors to provide seamless communication =
across the Internet domain despite the many intermediate functions that =
are in place today.</FONT></P>

<P><FONT FACE=3D"Times New Roman">Sincerely,</FONT>
</P>

<P><FONT FACE=3D"Times New Roman">Ran Ish-Shalom</FONT>

<BR><FONT FACE=3D"Times New Roman">Akamai technologies</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C91FEF.60BDACAF--

--===============0886685776==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm

--===============0886685776==--


From tcpm-bounces@ietf.org  Fri Sep 26 09:11:19 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 59F5F3A6A4C;
	Fri, 26 Sep 2008 09:11:19 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8B2093A6A4C
	for <tcpm@core3.amsl.com>; Fri, 26 Sep 2008 09:11:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.469
X-Spam-Level: 
X-Spam-Status: No, score=-2.469 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, SARE_RMML_Stock9=0.13]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id dOZXhhaZMIFX for <tcpm@core3.amsl.com>;
	Fri, 26 Sep 2008 09:11:17 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id 63B1E3A689A
	for <tcpm@ietf.org>; Fri, 26 Sep 2008 09:11:17 -0700 (PDT)
Received: from [128.9.176.35] (c1-vpn5.isi.edu [128.9.176.35])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m8QGAAS1020226
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Fri, 26 Sep 2008 09:10:12 -0700 (PDT)
Message-ID: <48DD0961.4020802@isi.edu>
Date: Fri, 26 Sep 2008 09:10:09 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "Ish Shalom, Ran" <rishshal@akamai.com>
References: <5342C364A2C3A6458B15BB147FB4B724AC479D@MAVS1.kendall.corp.akamai.com>
In-Reply-To: <5342C364A2C3A6458B15BB147FB4B724AC479D@MAVS1.kendall.corp.akamai.com>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tcpm@ietf.org
Subject: Re: [tcpm] End to End Proprietary Information Field - Request for a
 new	TCP option
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ish,

TCP options signal changes to the TCP protocol. That protocol is not
proprietary, and I do not support making it - or any variants thereof -
proprietary.

Proprietary information about a TCP connection is already encoded in the
port number, and in-band in the application data. If the information
determines the nature of the application data, it is a port number
issue. If the information is application data, it belongs in the data path.

I see no reason for a TCP option based on this argument, nor do I see a
reason for a proprietary TCP option either.

Additional note below...

Joe

Ish Shalom, Ran wrote:
> Increasingly businesses and their workforces are becoming more and more
> distributed as they spread globally and move their offices to be closer
> to their customers. At the same time, financial wisdom dictates strict
> cost control. The combination of which pushed more business to use the
> Internet as a transport medium for remote offices and/or employees.
> 
> IP addresses shortage, privacy and security concerns have generated a
> myriad of solutions in the form of NATs, PATs, firewalls, etc. As a
> result, local information such as private IP addresses, ports and
> potentially additional local private information often gets rewritten
> and lost when a session traverses these functions. Furthermore, some
> gateway services might terminate sessions in order to carry them over a
> different medium or using a different service. All of which result in
> the same way - lost of end to end transparency. However, occasionally
> applications and/or network administrators may need a means to
> communicate local private IP information across the Internet domain so
> that the far end may be able to process the session correctly.

Any device that destroys information of a TCP connection (e.g.,
destination port of a SYN, or rewriting IP addresss) cannot be trusted
to preserve TCP options either. They often rewrite or omit such options
anyway.

> I would like to propose creating a proprietary information channel using
> a dedicated TCP option that can be used by such application to
> communicate private local information across the internet. A flexible
> end-to-end private channel will allow Service Providers and application
> vendors to provide seamless communication across the Internet domain
> despite the many intermediate functions that are in place today.
> 
> Sincerely,
> 
> Ran Ish-Shalom
> Akamai technologies
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkjdCWEACgkQE5f5cImnZruh1wCfdUvaaEp7Zfmz0IljtN6rXLrA
zegAn31/adWJ8mpOuMDGfANcBlPmG2n0
=88Rb
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Fri Sep 26 09:22:06 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 40F993A6B76;
	Fri, 26 Sep 2008 09:22:06 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 160793A6B76
	for <tcpm@core3.amsl.com>; Fri, 26 Sep 2008 09:22:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.469
X-Spam-Level: 
X-Spam-Status: No, score=-2.469 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, SARE_RMML_Stock9=0.13]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id UyL6SU87tbIv for <tcpm@core3.amsl.com>;
	Fri, 26 Sep 2008 09:22:04 -0700 (PDT)
Received: from prod-mail-xrelay03.akamai.com (prod-mail-xrelay03.akamai.com
	[72.247.150.167])
	by core3.amsl.com (Postfix) with ESMTP id 3E9EF3A6B6E
	for <tcpm@ietf.org>; Fri, 26 Sep 2008 09:22:04 -0700 (PDT)
Received: from prod-mail-xrelay03.akamai.com (localhost [127.0.0.1])
	by postfix.imss70 (Postfix) with ESMTP id 2F9191000055;
	Fri, 26 Sep 2008 16:22:11 +0000 (GMT)
Received: from prod-mail-relay03.akamai.com (unknown [63.116.109.131])
	by prod-mail-xrelay03.akamai.com (Postfix) with ESMTP id 164AF1000048; 
	Fri, 26 Sep 2008 16:22:11 +0000 (GMT)
Received: from USMA1EX-GATE1.kendall.corp.akamai.com
	(usma1ex-gate1.kendall.corp.akamai.com [172.17.0.215])
	by prod-mail-relay03.akamai.com (Postfix) with ESMTP id C8C131000088;
	Fri, 26 Sep 2008 16:22:10 +0000 (GMT)
Received: from MAVS1.kendall.corp.akamai.com ([172.17.33.15]) by
	USMA1EX-GATE1.kendall.corp.akamai.com with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 26 Sep 2008 12:22:10 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 26 Sep 2008 12:22:09 -0400
Message-ID: <5342C364A2C3A6458B15BB147FB4B724AC482F@MAVS1.kendall.corp.akamai.com>
In-Reply-To: <48DD0961.4020802@isi.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcpm] End to End Proprietary Information Field - Request for a
	new	TCP option
thread-index: Ackf8nlJOWd6Di7YQ9qHLV4H2pYSaQAAUPSg
References: <5342C364A2C3A6458B15BB147FB4B724AC479D@MAVS1.kendall.corp.akamai.com>
	<48DD0961.4020802@isi.edu>
From: "Ish Shalom, Ran" <rishshal@akamai.com>
To: "Joe Touch" <touch@ISI.EDU>
X-OriginalArrivalTime: 26 Sep 2008 16:22:10.0229 (UTC)
	FILETIME=[06BCD650:01C91FF4]
Cc: tcpm@ietf.org
Subject: Re: [tcpm] End to End Proprietary Information Field - Request for a
	new	TCP option
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

Joe,

Thank you for your comments. I certainly agree with your stand that we
should not make TCP proprietary. My proposal was not to make it
proprietary but to assign an option to allow us to communicate local
information (such as private IP addresses and local ports) end to end
despite the many gateways that may change this information in the header
fields.

Ran 

-----Original Message-----
From: Joe Touch [mailto:touch@ISI.EDU] 
Sent: Friday, September 26, 2008 12:10 PM
To: Ish Shalom, Ran
Cc: tcpm@ietf.org
Subject: Re: [tcpm] End to End Proprietary Information Field - Request
for a new TCP option

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ish,

TCP options signal changes to the TCP protocol. That protocol is not
proprietary, and I do not support making it - or any variants thereof -
proprietary.

Proprietary information about a TCP connection is already encoded in the
port number, and in-band in the application data. If the information
determines the nature of the application data, it is a port number
issue. If the information is application data, it belongs in the data
path.

I see no reason for a TCP option based on this argument, nor do I see a
reason for a proprietary TCP option either.

Additional note below...

Joe

Ish Shalom, Ran wrote:
> Increasingly businesses and their workforces are becoming more and 
> more distributed as they spread globally and move their offices to be 
> closer to their customers. At the same time, financial wisdom dictates

> strict cost control. The combination of which pushed more business to 
> use the Internet as a transport medium for remote offices and/or
employees.
> 
> IP addresses shortage, privacy and security concerns have generated a 
> myriad of solutions in the form of NATs, PATs, firewalls, etc. As a 
> result, local information such as private IP addresses, ports and 
> potentially additional local private information often gets rewritten 
> and lost when a session traverses these functions. Furthermore, some 
> gateway services might terminate sessions in order to carry them over 
> a different medium or using a different service. All of which result 
> in the same way - lost of end to end transparency. However, 
> occasionally applications and/or network administrators may need a 
> means to communicate local private IP information across the Internet 
> domain so that the far end may be able to process the session
correctly.

Any device that destroys information of a TCP connection (e.g.,
destination port of a SYN, or rewriting IP addresss) cannot be trusted
to preserve TCP options either. They often rewrite or omit such options
anyway.

> I would like to propose creating a proprietary information channel 
> using a dedicated TCP option that can be used by such application to 
> communicate private local information across the internet. A flexible 
> end-to-end private channel will allow Service Providers and 
> application vendors to provide seamless communication across the 
> Internet domain despite the many intermediate functions that are in
place today.
> 
> Sincerely,
> 
> Ran Ish-Shalom
> Akamai technologies
> 
> 
> ----------------------------------------------------------------------
> --
> 
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkjdCWEACgkQE5f5cImnZruh1wCfdUvaaEp7Zfmz0IljtN6rXLrA
zegAn31/adWJ8mpOuMDGfANcBlPmG2n0
=88Rb
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Fri Sep 26 09:31:53 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DE4F43A6B9F;
	Fri, 26 Sep 2008 09:31:53 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A8A243A6AB3
	for <tcpm@core3.amsl.com>; Fri, 26 Sep 2008 09:31:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.534
X-Spam-Level: 
X-Spam-Status: No, score=-2.534 tagged_above=-999 required=5 tests=[AWL=0.065, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6QYtmetmI8Ty for <tcpm@core3.amsl.com>;
	Fri, 26 Sep 2008 09:31:51 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id A7AED3A6B9F
	for <tcpm@ietf.org>; Fri, 26 Sep 2008 09:31:51 -0700 (PDT)
Received: from [128.9.176.35] (c1-vpn5.isi.edu [128.9.176.35])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m8QGV9Fh027266
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Fri, 26 Sep 2008 09:31:12 -0700 (PDT)
Message-ID: <48DD0E4D.2070009@isi.edu>
Date: Fri, 26 Sep 2008 09:31:09 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "Ish Shalom, Ran" <rishshal@akamai.com>
References: <5342C364A2C3A6458B15BB147FB4B724AC479D@MAVS1.kendall.corp.akamai.com>
	<48DD0961.4020802@isi.edu>
	<5342C364A2C3A6458B15BB147FB4B724AC482F@MAVS1.kendall.corp.akamai.com>
In-Reply-To: <5342C364A2C3A6458B15BB147FB4B724AC482F@MAVS1.kendall.corp.akamai.com>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tcpm@ietf.org
Subject: Re: [tcpm] End to End Proprietary Information Field - Request for a
 new	TCP option
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Ish Shalom, Ran wrote:
> Joe,
> 
> Thank you for your comments. I certainly agree with your stand that we
> should not make TCP proprietary. My proposal was not to make it
> proprietary but to assign an option to allow us to communicate local
> information (such as private IP addresses and local ports) end to end
> despite the many gateways that may change this information in the header
> fields.

Ran,

As I noted before, NAT/NAPTs already cannot be trusted to pass options
unchanged, so this doesn't solve the problem.

It's already possible to exchange that information using a tunnel, which
does not require a change to the protocol. Use of a tunnel requires mods
to both ends of the protocol, but then so does use of this sort of option.

Further, a tunnel allows use of TCP authentication (TCP MD5, TCP-AO) to
verify that the addr/port values have not changed, or even the use of
IPsec (depending on the layer of the tunneling).

Joe

> 
> Ran 
> 
> -----Original Message-----
> From: Joe Touch [mailto:touch@ISI.EDU] 
> Sent: Friday, September 26, 2008 12:10 PM
> To: Ish Shalom, Ran
> Cc: tcpm@ietf.org
> Subject: Re: [tcpm] End to End Proprietary Information Field - Request
> for a new TCP option
> 
> Ish,
> 
> TCP options signal changes to the TCP protocol. That protocol is not
> proprietary, and I do not support making it - or any variants thereof -
> proprietary.
> 
> Proprietary information about a TCP connection is already encoded in the
> port number, and in-band in the application data. If the information
> determines the nature of the application data, it is a port number
> issue. If the information is application data, it belongs in the data
> path.
> 
> I see no reason for a TCP option based on this argument, nor do I see a
> reason for a proprietary TCP option either.
> 
> Additional note below...
> 
> Joe
> 
> Ish Shalom, Ran wrote:
>> Increasingly businesses and their workforces are becoming more and 
>> more distributed as they spread globally and move their offices to be 
>> closer to their customers. At the same time, financial wisdom dictates
> 
>> strict cost control. The combination of which pushed more business to 
>> use the Internet as a transport medium for remote offices and/or
> employees.
>> IP addresses shortage, privacy and security concerns have generated a 
>> myriad of solutions in the form of NATs, PATs, firewalls, etc. As a 
>> result, local information such as private IP addresses, ports and 
>> potentially additional local private information often gets rewritten 
>> and lost when a session traverses these functions. Furthermore, some 
>> gateway services might terminate sessions in order to carry them over 
>> a different medium or using a different service. All of which result 
>> in the same way - lost of end to end transparency. However, 
>> occasionally applications and/or network administrators may need a 
>> means to communicate local private IP information across the Internet 
>> domain so that the far end may be able to process the session
> correctly.
> 
> Any device that destroys information of a TCP connection (e.g.,
> destination port of a SYN, or rewriting IP addresss) cannot be trusted
> to preserve TCP options either. They often rewrite or omit such options
> anyway.
> 
>> I would like to propose creating a proprietary information channel 
>> using a dedicated TCP option that can be used by such application to 
>> communicate private local information across the internet. A flexible 
>> end-to-end private channel will allow Service Providers and 
>> application vendors to provide seamless communication across the 
>> Internet domain despite the many intermediate functions that are in
> place today.
>> Sincerely,
> 
>> Ran Ish-Shalom
>> Akamai technologies
> 
> 
>> ----------------------------------------------------------------------
>> --
> 
>> _______________________________________________
>> tcpm mailing list
>> tcpm@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcpm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkjdDk0ACgkQE5f5cImnZruNnQCfefutXF1ciE7W4IOlRLTXppOZ
RbgAoJOnhfNdGHcaaYMWIDkHIWUWyO32
=o0Rw
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Fri Sep 26 09:34:33 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 85D7D3A6B14;
	Fri, 26 Sep 2008 09:34:33 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3EC0C3A6B14
	for <tcpm@core3.amsl.com>; Fri, 26 Sep 2008 09:34:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.567
X-Spam-Level: 
X-Spam-Status: No, score=-2.567 tagged_above=-999 required=5 tests=[AWL=0.033, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id x3nU4Bnlj74B for <tcpm@core3.amsl.com>;
	Fri, 26 Sep 2008 09:34:31 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id 292A03A6B6A
	for <tcpm@ietf.org>; Fri, 26 Sep 2008 09:34:31 -0700 (PDT)
Received: from [128.9.176.35] (c1-vpn5.isi.edu [128.9.176.35])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m8QGXbu4028452
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Fri, 26 Sep 2008 09:33:40 -0700 (PDT)
Message-ID: <48DD0EE0.9000207@isi.edu>
Date: Fri, 26 Sep 2008 09:33:36 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Joe Touch <touch@ISI.EDU>
References: <5342C364A2C3A6458B15BB147FB4B724AC479D@MAVS1.kendall.corp.akamai.com>
	<48DD0961.4020802@isi.edu>
	<5342C364A2C3A6458B15BB147FB4B724AC482F@MAVS1.kendall.corp.akamai.com>
	<48DD0E4D.2070009@isi.edu>
In-Reply-To: <48DD0E4D.2070009@isi.edu>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tcpm@ietf.org
Subject: Re: [tcpm] End to End Proprietary Information Field - Request for a
 new	TCP option
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Joe Touch wrote:
> 
> 
> Ish Shalom, Ran wrote:
>> Joe,
> 
>> Thank you for your comments. I certainly agree with your stand that we
>> should not make TCP proprietary. My proposal was not to make it
>> proprietary but to assign an option to allow us to communicate local
>> information (such as private IP addresses and local ports) end to end
>> despite the many gateways that may change this information in the header
>> fields.
> 
> Ran,
> 
> As I noted before, NAT/NAPTs already cannot be trusted to pass options
> unchanged, so this doesn't solve the problem.
> 
> It's already possible to exchange that information using a tunnel, which
> does not require a change to the protocol. Use of a tunnel requires mods
> to both ends of the protocol, but then so does use of this sort of option.

(both ends of the connection; TCP, as noted, isn't modified)

> Further, a tunnel allows use of TCP authentication (TCP MD5, TCP-AO) to
> verify that the addr/port values have not changed, or even the use of
> IPsec (depending on the layer of the tunneling).
> 
> Joe
> 
>> Ran 
> 
>> -----Original Message-----
>> From: Joe Touch [mailto:touch@ISI.EDU] 
>> Sent: Friday, September 26, 2008 12:10 PM
>> To: Ish Shalom, Ran
>> Cc: tcpm@ietf.org
>> Subject: Re: [tcpm] End to End Proprietary Information Field - Request
>> for a new TCP option
> 
>> Ish,
> 
>> TCP options signal changes to the TCP protocol. That protocol is not
>> proprietary, and I do not support making it - or any variants thereof -
>> proprietary.
> 
>> Proprietary information about a TCP connection is already encoded in the
>> port number, and in-band in the application data. If the information
>> determines the nature of the application data, it is a port number
>> issue. If the information is application data, it belongs in the data
>> path.
> 
>> I see no reason for a TCP option based on this argument, nor do I see a
>> reason for a proprietary TCP option either.
> 
>> Additional note below...
> 
>> Joe
> 
>> Ish Shalom, Ran wrote:
>>> Increasingly businesses and their workforces are becoming more and 
>>> more distributed as they spread globally and move their offices to be 
>>> closer to their customers. At the same time, financial wisdom dictates
>>> strict cost control. The combination of which pushed more business to 
>>> use the Internet as a transport medium for remote offices and/or
>> employees.
>>> IP addresses shortage, privacy and security concerns have generated a 
>>> myriad of solutions in the form of NATs, PATs, firewalls, etc. As a 
>>> result, local information such as private IP addresses, ports and 
>>> potentially additional local private information often gets rewritten 
>>> and lost when a session traverses these functions. Furthermore, some 
>>> gateway services might terminate sessions in order to carry them over 
>>> a different medium or using a different service. All of which result 
>>> in the same way - lost of end to end transparency. However, 
>>> occasionally applications and/or network administrators may need a 
>>> means to communicate local private IP information across the Internet 
>>> domain so that the far end may be able to process the session
>> correctly.
> 
>> Any device that destroys information of a TCP connection (e.g.,
>> destination port of a SYN, or rewriting IP addresss) cannot be trusted
>> to preserve TCP options either. They often rewrite or omit such options
>> anyway.
> 
>>> I would like to propose creating a proprietary information channel 
>>> using a dedicated TCP option that can be used by such application to 
>>> communicate private local information across the internet. A flexible 
>>> end-to-end private channel will allow Service Providers and 
>>> application vendors to provide seamless communication across the 
>>> Internet domain despite the many intermediate functions that are in
>> place today.
>>> Sincerely,
>>> Ran Ish-Shalom
>>> Akamai technologies
> 
>>> ----------------------------------------------------------------------
>>> --
>>> _______________________________________________
>>> tcpm mailing list
>>> tcpm@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tcpm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkjdDuAACgkQE5f5cImnZrtDOwCdHzgmKZF4EG/HDYuacxNA5s6x
X5gAoMySfW3hWkvg3y3vpFNGsRD4klcG
=n4ho
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Fri Sep 26 09:39:19 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 82CDC3A6B8D;
	Fri, 26 Sep 2008 09:39:19 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C88AB3A6B8B
	for <tcpm@core3.amsl.com>; Fri, 26 Sep 2008 09:39:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.151
X-Spam-Level: 
X-Spam-Status: No, score=-2.151 tagged_above=-999 required=5 tests=[AWL=0.448, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id fesYp09H9hCf for <tcpm@core3.amsl.com>;
	Fri, 26 Sep 2008 09:39:16 -0700 (PDT)
Received: from prod-mail-xrelay01.akamai.com (prod-mail-xrelay01.akamai.com
	[72.246.2.12]) by core3.amsl.com (Postfix) with ESMTP id 5E4C13A6B86
	for <tcpm@ietf.org>; Fri, 26 Sep 2008 09:39:16 -0700 (PDT)
Received: from prod-mail-xrelay01.akamai.com (localhost [127.0.0.1])
	by postfix.imss70 (Postfix) with ESMTP id 45A4CC00039C;
	Fri, 26 Sep 2008 16:39:27 +0000 (GMT)
Received: from prod-mail-relay02.akamai.com (unknown [172.17.50.21])
	by prod-mail-xrelay01.akamai.com (Postfix) with ESMTP id 36AF6C00039B; 
	Fri, 26 Sep 2008 16:39:27 +0000 (UTC)
Received: from USMA1EX-GATE1.kendall.corp.akamai.com
	(usma1ex-gate1.kendall.corp.akamai.com [172.17.0.215])
	by prod-mail-relay02.akamai.com (Postfix) with ESMTP id 303D9100008C;
	Fri, 26 Sep 2008 16:39:27 +0000 (GMT)
Received: from MAVS1.kendall.corp.akamai.com ([172.17.33.15]) by
	USMA1EX-GATE1.kendall.corp.akamai.com with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 26 Sep 2008 12:39:26 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 26 Sep 2008 12:39:26 -0400
Message-ID: <5342C364A2C3A6458B15BB147FB4B724AC4868@MAVS1.kendall.corp.akamai.com>
In-Reply-To: <48DD0E4D.2070009@isi.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcpm] End to End Proprietary Information Field - Request for a
	new	TCP option
thread-index: Ackf9WGdHus7ifGyRjSg1h6M470bpAAAEcMg
References: <5342C364A2C3A6458B15BB147FB4B724AC479D@MAVS1.kendall.corp.akamai.com>
	<48DD0961.4020802@isi.edu>
	<5342C364A2C3A6458B15BB147FB4B724AC482F@MAVS1.kendall.corp.akamai.com>
	<48DD0E4D.2070009@isi.edu>
From: "Ish Shalom, Ran" <rishshal@akamai.com>
To: "Joe Touch" <touch@ISI.EDU>
X-OriginalArrivalTime: 26 Sep 2008 16:39:26.0983 (UTC)
	FILETIME=[70B0F170:01C91FF6]
Cc: tcpm@ietf.org
Subject: Re: [tcpm] End to End Proprietary Information Field - Request for a
	new	TCP option
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

Joe,

I agree and it was my oversight for not discussing it explicitly. A
tunnel is certainly an option to transmit such information (with
sometimes the added benefits of authentication). The main downside to
implementing it is its cost. Tunnels (at any layer) are sometimes very
expensive in terms of processing and delay. Having a TCP option may help
us avoid taking this hit. 

As for NAT devices still destroying TCP header information, I agree that
needs to be discussed and solved. The way I see it is that once we have
a formally assigned TCP option with a clear definition of what it is
used for and how to treat it, we can then work with NAT vendors to make
sure that this specific TCP option will not be changed. There are some
security concerns with it but there is also a benefit to communicating
this info.

Ran 

-----Original Message-----
From: Joe Touch [mailto:touch@ISI.EDU] 
Sent: Friday, September 26, 2008 12:31 PM
To: Ish Shalom, Ran
Cc: tcpm@ietf.org
Subject: Re: [tcpm] End to End Proprietary Information Field - Request
for a new TCP option

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Ish Shalom, Ran wrote:
> Joe,
> 
> Thank you for your comments. I certainly agree with your stand that we

> should not make TCP proprietary. My proposal was not to make it 
> proprietary but to assign an option to allow us to communicate local 
> information (such as private IP addresses and local ports) end to end 
> despite the many gateways that may change this information in the 
> header fields.

Ran,

As I noted before, NAT/NAPTs already cannot be trusted to pass options
unchanged, so this doesn't solve the problem.

It's already possible to exchange that information using a tunnel, which
does not require a change to the protocol. Use of a tunnel requires mods
to both ends of the protocol, but then so does use of this sort of
option.

Further, a tunnel allows use of TCP authentication (TCP MD5, TCP-AO) to
verify that the addr/port values have not changed, or even the use of
IPsec (depending on the layer of the tunneling).

Joe

> 
> Ran
> 
> -----Original Message-----
> From: Joe Touch [mailto:touch@ISI.EDU]
> Sent: Friday, September 26, 2008 12:10 PM
> To: Ish Shalom, Ran
> Cc: tcpm@ietf.org
> Subject: Re: [tcpm] End to End Proprietary Information Field - Request

> for a new TCP option
> 
> Ish,
> 
> TCP options signal changes to the TCP protocol. That protocol is not 
> proprietary, and I do not support making it - or any variants thereof 
> - proprietary.
> 
> Proprietary information about a TCP connection is already encoded in 
> the port number, and in-band in the application data. If the 
> information determines the nature of the application data, it is a 
> port number issue. If the information is application data, it belongs 
> in the data path.
> 
> I see no reason for a TCP option based on this argument, nor do I see 
> a reason for a proprietary TCP option either.
> 
> Additional note below...
> 
> Joe
> 
> Ish Shalom, Ran wrote:
>> Increasingly businesses and their workforces are becoming more and 
>> more distributed as they spread globally and move their offices to be

>> closer to their customers. At the same time, financial wisdom 
>> dictates
> 
>> strict cost control. The combination of which pushed more business to

>> use the Internet as a transport medium for remote offices and/or
> employees.
>> IP addresses shortage, privacy and security concerns have generated a

>> myriad of solutions in the form of NATs, PATs, firewalls, etc. As a 
>> result, local information such as private IP addresses, ports and 
>> potentially additional local private information often gets rewritten

>> and lost when a session traverses these functions. Furthermore, some 
>> gateway services might terminate sessions in order to carry them over

>> a different medium or using a different service. All of which result 
>> in the same way - lost of end to end transparency. However, 
>> occasionally applications and/or network administrators may need a 
>> means to communicate local private IP information across the Internet

>> domain so that the far end may be able to process the session
> correctly.
> 
> Any device that destroys information of a TCP connection (e.g., 
> destination port of a SYN, or rewriting IP addresss) cannot be trusted

> to preserve TCP options either. They often rewrite or omit such 
> options anyway.
> 
>> I would like to propose creating a proprietary information channel 
>> using a dedicated TCP option that can be used by such application to 
>> communicate private local information across the internet. A flexible

>> end-to-end private channel will allow Service Providers and 
>> application vendors to provide seamless communication across the 
>> Internet domain despite the many intermediate functions that are in
> place today.
>> Sincerely,
> 
>> Ran Ish-Shalom
>> Akamai technologies
> 
> 
>> ---------------------------------------------------------------------
>> -
>> --
> 
>> _______________________________________________
>> tcpm mailing list
>> tcpm@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcpm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkjdDk0ACgkQE5f5cImnZruNnQCfefutXF1ciE7W4IOlRLTXppOZ
RbgAoJOnhfNdGHcaaYMWIDkHIWUWyO32
=o0Rw
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Fri Sep 26 09:52:14 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 947BB28C19D;
	Fri, 26 Sep 2008 09:52:14 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BC1183A6B96
	for <tcpm@core3.amsl.com>; Fri, 26 Sep 2008 09:52:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.577
X-Spam-Level: 
X-Spam-Status: No, score=-2.577 tagged_above=-999 required=5 tests=[AWL=0.022, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id SzQd1t8hlJbW for <tcpm@core3.amsl.com>;
	Fri, 26 Sep 2008 09:52:12 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id 91D8E3A6B9A
	for <tcpm@ietf.org>; Fri, 26 Sep 2008 09:52:12 -0700 (PDT)
Received: from [128.9.176.35] (c1-vpn5.isi.edu [128.9.176.35])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m8QGp9bX004097
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Fri, 26 Sep 2008 09:51:11 -0700 (PDT)
Message-ID: <48DD12FC.30907@isi.edu>
Date: Fri, 26 Sep 2008 09:51:08 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "Ish Shalom, Ran" <rishshal@akamai.com>
References: <5342C364A2C3A6458B15BB147FB4B724AC479D@MAVS1.kendall.corp.akamai.com>
	<48DD0961.4020802@isi.edu>
	<5342C364A2C3A6458B15BB147FB4B724AC482F@MAVS1.kendall.corp.akamai.com>
	<48DD0E4D.2070009@isi.edu>
	<5342C364A2C3A6458B15BB147FB4B724AC4868@MAVS1.kendall.corp.akamai.com>
In-Reply-To: <5342C364A2C3A6458B15BB147FB4B724AC4868@MAVS1.kendall.corp.akamai.com>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tcpm@ietf.org
Subject: Re: [tcpm] End to End Proprietary Information Field - Request for a
 new	TCP option
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ran,

Ish Shalom, Ran wrote:
> Joe,
> 
> I agree and it was my oversight for not discussing it explicitly. A
> tunnel is certainly an option to transmit such information (with
> sometimes the added benefits of authentication). The main downside to
> implementing it is its cost. Tunnels (at any layer) are sometimes very
> expensive in terms of processing and delay. Having a TCP option may help
> us avoid taking this hit. 

That's an implementation issue, and largely impacts throughput and
processing (not latency). I don't think we should modify a core Internet
protocol to overcome the inefficiencies of some implementations.

> As for NAT devices still destroying TCP header information, I agree that
> needs to be discussed and solved. The way I see it is that once we have
> a formally assigned TCP option with a clear definition of what it is
> used for and how to treat it, we can then work with NAT vendors to make
> sure that this specific TCP option will not be changed. 

Cooperative NATs don't want to destroy the destination IP address or
port - which define the packet path and service.

Non-cooperative NATs, that destroy destination IP addresses or ports,
are no more likely to preserve this option than they were to preserve
the destination IP address and port.

It seems that there is only one reason for this sort of option - to
preserve the source IP address and source port. It's not clear why this
information is useful, however - e.g., the source address behind the NAT
could have been private and thus meaningless, and the source port is
useful only for demuxing anyway.

> There are some
> security concerns with it but there is also a benefit to communicating
> this info.

Given the above, can you explain further? I.e., what is the benefit to
knowing the source IP and source port?

Joe

> -----Original Message-----
> From: Joe Touch [mailto:touch@ISI.EDU] 
> Sent: Friday, September 26, 2008 12:31 PM
> To: Ish Shalom, Ran
> Cc: tcpm@ietf.org
> Subject: Re: [tcpm] End to End Proprietary Information Field - Request
> for a new TCP option
> 
> 
> 
> Ish Shalom, Ran wrote:
>> Joe,
> 
>> Thank you for your comments. I certainly agree with your stand that we
> 
>> should not make TCP proprietary. My proposal was not to make it 
>> proprietary but to assign an option to allow us to communicate local 
>> information (such as private IP addresses and local ports) end to end 
>> despite the many gateways that may change this information in the 
>> header fields.
> 
> Ran,
> 
> As I noted before, NAT/NAPTs already cannot be trusted to pass options
> unchanged, so this doesn't solve the problem.
> 
> It's already possible to exchange that information using a tunnel, which
> does not require a change to the protocol. Use of a tunnel requires mods
> to both ends of the protocol, but then so does use of this sort of
> option.
> 
> Further, a tunnel allows use of TCP authentication (TCP MD5, TCP-AO) to
> verify that the addr/port values have not changed, or even the use of
> IPsec (depending on the layer of the tunneling).
> 
> Joe
> 
>> Ran
> 
>> -----Original Message-----
>> From: Joe Touch [mailto:touch@ISI.EDU]
>> Sent: Friday, September 26, 2008 12:10 PM
>> To: Ish Shalom, Ran
>> Cc: tcpm@ietf.org
>> Subject: Re: [tcpm] End to End Proprietary Information Field - Request
> 
>> for a new TCP option
> 
>> Ish,
> 
>> TCP options signal changes to the TCP protocol. That protocol is not 
>> proprietary, and I do not support making it - or any variants thereof 
>> - proprietary.
> 
>> Proprietary information about a TCP connection is already encoded in 
>> the port number, and in-band in the application data. If the 
>> information determines the nature of the application data, it is a 
>> port number issue. If the information is application data, it belongs 
>> in the data path.
> 
>> I see no reason for a TCP option based on this argument, nor do I see 
>> a reason for a proprietary TCP option either.
> 
>> Additional note below...
> 
>> Joe
> 
>> Ish Shalom, Ran wrote:
>>> Increasingly businesses and their workforces are becoming more and 
>>> more distributed as they spread globally and move their offices to be
> 
>>> closer to their customers. At the same time, financial wisdom 
>>> dictates
>>> strict cost control. The combination of which pushed more business to
> 
>>> use the Internet as a transport medium for remote offices and/or
>> employees.
>>> IP addresses shortage, privacy and security concerns have generated a
> 
>>> myriad of solutions in the form of NATs, PATs, firewalls, etc. As a 
>>> result, local information such as private IP addresses, ports and 
>>> potentially additional local private information often gets rewritten
> 
>>> and lost when a session traverses these functions. Furthermore, some 
>>> gateway services might terminate sessions in order to carry them over
> 
>>> a different medium or using a different service. All of which result 
>>> in the same way - lost of end to end transparency. However, 
>>> occasionally applications and/or network administrators may need a 
>>> means to communicate local private IP information across the Internet
> 
>>> domain so that the far end may be able to process the session
>> correctly.
> 
>> Any device that destroys information of a TCP connection (e.g., 
>> destination port of a SYN, or rewriting IP addresss) cannot be trusted
> 
>> to preserve TCP options either. They often rewrite or omit such 
>> options anyway.
> 
>>> I would like to propose creating a proprietary information channel 
>>> using a dedicated TCP option that can be used by such application to 
>>> communicate private local information across the internet. A flexible
> 
>>> end-to-end private channel will allow Service Providers and 
>>> application vendors to provide seamless communication across the 
>>> Internet domain despite the many intermediate functions that are in
>> place today.
>>> Sincerely,
>>> Ran Ish-Shalom
>>> Akamai technologies
> 
>>> ---------------------------------------------------------------------
>>> -
>>> --
>>> _______________________________________________
>>> tcpm mailing list
>>> tcpm@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tcpm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkjdEvwACgkQE5f5cImnZru60QCgmt/acdHsTxdWTy9oW5luA7jo
dOIAoKAJY1Sran1qwqzZvyG95VInHZl/
=jwMA
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Fri Sep 26 12:40:01 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 60FF93A68A6;
	Fri, 26 Sep 2008 12:40:01 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D00973A68A6
	for <tcpm@core3.amsl.com>; Fri, 26 Sep 2008 12:39:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.349
X-Spam-Level: 
X-Spam-Status: No, score=-3.349 tagged_above=-999 required=5 tests=[AWL=0.250, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ummcCuvpErKb for <tcpm@core3.amsl.com>;
	Fri, 26 Sep 2008 12:39:59 -0700 (PDT)
Received: from mail.wrs.com (mail.windriver.com [147.11.1.11])
	by core3.amsl.com (Postfix) with ESMTP id 152D93A686B
	for <tcpm@ietf.org>; Fri, 26 Sep 2008 12:39:59 -0700 (PDT)
Received: from ALA-MAIL03.corp.ad.wrs.com (ala-mail03 [147.11.57.144])
	by mail.wrs.com (8.13.6/8.13.6) with ESMTP id m8QJbssO004421;
	Fri, 26 Sep 2008 12:37:55 -0700 (PDT)
Received: from ala-mail06.corp.ad.wrs.com ([147.11.57.147]) by
	ALA-MAIL03.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 26 Sep 2008 12:37:54 -0700
Received: from dab-restive.wrs.com ([192.168.117.73]) by
	ala-mail06.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 26 Sep 2008 12:37:54 -0700
Message-Id: <53797EED-2C93-4E20-AF60-E3C0EF8F85AC@windriver.com>
From: David Borman <david.borman@windriver.com>
To: tcpm@ietf.org
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 26 Sep 2008 14:37:52 -0500
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 26 Sep 2008 19:37:54.0625 (UTC)
	FILETIME=[5EF17310:01C9200F]
Cc: "Anantha Ramaiah \(ananth\)" <ananth@cisco.com>,
	mbashyam@ocarinanetworks.com
Subject: [tcpm] draft-ananth-tcpm-persist-00.txt as a WG document
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

At Dublin a presentation was made on draft-ananth-tcpm- 
persist-00.txt.  Not a lot of people had read the document at the time  
of the presentation, but there didn't seem to be any objections to  
adopting it as a TCPM WG document.

The authors posted a summary to the mailing list, have responded to  
all issues that were raised, and have a new version of the document  
ready for publication.  We (Wes and I) feel that there is support for  
adopting this as a WG document, but as always, we need to verify this  
on the mailing list.  So, if you have any objections to adopting this  
as a WG document, please speak up now.  Also speak up if you support  
adopting it as a WG document.

I'll be the first to say I support adopting this as a WG document.  If  
there are no serious objections, the authors can submit their updated  
version next week and Wes and I will add it to our list of WG documents.

			-David Borman, TCPM WG co-chair

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Fri Sep 26 15:32:57 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 119353A6A86;
	Fri, 26 Sep 2008 15:32:57 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 295BE3A68DD
	for <tcpm@core3.amsl.com>; Fri, 26 Sep 2008 15:32:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.586
X-Spam-Level: 
X-Spam-Status: No, score=-2.586 tagged_above=-999 required=5 tests=[AWL=0.013, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id JxAVwagq49Yt for <tcpm@core3.amsl.com>;
	Fri, 26 Sep 2008 15:32:55 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id 16EB03A6A86
	for <tcpm@ietf.org>; Fri, 26 Sep 2008 15:32:55 -0700 (PDT)
Received: from [128.9.176.49] (c1-vpn10.isi.edu [128.9.176.49])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m8QMWO3g021402
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Fri, 26 Sep 2008 15:32:26 -0700 (PDT)
Message-ID: <48DD62F8.3080708@isi.edu>
Date: Fri, 26 Sep 2008 15:32:24 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: David Borman <david.borman@windriver.com>
References: <53797EED-2C93-4E20-AF60-E3C0EF8F85AC@windriver.com>
In-Reply-To: <53797EED-2C93-4E20-AF60-E3C0EF8F85AC@windriver.com>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tcpm@ietf.org, "Anantha Ramaiah \(ananth\)" <ananth@cisco.com>,
	mbashyam@ocarinanetworks.com
Subject: Re: [tcpm] draft-ananth-tcpm-persist-00.txt as a WG document
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dave,

I'm not sure any of us disagreed with the content. The question is
whether it's important, useful, or necessary (in that order) to address
this, or whether we feel that the existing specs are sufficient.

My conclusion was that applications can always terminate TCP
connections, and so can OS's - e.g., an OS can always just reboot.

This still sounds like an implementation guideline to me. It may be
useful, and may be useful to document, but since it's implementation
focused, I'm not sure I see it as a protocol document.

As a result, I don't think this needs to be a WG document (which is
where I thought things were from Dublin). We talked there about it
potentially being an errata to 1122, and even the problems with that
approach.

Finally, it is not clear this is even in scope - it's not a modification
to TCP, nor is it maintenance.

Joe

David Borman wrote:
> At Dublin a presentation was made on draft-ananth-tcpm-persist-00.txt. 
> Not a lot of people had read the document at the time of the
> presentation, but there didn't seem to be any objections to adopting it
> as a TCPM WG document.
> 
> The authors posted a summary to the mailing list, have responded to all
> issues that were raised, and have a new version of the document ready
> for publication.  We (Wes and I) feel that there is support for adopting
> this as a WG document, but as always, we need to verify this on the
> mailing list.  So, if you have any objections to adopting this as a WG
> document, please speak up now.  Also speak up if you support adopting it
> as a WG document.
> 
> I'll be the first to say I support adopting this as a WG document.  If
> there are no serious objections, the authors can submit their updated
> version next week and Wes and I will add it to our list of WG documents.
> 
>             -David Borman, TCPM WG co-chair
> 
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkjdYvgACgkQE5f5cImnZrsMrACfTV5Bl9beeAJ29JDszVT6sVhY
XQAAoN8VPIAizeB1Z+IgkD/6iwT1h+HP
=jSx6
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Sat Sep 27 09:29:31 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 06E903A685E;
	Sat, 27 Sep 2008 09:29:31 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1CD483A69EB
	for <tcpm@core3.amsl.com>; Sat, 27 Sep 2008 09:29:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.969
X-Spam-Level: *
X-Spam-Status: No, score=1.969 tagged_above=-999 required=5
	tests=[BAYES_40=-0.185, DATE_IN_PAST_12_24=0.992,
	FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RCVD_IN_DNSWL_LOW=-1,
	RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id udVKYfoCPCp1 for <tcpm@core3.amsl.com>;
	Sat, 27 Sep 2008 09:29:27 -0700 (PDT)
Received: from smtp1.xmundo.net (unknown [201.216.232.80])
	by core3.amsl.com (Postfix) with ESMTP id 9DB173A685E
	for <tcpm@ietf.org>; Sat, 27 Sep 2008 09:29:26 -0700 (PDT)
Received: from venus.xmundo.net (venus.xmundo.net [201.216.232.56])
	by smtp1.xmundo.net (Postfix) with ESMTP id 083CB6B6581;
	Sat, 27 Sep 2008 13:29:05 -0300 (ART)
Received: from notebook.gont.com.ar (dsl-189-145-119-98.prod-infinitum.com.mx
	[189.145.119.98] (may be forged)) (authenticated bits=0)
	by venus.xmundo.net (8.14.1/8.13.8) with ESMTP id m8RGSmDg003914;
	Sat, 27 Sep 2008 13:28:50 -0300
Message-Id: <200809271628.m8RGSmDg003914@venus.xmundo.net>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 26 Sep 2008 15:48:47 -0300
To: "Ish Shalom, Ran" <rishshal@akamai.com>, "Joe Touch" <touch@ISI.EDU>
From: Fernando Gont <fernando@gont.com.ar>
In-Reply-To: <5342C364A2C3A6458B15BB147FB4B724AC482F@MAVS1.kendall.corp.
	akamai.com>
References: <5342C364A2C3A6458B15BB147FB4B724AC479D@MAVS1.kendall.corp.akamai.com>
	<48DD0961.4020802@isi.edu>
	<5342C364A2C3A6458B15BB147FB4B724AC482F@MAVS1.kendall.corp.akamai.com>
Mime-Version: 1.0
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by
	milter-greylist-3.0 (venus.xmundo.net [201.216.232.56]);
	Sat, 27 Sep 2008 13:29:03 -0300 (ART)
Cc: tcpm@ietf.org
Subject: Re: [tcpm] End to End Proprietary Information Field - Request for a
 new	TCP option
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

At 01:22 p.m. 26/09/2008, Ish Shalom, Ran wrote:

>Thank you for your comments. I certainly agree with your stand that we
>should not make TCP proprietary. My proposal was not to make it
>proprietary but to assign an option to allow us to communicate local
>information (such as private IP addresses and local ports) end to end
>despite the many gateways that may change this information in the header
>fields.

A TCP option is still a header field, and packet scrubbers may simply 
remove that option.

That said, it doesn't look like clean design the approach you are 
describing (stuffing IP addresses in TCP, or applications dealing 
with IP addresses in the first place).

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




_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Sun Sep 28 14:04:38 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5F23E3A6957;
	Sun, 28 Sep 2008 14:04:38 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3F2F63A6957
	for <tcpm@core3.amsl.com>; Sun, 28 Sep 2008 14:04:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.999
X-Spam-Level: 
X-Spam-Status: No, score=-3.999 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id IadFVzRUJ5aw for <tcpm@core3.amsl.com>;
	Sun, 28 Sep 2008 14:04:35 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id D27CD3A6950
	for <tcpm@ietf.org>; Sun, 28 Sep 2008 14:04:35 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,327,1220227200"; d="scan'208";a="164578401"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 28 Sep 2008 21:04:53 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m8SL4qE9021880; 
	Sun, 28 Sep 2008 14:04:52 -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.13.8/8.13.8) with ESMTP id m8SL4qqn025397;
	Sun, 28 Sep 2008 21:04:52 GMT
Received: from xmb-sjc-21c.amer.cisco.com ([171.70.151.176]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 28 Sep 2008 14:04:52 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 28 Sep 2008 14:03:55 -0700
Message-ID: <0C53DCFB700D144284A584F54711EC5805DF4359@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <20080906013831.GD2074@zod.isi.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
Thread-Index: AckPxNDHT/KHDJV6Rk6HqbPQTpAjDQAwyaoQ
References: <FE34F27F-8DDF-4C94-BC6E-E2ABF6000309@windriver.com>
	<B5A5E01F9387F4409E67604C0257C71E409513@NDJSEVS25A.ndc.nasa.gov>
	<24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>
	<20080906013831.GD2074@zod.isi.edu>
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: "Ted Faber" <faber@ISI.EDU>, "David Borman" <david.borman@windriver.com>
X-OriginalArrivalTime: 28 Sep 2008 21:04:52.0858 (UTC)
	FILETIME=[DA141DA0:01C921AD]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=9431; t=1222635892;
	x=1223499892; c=relaxed/simple; s=sjdkim4002;
	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[tcpm]=20WGLC=3A=20draft-ietf-tcpm-tcps
	ecure-10.txt |Sender:=20;
	bh=9x2K6ZTk+6zU9r5Re6iaxleCnE3Sao4ILSqXh8SSCaE=;
	b=emu898c3vMHZcIaeoWuN+yUkUTgSx3eXHuSDxB/7IMunMilHrDXxKN2wx1
	WygHzb9LBkpvmrjxsk/Hh5hLR1o71uK2vk0T7Ehklthn78AQ/Qh7mfQ+yulc
	G62Tywh/jq;
Authentication-Results: sj-dkim-4; header.From=ananth@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: rrs@cisco.com, tcpm@ietf.org, "Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org


Ted,
  Appreciate the detailed comments. Pl see inline responses.


> -----Original Message-----
> From: Ted Faber [mailto:faber@ISI.EDU] 
> Sent: Friday, September 05, 2008 6:39 PM
> To: David Borman
> Cc: tcpm@ietf.org; rrs@cisco.com; Mitesh Dalal (mdalal); 
> Anantha Ramaiah (ananth)
> Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
> 
> On Thu, Aug 21, 2008 at 12:40:43PM -0500, David Borman wrote:
> > 
> > Wes and I would like to start the WG Last Call for:
> > 
> >  Title           : Improving TCP's Robustness to Blind In-Window  
> > Attacks'
> >  Author(s)       : A. Ramaiah, R. Stewart & M. Dalal
> >  Filename        : draft-ietf-tcpm-tcpsecure-10.txt
> >  Pages           : 27
> >  Date            : July 9, 2008
> >  Intended Status : Proposed Standard
> > 
> > http://www.ietf.org/internet-drafts/draft-ietf-tcpm-tcpsecure-10.txt
> > 
> > It is our understanding that all the feedback has been incorporated 
> > into this latest version and that there are no known outstanding 
> > issues with this document.
> > 
> > Please send feedback to the list, even if it is just a 
> "yes, go ahead 
> > and publish".
> > 
> > The WGLC will end on Friday, September 5, 2009.
> 
> Overall I think this is a good draft and should advance.  I 
> have comments, which I'll present in page order:
> 
> Probably the most technical comment I have is the objection 
> to the "There was no sound technical reasoning for choosing 
> the Data mitigation as MAY", which is on P15.
> 
> P2:
> The 4-tuple is called a socket pair in 793.  Even if you 
> don't want to adopt that terminology, it's probably worth 
> mentioning.  I also don't like "RST, SYN or DATA segment."  
> These are TCP segments with the RST or SYN flag set and I'd 
> describe them that way.  ONce you've had a chance to define 
> "RST segment" as a segment with the RST bit set, you can use 
> the short form.

Good point. Will do.

> 
> I'd delete "either" from "This can cause the connection to 
> either abort or possibly cause data corruption."  I'd 
> consider deleting "possibly" as well.

Makes sense. Will do.

> 
> P4:
> 
> "The TCP spoofing attacks, which are seen in the Internet 
> today," - I'd say "The off-path TCP spoofing attacks".  We're 
> still describing the problem, so let's be clear.  The next 
> paragraph starts with a description of the attacks this draft 
> cares about, but until then be precise.
> 
> "... making the odds of guessing correctly the 4-tuple..."  I 
> think "correctly guessing" is more common.  I'd actually 
> suggest "... making it much easier to guess the 4-tuple."

Ok. 

> 
> P5:
> 
> "One of the important things to note is that, for the attack 
> to succeed the RST..." -> delete the comma.
> 
> "A slight enhancement to the TCP's segment processing" -> 
> delete the "the".

Both points taken.

> 
> P6:
> 
> "Every application has control of a number of factors that 
> effect drastically the probability of a successful spoofing 
> attack."  You mean "affect" not "effect".  I'd also use 
> "drastically affect" rather than "affect drastically".  The 
> order of the adverb is a matter of style, using "affect" 
> changes the meaning of the sentence to the one you intend.

Cool. Will do.

> 
> On the figures in the "To successfully inject a spoofed packet..."
> paragraph:
> 
> 1. Use parens, not [].
> 2. Finish the math.  If you want to say 1/2 * 2^32 = 2^31 
> rather than just dropping 2^31 that's fine, but we're going 
> to be comparing these requirements, so don't hide the 
> results.  "[SITW] shows that the mean number of tries needed 
> to inject a RST command is (2^31/window) rather than the 2^31 
> assumed before."

Ok.

> 
> 
> P7:
> 
> "...please refer to draft [RFC4953]" -> "please refer to [RFC4953]"
> It's not a draft any more.

Ok.

> 
> P8:
> 
> Why use 1) and 2) and A), B), C)?  Pick one.
> 
> "The previous text, quoted from [RFC0793], woould thus 
> become:" -> That sounds a lot like we're mandating the change 
> rather than it being a SHOULD.  Do we really need this 
> restatement at all?

Hmm.. I thought it was more clearer that way. 

> 
> P13:
> 
> "...so the chances of successfully injecting data into a 
> connection are
> 1 in (2^32/RCV.WND *2)."  In describing the RST attacks, we 
> spoke in terms of mean number of tries, and I'd be consistent 
> here.  Similarly I'd do the math all the way: " ... so the 
> mean number of tries needed to inject data successfully is  
> 2*2^32/RWND = 2^33/RCV.WND."

Sure, it is good to be consistent. But the math which you depict above
seems incorrect to me. What was said earlier in the document is
(referenced from Watson's paper ) is :

============
   "[SITW] demonstrated that
   this assumption was incorrect and that instead of [1/2 * 2^32]
   packets (assuming a random distribution) [1/2 * (2^32/window)]
   packets is required.

   Substituting numbers into this formula we see that for a window size
   of 32,768, an average of 65,536 packets would need to be transmitted
   in order to "spoof" a TCP segment that would be acceptable to a TCP
   receiver.  A window size of 65,535 reduces this even further to
   32,768 packets.  At today's access bandwidths an attack of that size
   is feasible.

===============

So for data injection, this should become 2^32/RCV.WND. (i.e, [1/2 *
2^32 *2]/window )


> 
> This section used a) and b) instead of either A) and B) or 1) 
> and 2) (used earlier for the same purpose). Again, pick one.

Ok.

> 
> P15:
> 
> "There was no strong technical reasoning for choosing the 
> Data mitigation as MAY."
> First, everywhere else the you use "DATA", I'd use it here.

Sure.

> 
> Second, if I failed to make the case before, let me make it 
> now.  The DATA injection is 4 times less likely than either 
> the RST or the SYN attacks (2^33 vs 2^31) and may be visible 

Hmm.. It should be actually twice less likely 2^32 versus 2^31, based on
above.


> to the application as garbled data.  If the attack is visible 
> an application can gracefully terminate the connection and 
> re-establish the conversation - unlike the RST/SYN cases.  As 
> the attack is harder to carry out, and a successful attack 
> may be easier to recover from, I recommend a MAY.  I don't 
> care if you repeat that argument, but I do believe that there 
> are sound technical reasons for the MAY, and I'd like to see 
> the sentence that started this comment elided.

I think the general understanding was that any malicious event
responsible for the connection to go down is a problem. So I am not sure
whether I can buy this argument. OTOH, if you are classifying the
strength based on how easy/difficuly it is to contruct the attack vector
and cause harm to the connection, and if that is what is the consensus,
then so be it. I can mention this in the document.

> 
> P16:
> 
> "Currently there is no known bad behavior that can be 
> attributed to the lack of ACK throttling, but as a general 
> principle, if ever invoked, something incorrect is occurring 
> and such a mechanism will act as a failsafe that protects 
> both the sender and the network." -> "While we have not 
> encountered a case where the lack of ACK throttling can be 
> exploited, as a fail-safe mechanism we recommend its use.  An 
> implementation may take an excessive number of invocations of 
> the throttling mechanism as an indication that network 
> conditions are unusual or hostile."

Your change looks elegant. Will do.

> 
> P18:
> 
> "...the middle box design does not comply to [RFC0793]."   No 
> middlebox
> complies with RFC793; I suggest "...the middle box is 
> generating packets a conformant TCP endpoint would not generate."

Ok.

> 
> P22:
> 
> "ACK throttling was introduced to this document bt combining 
> the suggestions from the tcpm working group."  That seems out 
> of place in "Contributors".  That section is to acknowledge 
> the efforts of individuals.

Makes sense.. Good eye!

> 
> P24:
> 
> Why are RFC's 4302 and 4303 normative?  And if they are why 
> isn't RFC2385?  They're all referred to as possible 
> mitigations.  My preference is making 4302 and 4303 
> non-normative, but it's very likely that I'm missing a rule here.

I am not sure about the rules here?  David/Wes what needs to be done
here ?

> 
> Quotation marks are misplaced on the Medina05 reference.

Ok.

> 
> The NISCC reference lacks a date.
> 
> P25:
> 
> Quotation marks are misplaced on the SITW reference.

This was put in long back.... I need to check.

I'll incorporate these comments along with others received in the next
(final, hopefully ?) version.

Once again, thanks for the detailed review.

-Anantha
> 
> --
> Ted Faber
> http://www.isi.edu/~faber           PGP: 
> http://www.isi.edu/~faber/pubkeys.asc
> Unexpected attachment on this mail? See 
> http://www.isi.edu/~faber/FAQ.html#SIG
> 
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Sun Sep 28 14:07:48 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B9B463A698E;
	Sun, 28 Sep 2008 14:07:48 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 58FF93A698E
	for <tcpm@core3.amsl.com>; Sun, 28 Sep 2008 14:07:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.849
X-Spam-Level: 
X-Spam-Status: No, score=-4.849 tagged_above=-999 required=5 tests=[AWL=0.850, 
	BAYES_00=-2.599, J_CHICKENPOX_33=0.6, MIME_8BIT_HEADER=0.3,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id pE-unNoslsRf for <tcpm@core3.amsl.com>;
	Sun, 28 Sep 2008 14:07:46 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 6AEFA3A6989
	for <tcpm@ietf.org>; Sun, 28 Sep 2008 14:07:46 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,327,1220227200"; d="scan'208";a="164579142"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 28 Sep 2008 21:08:03 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m8SL83gY023222; 
	Sun, 28 Sep 2008 14:08:03 -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.13.8/8.13.8) with ESMTP id m8SL83Ph026236;
	Sun, 28 Sep 2008 21:08:03 GMT
Received: from xmb-sjc-21c.amer.cisco.com ([171.70.151.176]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 28 Sep 2008 14:08:02 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 28 Sep 2008 14:08:01 -0700
Message-ID: <0C53DCFB700D144284A584F54711EC5805DF435A@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <200808140650.IAA05627@TR-Sys.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: another review of draft-ietf-tcpm-tcpsecure[-10]
Thread-Index: Acj92i4QWt95JBWwQLeg6Sqf0q8UTQjzKXsA
References: <200808140650.IAA05627@TR-Sys.de>
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: =?iso-8859-1?Q?Alfred_H=CEnes?= <ah@tr-sys.de>, <rrs@cisco.com>,
	"Mitesh Dalal (mdalal)" <mdalal@cisco.com>
X-OriginalArrivalTime: 28 Sep 2008 21:08:02.0965 (UTC)
	FILETIME=[4B642450:01C921AE]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3915; t=1222636083;
	x=1223500083; c=relaxed/simple; s=sjdkim4002;
	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=20another=20review=20of=20draft-ietf-tcpm
	-tcpsecure[-10] |Sender:=20;
	bh=mT7BXMFbiHrIdyyNQ7Kf7veE+quylKGxHF69EX0KGcs=;
	b=JXk7PMyZaNFSi10ZrJb0PNtssqPPKWoWEPC2aNne+basAzeNgR3DcWDXcQ
	GAzjTHhygDJjbURI+xTyelW6+NMc3NiwlrECgPCpitSz7237hjqGSy9lj/BN
	oMJ638fpep;
Authentication-Results: sj-dkim-4; header.From=ananth@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: tcpm@ietf.org
Subject: Re: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

Alfred,
    I am compiling all the changes including the last call comments into th=
e next revision. I will incorporate all your comments below. =


In particular, regarding your observation of mentioning what the document i=
s doing, I agree that we should mention that it "updates 793". I am hoping =
that nobody has any objection to this point. =


-Anantha
-----Original Message-----
From: Alfred H=CEnes [mailto:ah@tr-sys.de] =

Sent: Wednesday, August 13, 2008 11:50 PM
To: Anantha Ramaiah (ananth); rrs@cisco.com; Mitesh Dalal (mdalal)
Cc: tcpm@ietf.org
Subject: another review of draft-ietf-tcpm-tcpsecure[-10]

Hello all,
I have once more tried to closely read the latest (-10) version of the 'tcp=
secure' draft, and only found a very small number of nits -- see below.


Furthermore, I once more advocate making clear in the document metadata wha=
t the document does, by adding to the heading:

    Updates: 793 (if approved)

Doing so will definitely help guide implementers to quickly locate the docu=
ment once published as an RFC.
By WG consensus, the document is intended for Standards Track, and Sections=
 3.2, 4.2, and 5.2 clearly state that they update RFC 793; thus, this shoul=
d be made visible at the metadata level as well.


Nits (in recently added / modified text):

(1)
At the very end of section 1, please change:

              [...] please refer to draft [RFC4953]
                                   ^^^^^^          ^
   to:
              [...] please refer to RFC 4953 [RFC4953].
                                   ^^^^^^^^^          ^
   or:
              [...] please refer to [RFC4953].
                                   ^         ^

(2)
In the first paragraph of section 5.2, please correct two punctuation flaws=
 (missing period, and extraneous apostrophe).
I also have included two minor stylistic improvement below:

                                                    [...].  It needs to
|  be noted that RFC 793 page 72 (fifth check) says : "If the ACK is a
                        ^                          ^^
   duplicate (SEG.ACK < SND.UNA), it can be ignored.  If the ACK
   acknowledges something not yet sent (SEG.ACK > SND.NXT) then send an
|  ACK, drop the segment, and return" This mitigation makes the ACK
                                    ^^
   check more stringent since any ACK < SND.UNA wouldn't be accepted,
|  instead only ACK's which are in the range ((SND.UNA - MAX.SND.WND) <=3D
                   ^^
   SEG.ACK <=3D SND.NXT) gets through.
---
                                                    [...].  It needs to
|  be noted that RFC 793 on page 72 (fifth check) says: "If the ACK is a
                        ^^^^                          ^
   duplicate (SEG.ACK < SND.UNA), it can be ignored.  If the ACK
   acknowledges something not yet sent (SEG.ACK > SND.NXT) then send an
|  ACK, drop the segment, and return."  This mitigation makes the ACK
                                    ^^^^
   check more stringent since any ACK < SND.UNA wouldn't be accepted,
|  instead only ACKs which are in the range ((SND.UNA - MAX.SND.WND) <=3D
                   ^^
   SEG.ACK <=3D SND.NXT) gets through.

Note: The quotation comprises multiple sentences; hence the "rational
      quotation" rule of the RFC-Ed does not apply.


IMO, otherwise the draft is ready to go, and because of the importance of t=
he topic, it should now be advanced quickly!

Kind regards,
  Alfred H=CEnes.

-- =


+------------------------+--------------------------------------------+
| TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math., Dipl.-Phys.  |
| Gerlinger Strasse 12   |  Phone: (+49)7156/9635-0, Fax: -18         |
| D-71254  Ditzingen     |  E-Mail:  ah@TR-Sys.de                     |
+------------------------+--------------------------------------------+

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Mon Sep 29 07:43:47 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0E78E3A69CC;
	Mon, 29 Sep 2008 07:43:47 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 383A53A69BA
	for <tcpm@core3.amsl.com>; Mon, 29 Sep 2008 07:43:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.474
X-Spam-Level: 
X-Spam-Status: No, score=-3.474 tagged_above=-999 required=5 tests=[AWL=0.125, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id dNraSH69C41d for <tcpm@core3.amsl.com>;
	Mon, 29 Sep 2008 07:43:44 -0700 (PDT)
Received: from mail.wrs.com (mail.windriver.com [147.11.1.11])
	by core3.amsl.com (Postfix) with ESMTP id 7C4873A6817
	for <tcpm@ietf.org>; Mon, 29 Sep 2008 07:43:44 -0700 (PDT)
Received: from ALA-MAIL03.corp.ad.wrs.com (ala-mail03 [147.11.57.144])
	by mail.wrs.com (8.13.6/8.13.6) with ESMTP id m8TEhFl4012279;
	Mon, 29 Sep 2008 07:43:16 -0700 (PDT)
Received: from ala-mail06.corp.ad.wrs.com ([147.11.57.147]) by
	ALA-MAIL03.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 29 Sep 2008 07:43:15 -0700
Received: from dab-restive.wrs.com ([192.168.117.73]) by
	ala-mail06.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 29 Sep 2008 07:43:15 -0700
Message-Id: <6FDABCB8-7EDA-40A2-A40A-9F768396A2D2@windriver.com>
From: David Borman <david.borman@windriver.com>
To: Anantha Ramaiah (ananth) <ananth@cisco.com>
In-Reply-To: <0C53DCFB700D144284A584F54711EC5805DF4359@xmb-sjc-21c.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 29 Sep 2008 09:43:13 -0500
References: <FE34F27F-8DDF-4C94-BC6E-E2ABF6000309@windriver.com>
	<B5A5E01F9387F4409E67604C0257C71E409513@NDJSEVS25A.ndc.nasa.gov>
	<24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>
	<20080906013831.GD2074@zod.isi.edu>
	<0C53DCFB700D144284A584F54711EC5805DF4359@xmb-sjc-21c.amer.cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 29 Sep 2008 14:43:15.0295 (UTC)
	FILETIME=[B47B06F0:01C92241]
Cc: tcpm@ietf.org, Ted Faber <faber@isi.edu>,
	"Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org


On Sep 28, 2008, at 4:03 PM, Anantha Ramaiah (ananth) wrote:

>> P24:
>>
>> Why are RFC's 4302 and 4303 normative?  And if they are why
>> isn't RFC2385?  They're all referred to as possible
>> mitigations.  My preference is making 4302 and 4303
>> non-normative, but it's very likely that I'm missing a rule here.
>
> I am not sure about the rules here?  David/Wes what needs to be done
> here ?

Typically normative references are things that a document depends on  
for understanding and/or implementation.  The only references to RFC  
4302 & 4303 are to say that the only real way to secure a connection  
is using IPsec, and since this document deals with the absence of  
them, I agree with Ted, these should be informative references.

			-David

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Mon Sep 29 07:53:32 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AFCEA3A6A8D;
	Mon, 29 Sep 2008 07:53:32 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 142463A6AFC
	for <tcpm@core3.amsl.com>; Mon, 29 Sep 2008 07:53:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gIenjw+ykCpz for <tcpm@core3.amsl.com>;
	Mon, 29 Sep 2008 07:53:30 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id 2E2E23A6AF4
	for <tcpm@ietf.org>; Mon, 29 Sep 2008 07:53:30 -0700 (PDT)
Received: from [192.168.1.45] (pool-71-106-119-240.lsanca.dsl-w.verizon.net
	[71.106.119.240])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m8TErIvP015158
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 29 Sep 2008 07:53:20 -0700 (PDT)
Message-ID: <48E0EBDE.5060403@isi.edu>
Date: Mon, 29 Sep 2008 07:53:18 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: David Borman <david.borman@windriver.com>
References: <FE34F27F-8DDF-4C94-BC6E-E2ABF6000309@windriver.com>	<B5A5E01F9387F4409E67604C0257C71E409513@NDJSEVS25A.ndc.nasa.gov>	<24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>	<20080906013831.GD2074@zod.isi.edu>	<0C53DCFB700D144284A584F54711EC5805DF4359@xmb-sjc-21c.amer.cisco.com>
	<6FDABCB8-7EDA-40A2-A40A-9F768396A2D2@windriver.com>
In-Reply-To: <6FDABCB8-7EDA-40A2-A40A-9F768396A2D2@windriver.com>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Ted Faber <faber@ISI.EDU>, tcpm@ietf.org,
	"Anantha Ramaiah \(ananth\)" <ananth@cisco.com>,
	"Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

FWIW, it seems like RFC1122 should be moved to normative.

Regarding some of the recent thread regarding the numbers in section
1.3 (Ted's comments, "finish the math"), I've noted before, as well,
that section 1.3 is redundant with RFC4953. Replicating the math isn't
needed. Also, the prediction regarding the impact of BW on the attack is
a guess in this doc, whereas in RFC4953 the relationship is explained.

Joe

David Borman wrote:
> 
> On Sep 28, 2008, at 4:03 PM, Anantha Ramaiah (ananth) wrote:
> 
>>> P24:
>>>
>>> Why are RFC's 4302 and 4303 normative?  And if they are why
>>> isn't RFC2385?  They're all referred to as possible
>>> mitigations.  My preference is making 4302 and 4303
>>> non-normative, but it's very likely that I'm missing a rule here.
>>
>> I am not sure about the rules here?  David/Wes what needs to be done
>> here ?
> 
> Typically normative references are things that a document depends on for
> understanding and/or implementation.  The only references to RFC 4302 &
> 4303 are to say that the only real way to secure a connection is using
> IPsec, and since this document deals with the absence of them, I agree
> with Ted, these should be informative references.
> 
>             -David
> 
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkjg694ACgkQE5f5cImnZrtsxQCgkNBjvjje7gc63/VsIjEvCU8m
KpQAoI798NpQRLmIWQoxxOWizSv8zYqu
=0+Tk
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Mon Sep 29 08:21:29 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 349D43A693F;
	Mon, 29 Sep 2008 08:21:29 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1D7203A6AE9
	for <tcpm@core3.amsl.com>; Mon, 29 Sep 2008 08:21:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id MgSRTKTi6isT for <tcpm@core3.amsl.com>;
	Mon, 29 Sep 2008 08:21:24 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by core3.amsl.com (Postfix) with ESMTP id 415523A67A8
	for <tcpm@ietf.org>; Mon, 29 Sep 2008 08:21:24 -0700 (PDT)
Received: from zod.isi.edu (zod.isi.edu [128.9.168.221])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m8TFJxGN015516
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 29 Sep 2008 08:20:00 -0700 (PDT)
Received: (from faber@localhost)
	by zod.isi.edu (8.14.3/8.14.2/Submit) id m8TFJxpT008849;
	Mon, 29 Sep 2008 08:19:59 -0700 (PDT) (envelope-from faber)
Date: Mon, 29 Sep 2008 08:19:59 -0700
From: Ted Faber <faber@ISI.EDU>
To: Joe Touch <touch@ISI.EDU>
Message-ID: <20080929151959.GA54282@zod.isi.edu>
References: <FE34F27F-8DDF-4C94-BC6E-E2ABF6000309@windriver.com>
	<B5A5E01F9387F4409E67604C0257C71E409513@NDJSEVS25A.ndc.nasa.gov>
	<24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>
	<20080906013831.GD2074@zod.isi.edu>
	<0C53DCFB700D144284A584F54711EC5805DF4359@xmb-sjc-21c.amer.cisco.com>
	<6FDABCB8-7EDA-40A2-A40A-9F768396A2D2@windriver.com>
	<48E0EBDE.5060403@isi.edu>
Mime-Version: 1.0
In-Reply-To: <48E0EBDE.5060403@isi.edu>
User-Agent: Mutt/1.4.2.3i
X-url: http://www.isi.edu/~faber
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: faber@zod.isi.edu
Cc: "Anantha Ramaiah \(ananth\)" <ananth@cisco.com>, tcpm@ietf.org,
	David Borman <david.borman@windriver.com>,
	"Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0282995908=="
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org


--===============0282995908==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="1yeeQ81UyVL57Vl7"
Content-Disposition: inline


--1yeeQ81UyVL57Vl7
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Sep 29, 2008 at 07:53:18AM -0700, Joe Touch wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> FWIW, it seems like RFC1122 should be moved to normative.
>=20
> Regarding some of the recent thread regarding the numbers in section
> 1.3 (Ted's comments, "finish the math"), I've noted before, as well,
> that section 1.3 is redundant with RFC4953. Replicating the math isn't
> needed. Also, the prediction regarding the impact of BW on the attack is
> a guess in this doc, whereas in RFC4953 the relationship is explained.

I don't have an y strong attachment to where the arithmatic is done, but
expressions like (2*2^32) need to be simplified so it's easy for a
reader to compare the risks.

If the authors are cool with a pointer to 4953 for derivations, I am,
too, but the final numbers should appear here as well.

--=20
Ted Faber
http://www.isi.edu/~faber           PGP: http://www.isi.edu/~faber/pubkeys.=
asc
Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#=
SIG

--1yeeQ81UyVL57Vl7
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkjg8h8ACgkQaUz3f+Zf+XuscACg2Pw/oCNiEVxHqBSVWpR6fe3g
S/EAoIFvTg0ZvBFjO5/UvqsC3+Fpe+ub
=6xZE
-----END PGP SIGNATURE-----

--1yeeQ81UyVL57Vl7--

--===============0282995908==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm

--===============0282995908==--


From tcpm-bounces@ietf.org  Mon Sep 29 08:27:35 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1605B3A6AFA;
	Mon, 29 Sep 2008 08:27:35 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0F02D3A6AFA
	for <tcpm@core3.amsl.com>; Mon, 29 Sep 2008 08:27:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.471
X-Spam-Level: 
X-Spam-Status: No, score=-6.471 tagged_above=-999 required=5 tests=[AWL=0.128, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id KZRBQFRrcAyl for <tcpm@core3.amsl.com>;
	Mon, 29 Sep 2008 08:27:30 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id EC5083A6A8D
	for <tcpm@ietf.org>; Mon, 29 Sep 2008 08:27:29 -0700 (PDT)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com
	[10.160.244.31])
	by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m8TFQg7f011843; Mon, 29 Sep 2008 18:26:42 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 29 Sep 2008 18:26:24 +0300
Received: from net-202.nrpn.net ([10.241.184.208]) by esebh102.NOE.Nokia.com
	over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 29 Sep 2008 18:26:23 +0300
Message-Id: <B35986E6-D8D7-4A9E-B8AB-3DB2E5C3FA29@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
To: ext Anantha Ramaiah (ananth) <ananth@cisco.com>
In-Reply-To: <0C53DCFB700D144284A584F54711EC5805DF435A@xmb-sjc-21c.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 29 Sep 2008 18:26:18 +0300
References: <200808140650.IAA05627@TR-Sys.de>
	<0C53DCFB700D144284A584F54711EC5805DF435A@xmb-sjc-21c.amer.cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 29 Sep 2008 15:26:23.0722 (UTC)
	FILETIME=[BB4DA4A0:01C92247]
X-Nokia-AV: Clean
Cc: tcpm@ietf.org, =?ISO-8859-1?Q?Alfred_H=CEnes?= <ah@tr-sys.de>,
	"Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>, rrs@cisco.com
Subject: Re: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

Hi,

(individual hat on)

On 2008-9-29, at 0:08, ext Anantha Ramaiah (ananth) wrote:
> In particular, regarding your observation of mentioning what the  
> document is doing, I agree that we should mention that it "updates  
> 793". I am hoping that nobody has any objection to this point.

since this document specifies an optional component to TCP, I'd argue  
that it should not update RFC793. If you look at the RFC Editor page,  
almost no other RFC updates RFC793, because even widely-deployed  
extensions (timestamps, SACK, etc.) are all optional. Even RFC2581  
doesn't update RFC793.

Lars
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Mon Sep 29 08:33:32 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AE4DD3A6940;
	Mon, 29 Sep 2008 08:33:32 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 998F83A6940
	for <tcpm@core3.amsl.com>; Mon, 29 Sep 2008 08:33:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id AHVcYZor9HIb for <tcpm@core3.amsl.com>;
	Mon, 29 Sep 2008 08:33:29 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id 9DA6A3A69D6
	for <tcpm@ietf.org>; Mon, 29 Sep 2008 08:33:29 -0700 (PDT)
Received: from [192.168.1.45] (pool-71-106-119-240.lsanca.dsl-w.verizon.net
	[71.106.119.240])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m8TFWIZn014074
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 29 Sep 2008 08:32:20 -0700 (PDT)
Message-ID: <48E0F501.90001@isi.edu>
Date: Mon, 29 Sep 2008 08:32:17 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Ted Faber <faber@ISI.EDU>
References: <FE34F27F-8DDF-4C94-BC6E-E2ABF6000309@windriver.com>
	<B5A5E01F9387F4409E67604C0257C71E409513@NDJSEVS25A.ndc.nasa.gov>
	<24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>
	<20080906013831.GD2074@zod.isi.edu>
	<0C53DCFB700D144284A584F54711EC5805DF4359@xmb-sjc-21c.amer.cisco.com>
	<6FDABCB8-7EDA-40A2-A40A-9F768396A2D2@windriver.com>
	<48E0EBDE.5060403@isi.edu> <20080929151959.GA54282@zod.isi.edu>
In-Reply-To: <20080929151959.GA54282@zod.isi.edu>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "Anantha Ramaiah \(ananth\)" <ananth@cisco.com>, tcpm@ietf.org,
	David Borman <david.borman@windriver.com>,
	"Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Ted Faber wrote:
> On Mon, Sep 29, 2008 at 07:53:18AM -0700, Joe Touch wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> FWIW, it seems like RFC1122 should be moved to normative.
>>
>> Regarding some of the recent thread regarding the numbers in section
>> 1.3 (Ted's comments, "finish the math"), I've noted before, as well,
>> that section 1.3 is redundant with RFC4953. Replicating the math isn't
>> needed. Also, the prediction regarding the impact of BW on the attack is
>> a guess in this doc, whereas in RFC4953 the relationship is explained.
> 
> I don't have an y strong attachment to where the arithmatic is done, but
> expressions like (2*2^32) need to be simplified so it's easy for a
> reader to compare the risks.
> 
> If the authors are cool with a pointer to 4953 for derivations, I am,
> too, but the final numbers should appear here as well.

Agreed - a summary statement and the final numbers or conclusions from
4953 need to be contained in this doc.

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

iEYEARECAAYFAkjg9QEACgkQE5f5cImnZruQugCfWEPoi8xbrF0g03o8Qtg5wdhN
Sc8AoI+wE8rgAwf3g8J/XQ9Ij3krAtya
=Y2HF
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Mon Sep 29 08:41:31 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E010828C0DE;
	Mon, 29 Sep 2008 08:41:31 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 825E53A6B24
	for <tcpm@core3.amsl.com>; Mon, 29 Sep 2008 08:41:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id e20Jkb77hO9A for <tcpm@core3.amsl.com>;
	Mon, 29 Sep 2008 08:41:29 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by core3.amsl.com (Postfix) with ESMTP id B13193A6B25
	for <tcpm@ietf.org>; Mon, 29 Sep 2008 08:41:29 -0700 (PDT)
Received: from zod.isi.edu (zod.isi.edu [128.9.168.221])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m8TFeFVx026810
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 29 Sep 2008 08:40:16 -0700 (PDT)
Received: (from faber@localhost)
	by zod.isi.edu (8.14.3/8.14.2/Submit) id m8TFeFOj099282;
	Mon, 29 Sep 2008 08:40:15 -0700 (PDT) (envelope-from faber)
Date: Mon, 29 Sep 2008 08:40:15 -0700
From: Ted Faber <faber@ISI.EDU>
To: Joe Touch <touch@ISI.EDU>
Message-ID: <20080929154015.GB54282@zod.isi.edu>
References: <FE34F27F-8DDF-4C94-BC6E-E2ABF6000309@windriver.com>
	<B5A5E01F9387F4409E67604C0257C71E409513@NDJSEVS25A.ndc.nasa.gov>
	<24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>
	<20080906013831.GD2074@zod.isi.edu>
	<0C53DCFB700D144284A584F54711EC5805DF4359@xmb-sjc-21c.amer.cisco.com>
	<6FDABCB8-7EDA-40A2-A40A-9F768396A2D2@windriver.com>
	<48E0EBDE.5060403@isi.edu> <20080929151959.GA54282@zod.isi.edu>
	<48E0F501.90001@isi.edu>
Mime-Version: 1.0
In-Reply-To: <48E0F501.90001@isi.edu>
User-Agent: Mutt/1.4.2.3i
X-url: http://www.isi.edu/~faber
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: faber@zod.isi.edu
Cc: "Anantha Ramaiah \(ananth\)" <ananth@cisco.com>, tcpm@ietf.org,
	David Borman <david.borman@windriver.com>,
	"Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1577274749=="
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org


--===============1577274749==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="rS8CxjVDS/+yyDmU"
Content-Disposition: inline


--rS8CxjVDS/+yyDmU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Sep 29, 2008 at 08:32:17AM -0700, Joe Touch wrote:
> Ted Faber wrote:
> >=20
> > If the authors are cool with a pointer to 4953 for derivations, I am,
> > too, but the final numbers should appear here as well.
>=20
> Agreed - a summary statement and the final numbers or conclusions from
> 4953 need to be contained in this doc.

Just to be clear, I don't have a preference, and apparently I wasn't
quite clear enough on thst.

If the authors are determined to include the derivation here, that's
fine with me, as it's fine with me to point off to 4953.  My only 2
concerns are that the final figures be simplified in this draft and that
the two documents agree(!).

--=20
Ted Faber
http://www.isi.edu/~faber           PGP: http://www.isi.edu/~faber/pubkeys.=
asc
Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#=
SIG

--rS8CxjVDS/+yyDmU
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkjg9t8ACgkQaUz3f+Zf+XudEQCfaKzWlNqsNud0LrPbafXx4qKm
FvkAnRToU8w12iu9xaWFhKT7bCBO1O/N
=s5Rd
-----END PGP SIGNATURE-----

--rS8CxjVDS/+yyDmU--

--===============1577274749==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm

--===============1577274749==--


From tcpm-bounces@ietf.org  Mon Sep 29 08:57:29 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C7CB73A6B20;
	Mon, 29 Sep 2008 08:57:29 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1B89A3A6B3B
	for <tcpm@core3.amsl.com>; Mon, 29 Sep 2008 08:57:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.724
X-Spam-Level: 
X-Spam-Status: No, score=-5.724 tagged_above=-999 required=5 tests=[AWL=0.875, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ECXM7lpTmKXp for <tcpm@core3.amsl.com>;
	Mon, 29 Sep 2008 08:57:22 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 5E8943A693C
	for <tcpm@ietf.org>; Mon, 29 Sep 2008 08:57:22 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,332,1220227200"; d="scan'208";a="165044332"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 29 Sep 2008 15:57:41 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m8TFvfXn014263; 
	Mon, 29 Sep 2008 08:57:41 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m8TFvfuT005234;
	Mon, 29 Sep 2008 15:57:41 GMT
Received: from xmb-sjc-21c.amer.cisco.com ([171.70.151.176]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 29 Sep 2008 08:57:41 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 29 Sep 2008 08:57:42 -0700
Message-ID: <0C53DCFB700D144284A584F54711EC5805DF44B8@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <48E0EBDE.5060403@isi.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
Thread-Index: AckiQzEPFNCznTEATb6KmBJzaksjhwAB4FjQ
References: <FE34F27F-8DDF-4C94-BC6E-E2ABF6000309@windriver.com>	<B5A5E01F9387F4409E67604C0257C71E409513@NDJSEVS25A.ndc.nasa.gov>	<24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>	<20080906013831.GD2074@zod.isi.edu>	<0C53DCFB700D144284A584F54711EC5805DF4359@xmb-sjc-21c.amer.cisco.com><6FDABCB8-7EDA-40A2-A40A-9F768396A2D2@windriver.com>
	<48E0EBDE.5060403@isi.edu>
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: "Joe Touch" <touch@ISI.EDU>, "David Borman" <david.borman@windriver.com>
X-OriginalArrivalTime: 29 Sep 2008 15:57:41.0274 (UTC)
	FILETIME=[1A6957A0:01C9224C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2735; t=1222703861;
	x=1223567861; c=relaxed/simple; s=sjdkim1004;
	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[tcpm]=20WGLC=3A=20draft-ietf-tcpm-tcps
	ecure-10.txt |Sender:=20;
	bh=vBAO+VtoOyLW68SzeobUX8+Jx9ellNoQscxSaZCySrQ=;
	b=nrayMNyjQdNzcpFcgDoFdpqpj4H+LshTBpStywtRYbJwklZZ2aPlpki4Ac
	jmQ+rmepTKfSzjBsYkZEa4ool2/kEG1BxT+myjbuKBVKrLxRBIh4UeI8mH2e
	Pks2xuJV0FZizsAUPgatzmmqUGgG+Sys42KnW+WApM27CzMRT8USY=;
Authentication-Results: sj-dkim-1; header.From=ananth@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: tcpm@ietf.org, Ted Faber <faber@ISI.EDU>,
	"Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

 
Yes, in the current document (tcpsecure) the math is all about how many
numbers (quantifies difficulty) one has to guess and doesn't explain in
detail how much time this would take to ultimately kill the connection
taking into account varying bandwidth. I am fine adding another explicit
reference here if needed. The current math still need to exist, and it
isn't redundant and is limited in scope. Maybe we can have real numbers
like 4294967296 instead of 2^32.

Good point about 1122, should be under normative. 

-Anantha

-----Original Message-----
From: tcpm-bounces@ietf.org [mailto:tcpm-bounces@ietf.org] On Behalf Of
Joe Touch
Sent: Monday, September 29, 2008 7:53 AM
To: David Borman
Cc: Ted Faber; tcpm@ietf.org; Anantha Ramaiah (ananth); Mitesh Dalal
(mdalal)
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

FWIW, it seems like RFC1122 should be moved to normative.

Regarding some of the recent thread regarding the numbers in section
1.3 (Ted's comments, "finish the math"), I've noted before, as well,
that section 1.3 is redundant with RFC4953. Replicating the math isn't
needed. Also, the prediction regarding the impact of BW on the attack is
a guess in this doc, whereas in RFC4953 the relationship is explained.

Joe

David Borman wrote:
> 
> On Sep 28, 2008, at 4:03 PM, Anantha Ramaiah (ananth) wrote:
> 
>>> P24:
>>>
>>> Why are RFC's 4302 and 4303 normative?  And if they are why isn't 
>>> RFC2385?  They're all referred to as possible mitigations.  My 
>>> preference is making 4302 and 4303 non-normative, but it's very 
>>> likely that I'm missing a rule here.
>>
>> I am not sure about the rules here?  David/Wes what needs to be done 
>> here ?
> 
> Typically normative references are things that a document depends on 
> for understanding and/or implementation.  The only references to RFC 
> 4302 &
> 4303 are to say that the only real way to secure a connection is using

> IPsec, and since this document deals with the absence of them, I agree

> with Ted, these should be informative references.
> 
>             -David
> 
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkjg694ACgkQE5f5cImnZrtsxQCgkNBjvjje7gc63/VsIjEvCU8m
KpQAoI798NpQRLmIWQoxxOWizSv8zYqu
=0+Tk
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Mon Sep 29 09:08:53 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 89EBF3A6A58;
	Mon, 29 Sep 2008 09:08:53 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D11673A68C6
	for <tcpm@core3.amsl.com>; Mon, 29 Sep 2008 09:08:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_33=0.6]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id qYP3sWjcagy9 for <tcpm@core3.amsl.com>;
	Mon, 29 Sep 2008 09:08:51 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by core3.amsl.com (Postfix) with ESMTP id CE59A3A6A7A
	for <tcpm@ietf.org>; Mon, 29 Sep 2008 09:08:51 -0700 (PDT)
Received: from zod.isi.edu (zod.isi.edu [128.9.168.221])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m8TG7OOW012211
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 29 Sep 2008 09:07:25 -0700 (PDT)
Received: (from faber@localhost)
	by zod.isi.edu (8.14.3/8.14.2/Submit) id m8TG7Oec060850;
	Mon, 29 Sep 2008 09:07:24 -0700 (PDT) (envelope-from faber)
Date: Mon, 29 Sep 2008 09:07:24 -0700
From: Ted Faber <faber@ISI.EDU>
To: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
Message-ID: <20080929160724.GD54282@zod.isi.edu>
References: <FE34F27F-8DDF-4C94-BC6E-E2ABF6000309@windriver.com>
	<B5A5E01F9387F4409E67604C0257C71E409513@NDJSEVS25A.ndc.nasa.gov>
	<24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>
	<20080906013831.GD2074@zod.isi.edu>
	<0C53DCFB700D144284A584F54711EC5805DF4359@xmb-sjc-21c.amer.cisco.com>
Mime-Version: 1.0
In-Reply-To: <0C53DCFB700D144284A584F54711EC5805DF4359@xmb-sjc-21c.amer.cisco.com>
User-Agent: Mutt/1.4.2.3i
X-url: http://www.isi.edu/~faber
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: faber@zod.isi.edu
Cc: rrs@cisco.com, tcpm@ietf.org, David Borman <david.borman@windriver.com>,
	"Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0973761383=="
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org


--===============0973761383==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="C1iGAkRnbeBonpVg"
Content-Disposition: inline


--C1iGAkRnbeBonpVg
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Sep 28, 2008 at 02:03:55PM -0700, Anantha Ramaiah (ananth) wrote:
>=20
> Ted,
>   Appreciate the detailed comments. Pl see inline responses.

My pleasure.

> > -----Original Message-----
> > From: Ted Faber [mailto:faber@ISI.EDU]=20
> >
> > P13:
> >=20
> > "...so the chances of successfully injecting data into a=20
> > connection are
> > 1 in (2^32/RCV.WND *2)."  In describing the RST attacks, we=20
> > spoke in terms of mean number of tries, and I'd be consistent=20
> > here.  Similarly I'd do the math all the way: " ... so the=20
> > mean number of tries needed to inject data successfully is =20
> > 2*2^32/RWND =3D 2^33/RCV.WND."
>=20
> Sure, it is good to be consistent. But the math which you depict above
> seems incorrect to me. What was said earlier in the document is
> (referenced from Watson's paper ) is :
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>    "[SITW] demonstrated that
>    this assumption was incorrect and that instead of [1/2 * 2^32]
>    packets (assuming a random distribution) [1/2 * (2^32/window)]
>    packets is required.
>=20
>    Substituting numbers into this formula we see that for a window size
>    of 32,768, an average of 65,536 packets would need to be transmitted
>    in order to "spoof" a TCP segment that would be acceptable to a TCP
>    receiver.  A window size of 65,535 reduces this even further to
>    32,768 packets.  At today's access bandwidths an attack of that size
>    is feasible.
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> So for data injection, this should become 2^32/RCV.WND. (i.e, [1/2 *
> 2^32 *2]/window )

The paragraph I'm commenting on reads:

   A third type of attack is also highlighted by both the RST and SYN
   attacks.  It is also possible to inject data into a TCP connection by
   simply guessing a sequence number within the current receive window
   of the victim.  The ACK value of any data segment is considered valid
   as long as it does not acknowledge data ahead of the next segment to
   send.  In other words an ACK value is acceptable if it is ((SND.UNA-
   (2^31-1)) <=3D SEG.ACK <=3D SND.NXT).  The (2^31 - 1) in the above
   inequality takes into account the fact that comparisons on TCP
   sequence and acknowledgement numbers is done using the modulo 32 bit
   arithmetic to accommodate the number wraparound.  This means that an
   attacker has to guess two ACK values with every guessed sequence
   number so that the chances of successfully injecting data into a
   connection are 1 in ((2^32 / RCV.WND) * 2).

I'm saying that, assuming the math is correct, that last expression
should be (2^33 / RCV.WND).  I didn't check the math.  If you also
believe the math is wrong, you have a larger edit. :-)

On rereading the argument, it does sound like a data injection attack
should be harder by a factor of 2 and that they multiplied by the wrong
expression (2^32 rather than 2^31).  So I think you're correct about the
math, and if so the final expression would be 2^32 / RCV.WND.

I'd be happier if someone else also looked at this paragraph for
technical accuracy.

--=20
Ted Faber
http://www.isi.edu/~faber           PGP: http://www.isi.edu/~faber/pubkeys.=
asc
Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#=
SIG

--C1iGAkRnbeBonpVg
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkjg/TwACgkQaUz3f+Zf+Xu0IACeJ62Rf/CUHktYqn9XYqdXIHv/
tHAAoIwQczy4Pw8HtcsBzYdPVk+opyj6
=d5PS
-----END PGP SIGNATURE-----

--C1iGAkRnbeBonpVg--

--===============0973761383==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm

--===============0973761383==--


From tcpm-bounces@ietf.org  Mon Sep 29 09:14:35 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EA8BE28C11E;
	Mon, 29 Sep 2008 09:14:35 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 48D0428C114
	for <tcpm@core3.amsl.com>; Mon, 29 Sep 2008 09:14:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.016
X-Spam-Level: 
X-Spam-Status: No, score=-6.016 tagged_above=-999 required=5 tests=[AWL=0.583, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id HpIZ6KCvIyuV for <tcpm@core3.amsl.com>;
	Mon, 29 Sep 2008 09:14:33 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 7266428C110
	for <tcpm@ietf.org>; Mon, 29 Sep 2008 09:14:33 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,332,1220227200"; d="scan'208";a="165056058"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 29 Sep 2008 16:14:43 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m8TGEhq1014939; 
	Mon, 29 Sep 2008 09:14:43 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m8TGEhQ8023776;
	Mon, 29 Sep 2008 16:14:43 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); 
	Mon, 29 Sep 2008 09:14:43 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 29 Sep 2008 09:14:47 -0700
Message-ID: <0C53DCFB700D144284A584F54711EC5805DF44E1@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <B35986E6-D8D7-4A9E-B8AB-3DB2E5C3FA29@nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
Thread-Index: AckiR8oje1QupBQJTiGSc6DWkxBMzQABK5UQ
References: <200808140650.IAA05627@TR-Sys.de>
	<0C53DCFB700D144284A584F54711EC5805DF435A@xmb-sjc-21c.amer.cisco.com>
	<B35986E6-D8D7-4A9E-B8AB-3DB2E5C3FA29@nokia.com>
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: "Lars Eggert" <lars.eggert@nokia.com>
X-OriginalArrivalTime: 29 Sep 2008 16:14:43.0501 (UTC)
	FILETIME=[7BB4CDD0:01C9224E]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1612; t=1222704883;
	x=1223568883; c=relaxed/simple; s=sjdkim4002;
	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[tcpm]=20another=20review=20of=20draft-
	ietf-tcpm-tcpsecure[-10] |Sender:=20;
	bh=blgS6xaJcohYzXoJA+/i+8m9JBEagvPIOTQpUz6x2VA=;
	b=muntB462m2w0yBXpfRTQ8isVnHlh56coKpOiy+SOq7yaFE/BJXq/kVVQq3
	7/789h/wvplXy5JBDCyjdof/WlL5wyeH70Gvg0Ac5+2lhPyZzxwiDV+3jBBk
	S/2E92iDFL;
Authentication-Results: sj-dkim-4; header.From=ananth@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: tcpm@ietf.org, =?iso-8859-1?Q?Alfred_H=CEnes?= <ah@tr-sys.de>,
	"Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>, rrs@cisco.com
Subject: Re: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org


Lars,

Confused here. The TCP timestamps, SACK etc., are NOT specified in RFC 793.=
 Hence they don't update RFC 793 in any sense, these are independent.

Now, RFC 2001 is a separate RFC by itself which was obsoleted by RFC 2581. =
Yes, this is pretty close since this talks about congestion control which i=
s central to TCP, so may be it updates some sections of RFC 793, I haven't =
taken a close look.

Tcpsecure on the other hand does update the processing rules of 793 ( pl se=
e sections 3.2, 4.2, and 5.2), and hence Alfred's point makes sense to me. =

FWIW, I never thought about this until Alfred brought this point up, IMO, t=
his is a good point.

-Anantha

-----Original Message-----
From: Lars Eggert [mailto:lars.eggert@nokia.com] =

Sent: Monday, September 29, 2008 8:26 AM
To: Anantha Ramaiah (ananth)
Cc: Alfred H=CEnes; rrs@cisco.com; Mitesh Dalal (mdalal); tcpm@ietf.org
Subject: Re: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]

Hi,

(individual hat on)

On 2008-9-29, at 0:08, ext Anantha Ramaiah (ananth) wrote:
> In particular, regarding your observation of mentioning what the =

> document is doing, I agree that we should mention that it "updates =

> 793". I am hoping that nobody has any objection to this point.

since this document specifies an optional component to TCP, I'd argue that =
it should not update RFC793. If you look at the RFC Editor page, almost no =
other RFC updates RFC793, because even widely-deployed extensions (timestam=
ps, SACK, etc.) are all optional. Even RFC2581 doesn't update RFC793.

Lars
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Mon Sep 29 09:22:13 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8FA9C3A698A;
	Mon, 29 Sep 2008 09:22:13 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9C1DA3A6B0F
	for <tcpm@core3.amsl.com>; Mon, 29 Sep 2008 09:22:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 34uDNU3rp0IQ for <tcpm@core3.amsl.com>;
	Mon, 29 Sep 2008 09:22:08 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id B1CFD3A6940
	for <tcpm@ietf.org>; Mon, 29 Sep 2008 09:22:08 -0700 (PDT)
Received: from [75.215.184.156] (156.sub-75-215-184.myvzw.com [75.215.184.156])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m8TGLiNa009761
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 29 Sep 2008 09:21:46 -0700 (PDT)
Message-ID: <48E10094.6030204@isi.edu>
Date: Mon, 29 Sep 2008 09:21:40 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Ted Faber <faber@ISI.EDU>
References: <FE34F27F-8DDF-4C94-BC6E-E2ABF6000309@windriver.com>
	<B5A5E01F9387F4409E67604C0257C71E409513@NDJSEVS25A.ndc.nasa.gov>
	<24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>
	<20080906013831.GD2074@zod.isi.edu>
	<0C53DCFB700D144284A584F54711EC5805DF4359@xmb-sjc-21c.amer.cisco.com>
	<6FDABCB8-7EDA-40A2-A40A-9F768396A2D2@windriver.com>
	<48E0EBDE.5060403@isi.edu> <20080929151959.GA54282@zod.isi.edu>
	<48E0F501.90001@isi.edu> <20080929154015.GB54282@zod.isi.edu>
In-Reply-To: <20080929154015.GB54282@zod.isi.edu>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "Anantha Ramaiah \(ananth\)" <ananth@cisco.com>, tcpm@ietf.org,
	David Borman <david.borman@windriver.com>,
	"Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Ted Faber wrote:
> On Mon, Sep 29, 2008 at 08:32:17AM -0700, Joe Touch wrote:
>> Ted Faber wrote:
>>> If the authors are cool with a pointer to 4953 for derivations, I am,
>>> too, but the final numbers should appear here as well.
>> Agreed - a summary statement and the final numbers or conclusions from
>> 4953 need to be contained in this doc.
> 
> Just to be clear, I don't have a preference, and apparently I wasn't
> quite clear enough on thst.
> 
> If the authors are determined to include the derivation here, that's
> fine with me, as it's fine with me to point off to 4953.  My only 2
> concerns are that the final figures be simplified in this draft and that
> the two documents agree(!).

IMO, the whole point of developing 4953 was to document the problem and
define its impact mathematically so that other RFCs could refer to it.

This doc certainly needs to refer to the problem and the resulting
analysis, but there's no utility in replicating the derivations in 4953.

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

iEYEARECAAYFAkjhAJQACgkQE5f5cImnZrsYVgCgoiGrFMcKiEKhl4BeBYZFF62p
QQwAn1eo5zf0uOmVh3QCW98AwbIFJ2zB
=1ZFH
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Mon Sep 29 10:28:23 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B4C823A693C;
	Mon, 29 Sep 2008 10:28:23 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 083B23A693C
	for <tcpm@core3.amsl.com>; Mon, 29 Sep 2008 10:28:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id PUCEZ4oQ7EtW for <tcpm@core3.amsl.com>;
	Mon, 29 Sep 2008 10:28:19 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id 1A4F83A6870
	for <tcpm@ietf.org>; Mon, 29 Sep 2008 10:28:19 -0700 (PDT)
Received: from [75.215.184.156] (156.sub-75-215-184.myvzw.com [75.215.184.156])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m8THRYBP001680
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 29 Sep 2008 10:27:37 -0700 (PDT)
Message-ID: <48E11006.9000100@isi.edu>
Date: Mon, 29 Sep 2008 10:27:34 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
References: <200808140650.IAA05627@TR-Sys.de>	<0C53DCFB700D144284A584F54711EC5805DF435A@xmb-sjc-21c.amer.cisco.com>	<B35986E6-D8D7-4A9E-B8AB-3DB2E5C3FA29@nokia.com>
	<0C53DCFB700D144284A584F54711EC5805DF44E1@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <0C53DCFB700D144284A584F54711EC5805DF44E1@xmb-sjc-21c.amer.cisco.com>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>,
	=?ISO-8859-1?Q?Alfred_H=CEnes?= <ah@tr-sys.de>, tcpm@ietf.org,
	rrs@cisco.com
Subject: Re: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This has been the big issue with this doc from the beginning, and I've
been raising it from the beginning. Other docs describe extensions to
the protocol, but don't change the base protocol. This one does, which
has always been my broadest concern.

It's a little odd to hear anyone think this is the first time this was
raised.

Joe

Anantha Ramaiah (ananth) wrote:
> Lars,
> =

> Confused here. The TCP timestamps, SACK etc., are NOT specified in RFC 79=
3. Hence they don't update RFC 793 in any sense, these are independent.
> =

> Now, RFC 2001 is a separate RFC by itself which was obsoleted by RFC 2581=
. Yes, this is pretty close since this talks about congestion control which=
 is central to TCP, so may be it updates some sections of RFC 793, I haven'=
t taken a close look.
> =

> Tcpsecure on the other hand does update the processing rules of 793 ( pl =
see sections 3.2, 4.2, and 5.2), and hence Alfred's point makes sense to me=
. =

> FWIW, I never thought about this until Alfred brought this point up, IMO,=
 this is a good point.
> =

> -Anantha
> =

> -----Original Message-----
> From: Lars Eggert [mailto:lars.eggert@nokia.com] =

> Sent: Monday, September 29, 2008 8:26 AM
> To: Anantha Ramaiah (ananth)
> Cc: Alfred H=CEnes; rrs@cisco.com; Mitesh Dalal (mdalal); tcpm@ietf.org
> Subject: Re: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
> =

> Hi,
> =

> (individual hat on)
> =

> On 2008-9-29, at 0:08, ext Anantha Ramaiah (ananth) wrote:
>> In particular, regarding your observation of mentioning what the =

>> document is doing, I agree that we should mention that it "updates =

>> 793". I am hoping that nobody has any objection to this point.
> =

> since this document specifies an optional component to TCP, I'd argue tha=
t it should not update RFC793. If you look at the RFC Editor page, almost n=
o other RFC updates RFC793, because even widely-deployed extensions (timest=
amps, SACK, etc.) are all optional. Even RFC2581 doesn't update RFC793.
> =

> Lars
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkjhEAYACgkQE5f5cImnZrvhkgCfQMc0AP8JMGZqXgKhjNZ/LreG
k7kAoM9M9JgpiYagxzrNjibrCR29fwCy
=3DELvI
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Mon Sep 29 10:30:37 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B205B3A6940;
	Mon, 29 Sep 2008 10:30:37 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A67A93A6940
	for <tcpm@core3.amsl.com>; Mon, 29 Sep 2008 10:30:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1Hsfb4jCoA7l for <tcpm@core3.amsl.com>;
	Mon, 29 Sep 2008 10:30:36 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id CAF6D3A6870
	for <tcpm@ietf.org>; Mon, 29 Sep 2008 10:30:35 -0700 (PDT)
Received: from [75.215.184.156] (156.sub-75-215-184.myvzw.com [75.215.184.156])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m8THS7wd002119
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 29 Sep 2008 10:28:11 -0700 (PDT)
Message-ID: <48E11027.2000309@isi.edu>
Date: Mon, 29 Sep 2008 10:28:07 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Ted Faber <faber@ISI.EDU>
References: <FE34F27F-8DDF-4C94-BC6E-E2ABF6000309@windriver.com>	<B5A5E01F9387F4409E67604C0257C71E409513@NDJSEVS25A.ndc.nasa.gov>	<24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>	<20080906013831.GD2074@zod.isi.edu>	<0C53DCFB700D144284A584F54711EC5805DF4359@xmb-sjc-21c.amer.cisco.com>
	<20080929160724.GD54282@zod.isi.edu>
In-Reply-To: <20080929160724.GD54282@zod.isi.edu>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: David Borman <david.borman@windriver.com>, rrs@cisco.com, tcpm@ietf.org,
	"Anantha Ramaiah \(ananth\)" <ananth@cisco.com>,
	"Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Ted Faber wrote:
...
> I'd be happier if someone else also looked at this paragraph for
> technical accuracy.

Further good reasons not to replicate the derivation, IMO.

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

iEYEARECAAYFAkjhECcACgkQE5f5cImnZrt+sgCg3cBdGOHKoBYCGMtNkjIccNn1
8y8AoMvkbtwvjuWfyOffUfW06eg2VokN
=SYny
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Mon Sep 29 10:32:04 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E6B5A3A693C;
	Mon, 29 Sep 2008 10:32:04 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 635BE3A693C
	for <tcpm@core3.amsl.com>; Mon, 29 Sep 2008 10:32:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gmBYq5olFBiX for <tcpm@core3.amsl.com>;
	Mon, 29 Sep 2008 10:32:02 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id 8B3F63A6870
	for <tcpm@ietf.org>; Mon, 29 Sep 2008 10:32:02 -0700 (PDT)
Received: from [75.215.184.156] (156.sub-75-215-184.myvzw.com [75.215.184.156])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m8THVAfT003015
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 29 Sep 2008 10:31:13 -0700 (PDT)
Message-ID: <48E110DE.8050903@isi.edu>
Date: Mon, 29 Sep 2008 10:31:10 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Lars Eggert <lars.eggert@nokia.com>
References: <200808140650.IAA05627@TR-Sys.de>	<0C53DCFB700D144284A584F54711EC5805DF435A@xmb-sjc-21c.amer.cisco.com>
	<B35986E6-D8D7-4A9E-B8AB-3DB2E5C3FA29@nokia.com>
In-Reply-To: <B35986E6-D8D7-4A9E-B8AB-3DB2E5C3FA29@nokia.com>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: =?ISO-8859-1?Q?Alfred_H=CEnes?= <ah@tr-sys.de>, tcpm@ietf.org,
	"ext Anantha Ramaiah \(ananth\)" <ananth@cisco.com>,
	rrs@cisco.com, "Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>
Subject: Re: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Lars,

Is it possible that a SHOULD isn't considered a "updates"?

I.e., there are different issues:

	a) this doc does change the core 793 spec
	b) this doc is optional

(b) argues that we really ought not be using SHOULD, but rather MAY, for
the whole document. I've made that point before, but the label "updates"
may motivate revisiting that issue.

IMO, MAYs don't update, MUSTs definitely do. I don't know where SHOULDs
fall, though.

I.e., I would be comfortable with the current recommendation (SHOULD,
and not "updates"), but if SHOULD implies "updates", I'd suggest
considering going to a level of recommendation that does NOT update 793
(e.g., MAY, if that even suffices).

Joe



Lars Eggert wrote:
> Hi,
> 
> (individual hat on)
> 
> On 2008-9-29, at 0:08, ext Anantha Ramaiah (ananth) wrote:
>> In particular, regarding your observation of mentioning what the
>> document is doing, I agree that we should mention that it "updates
>> 793". I am hoping that nobody has any objection to this point.
> 
> since this document specifies an optional component to TCP, I'd argue
> that it should not update RFC793. If you look at the RFC Editor page,
> almost no other RFC updates RFC793, because even widely-deployed
> extensions (timestamps, SACK, etc.) are all optional. Even RFC2581
> doesn't update RFC793.
> 
> Lars
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkjhEN4ACgkQE5f5cImnZruuVACg9GiRCyUrI9O51lHcEUOVzoIf
heoAmwRbcNUcJ15slOox/D0A/homk1vm
=O+z6
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Mon Sep 29 10:37:50 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 53B453A693C;
	Mon, 29 Sep 2008 10:37:50 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E32D43A6A08
	for <tcpm@core3.amsl.com>; Mon, 29 Sep 2008 10:37:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.162
X-Spam-Level: 
X-Spam-Status: No, score=-6.162 tagged_above=-999 required=5 tests=[AWL=0.438, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id LS8QBzUsYmcf for <tcpm@core3.amsl.com>;
	Mon, 29 Sep 2008 10:37:47 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id B00283A68E1
	for <tcpm@ietf.org>; Mon, 29 Sep 2008 10:37:47 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,333,1220227200"; d="scan'208";a="165117596"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 29 Sep 2008 17:37:37 +0000
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 m8THbbvp015132; 
	Mon, 29 Sep 2008 10:37:37 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m8THbYwS008968;
	Mon, 29 Sep 2008 17:37:37 GMT
Received: from xmb-sjc-21c.amer.cisco.com ([171.70.151.176]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 29 Sep 2008 10:37:34 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 29 Sep 2008 10:37:40 -0700
Message-ID: <0C53DCFB700D144284A584F54711EC5805DF456C@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <48E11006.9000100@isi.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
Thread-Index: AckiWLp6W7pNe/ZfQNaJj3e87ZwypAAACCOw
References: <200808140650.IAA05627@TR-Sys.de>	<0C53DCFB700D144284A584F54711EC5805DF435A@xmb-sjc-21c.amer.cisco.com>	<B35986E6-D8D7-4A9E-B8AB-3DB2E5C3FA29@nokia.com>
	<0C53DCFB700D144284A584F54711EC5805DF44E1@xmb-sjc-21c.amer.cisco.com>
	<48E11006.9000100@isi.edu>
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: "Joe Touch" <touch@ISI.EDU>
X-OriginalArrivalTime: 29 Sep 2008 17:37:34.0943 (UTC)
	FILETIME=[0EEAA6F0:01C9225A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3739; t=1222709857;
	x=1223573857; 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[tcpm]=20another=20review=20of=20draft-
	ietf-tcpm-tcpsecure[-10] |Sender:=20;
	bh=/iP5+YgLycmzgyHVn7r/0xFPjk03TzzMpW4KaYKsJEY=;
	b=GfwZSlZHG/T50j7rIsgSqKQqrTZpTJVrVdgqnoAPbMdfyyz0tuNRlL6iL+
	bEZcQXg707zYZCX4Wnlp5HC3JHUH/eZcG0B4WJ61nBZnJCO3I9cnmjfcgsjB
	gy3vzEuhpj;
Authentication-Results: sj-dkim-2; header.From=ananth@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: =?iso-8859-1?Q?Alfred_H=CEnes?= <ah@tr-sys.de>, tcpm@ietf.org
Subject: Re: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org


I think we are losing context here. ( At this stage in the document we don'=
t need a rat-hole here) Alfred's point was :

" =

Furthermore, I once more advocate making clear in the document metadata wha=
t the document does, by adding to the heading:

    Updates: 793 (if approved)

Doing so will definitely help guide implementers to quickly locate the docu=
ment once published as an RFC.
By WG consensus, the document is intended for Standards Track, and Sections=
 3.2, 4.2, and 5.2 clearly state that they update RFC 793; thus, this shoul=
d be made visible at the metadata level as well.
"

The question is whether or not we should put that phrase in the front. =


-Anantha

> -----Original Message-----
> From: Joe Touch [mailto:touch@ISI.EDU] =

> Sent: Monday, September 29, 2008 10:28 AM
> To: Anantha Ramaiah (ananth)
> Cc: Lars Eggert; tcpm@ietf.org; Alfred H=CEnes; Mitesh Dalal =

> (mdalal); rrs@cisco.com
> Subject: Re: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
> =

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> =

> This has been the big issue with this doc from the beginning, =

> and I've been raising it from the beginning. Other docs =

> describe extensions to the protocol, but don't change the =

> base protocol. This one does, which has always been my =

> broadest concern.
> =

> It's a little odd to hear anyone think this is the first time =

> this was raised.
> =

> Joe
> =

> Anantha Ramaiah (ananth) wrote:
> > Lars,
> > =

> > Confused here. The TCP timestamps, SACK etc., are NOT =

> specified in RFC 793. Hence they don't update RFC 793 in any =

> sense, these are independent.
> > =

> > Now, RFC 2001 is a separate RFC by itself which was =

> obsoleted by RFC 2581. Yes, this is pretty close since this =

> talks about congestion control which is central to TCP, so =

> may be it updates some sections of RFC 793, I haven't taken a =

> close look.
> > =

> > Tcpsecure on the other hand does update the processing =

> rules of 793 ( pl see sections 3.2, 4.2, and 5.2), and hence =

> Alfred's point makes sense to me. =

> > FWIW, I never thought about this until Alfred brought this =

> point up, IMO, this is a good point.
> > =

> > -Anantha
> > =

> > -----Original Message-----
> > From: Lars Eggert [mailto:lars.eggert@nokia.com]
> > Sent: Monday, September 29, 2008 8:26 AM
> > To: Anantha Ramaiah (ananth)
> > Cc: Alfred H=CEnes; rrs@cisco.com; Mitesh Dalal (mdalal); =

> tcpm@ietf.org
> > Subject: Re: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
> > =

> > Hi,
> > =

> > (individual hat on)
> > =

> > On 2008-9-29, at 0:08, ext Anantha Ramaiah (ananth) wrote:
> >> In particular, regarding your observation of mentioning what the =

> >> document is doing, I agree that we should mention that it "updates =

> >> 793". I am hoping that nobody has any objection to this point.
> > =

> > since this document specifies an optional component to TCP, =

> I'd argue that it should not update RFC793. If you look at =

> the RFC Editor page, almost no other RFC updates RFC793, =

> because even widely-deployed extensions (timestamps, SACK, =

> etc.) are all optional. Even RFC2581 doesn't update RFC793.
> > =

> > Lars
> > _______________________________________________
> > tcpm mailing list
> > tcpm@ietf.org
> > https://www.ietf.org/mailman/listinfo/tcpm
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> =

> iEYEARECAAYFAkjhEAYACgkQE5f5cImnZrvhkgCfQMc0AP8JMGZqXgKhjNZ/LreG
> k7kAoM9M9JgpiYagxzrNjibrCR29fwCy
> =3DELvI
> -----END PGP SIGNATURE-----
> =

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Mon Sep 29 10:41:24 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8646B3A693C;
	Mon, 29 Sep 2008 10:41:24 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A84E03A6940
	for <tcpm@core3.amsl.com>; Mon, 29 Sep 2008 10:41:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.949
X-Spam-Level: 
X-Spam-Status: No, score=-5.949 tagged_above=-999 required=5 tests=[AWL=0.050, 
	BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id TEm4-XzBd5g9 for <tcpm@core3.amsl.com>;
	Mon, 29 Sep 2008 10:41:22 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id ADD173A6870
	for <tcpm@ietf.org>; Mon, 29 Sep 2008 10:41:22 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,333,1220227200"; d="scan'208";a="90502578"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-2.cisco.com with ESMTP; 29 Sep 2008 17:40:14 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m8THeEb2029558; 
	Mon, 29 Sep 2008 10:40:14 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m8THeE4U012868;
	Mon, 29 Sep 2008 17:40:14 GMT
Received: from xmb-sjc-21c.amer.cisco.com ([171.70.151.176]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 29 Sep 2008 10:40:13 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 29 Sep 2008 10:40:20 -0700
Message-ID: <0C53DCFB700D144284A584F54711EC5805DF4573@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <20080929160724.GD54282@zod.isi.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
Thread-Index: AckiTbQ1DN29m0SuSzOqa0zafBiSNwACugVA
References: <FE34F27F-8DDF-4C94-BC6E-E2ABF6000309@windriver.com>
	<B5A5E01F9387F4409E67604C0257C71E409513@NDJSEVS25A.ndc.nasa.gov>
	<24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>
	<20080906013831.GD2074@zod.isi.edu>
	<0C53DCFB700D144284A584F54711EC5805DF4359@xmb-sjc-21c.amer.cisco.com>
	<20080929160724.GD54282@zod.isi.edu>
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: "Ted Faber" <faber@ISI.EDU>
X-OriginalArrivalTime: 29 Sep 2008 17:40:13.0986 (UTC)
	FILETIME=[6DB6B020:01C9225A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1997; t=1222710014;
	x=1223574014; c=relaxed/simple; s=sjdkim1004;
	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[tcpm]=20WGLC=3A=20draft-ietf-tcpm-tcps
	ecure-10.txt |Sender:=20;
	bh=BEaRySDckt0ZtX9oVZoSbf5p6DnAKTJ6/lXWqeQ97AM=;
	b=I9CRIO++hoHwwwUx0laetgL+iFJuufjLcjvcivFKZcbMW0EepC6hqLLUAN
	iqJLO62ovMpki0a90VGO9UJbSP2HHcvkOdZiB2mUziXg3WpvSupWZvFDqMtB
	LA3qWlPvqW7vXf6y6EF4ogEwnvLlvGUeu8SsOq8hyjaBnlD5KgdmE=;
Authentication-Results: sj-dkim-1; header.From=ananth@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: rrs@cisco.com, tcpm@ietf.org, David Borman <david.borman@windriver.com>,
	"Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

> 
> The paragraph I'm commenting on reads:
> 
>    A third type of attack is also highlighted by both the RST and SYN
>    attacks.  It is also possible to inject data into a TCP 
> connection by
>    simply guessing a sequence number within the current receive window
>    of the victim.  The ACK value of any data segment is 
> considered valid
>    as long as it does not acknowledge data ahead of the next 
> segment to
>    send.  In other words an ACK value is acceptable if it is 
> ((SND.UNA-
>    (2^31-1)) <= SEG.ACK <= SND.NXT).  The (2^31 - 1) in the above
>    inequality takes into account the fact that comparisons on TCP
>    sequence and acknowledgement numbers is done using the 
> modulo 32 bit
>    arithmetic to accommodate the number wraparound.  This 
> means that an
>    attacker has to guess two ACK values with every guessed sequence
>    number so that the chances of successfully injecting data into a
>    connection are 1 in ((2^32 / RCV.WND) * 2).
> 
> I'm saying that, assuming the math is correct, that last 
> expression should be (2^33 / RCV.WND).  I didn't check the 
> math.  If you also believe the math is wrong, you have a 
> larger edit. :-)
> 
> On rereading the argument, it does sound like a data 
> injection attack should be harder by a factor of 2 and that 
> they multiplied by the wrong expression (2^32 rather than 
> 2^31).  So I think you're correct about the math, and if so 
> the final expression would be 2^32 / RCV.WND.
> 
> I'd be happier if someone else also looked at this paragraph 
> for technical accuracy.

I have updated the document with the correct math. I agree that it would
be nice if a few more folks take a look.

Thanks,
Anantha

> 
> --
> Ted Faber
> http://www.isi.edu/~faber           PGP: 
> http://www.isi.edu/~faber/pubkeys.asc
> Unexpected attachment on this mail? See 
> http://www.isi.edu/~faber/FAQ.html#SIG
> 
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Mon Sep 29 11:03:38 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E7A6528C0E0;
	Mon, 29 Sep 2008 11:03:38 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 113CC3A6AD8
	for <tcpm@core3.amsl.com>; Mon, 29 Sep 2008 11:03:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ImH+7pV0516B for <tcpm@core3.amsl.com>;
	Mon, 29 Sep 2008 11:03:37 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id 1D1E63A69ED
	for <tcpm@ietf.org>; Mon, 29 Sep 2008 11:03:37 -0700 (PDT)
Received: from [75.215.184.156] (156.sub-75-215-184.myvzw.com [75.215.184.156])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m8TI3ISN013519
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 29 Sep 2008 11:03:20 -0700 (PDT)
Message-ID: <48E11865.4070702@isi.edu>
Date: Mon, 29 Sep 2008 11:03:17 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
References: <FE34F27F-8DDF-4C94-BC6E-E2ABF6000309@windriver.com>	<B5A5E01F9387F4409E67604C0257C71E409513@NDJSEVS25A.ndc.nasa.gov>	<24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>	<20080906013831.GD2074@zod.isi.edu>	<0C53DCFB700D144284A584F54711EC5805DF4359@xmb-sjc-21c.amer.cisco.com>	<20080929160724.GD54282@zod.isi.edu>
	<0C53DCFB700D144284A584F54711EC5805DF4573@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <0C53DCFB700D144284A584F54711EC5805DF4573@xmb-sjc-21c.amer.cisco.com>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: David Borman <david.borman@windriver.com>, rrs@cisco.com, tcpm@ietf.org,
	Ted Faber <faber@ISI.EDU>, "Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Anantha Ramaiah (ananth) wrote:
...
> I have updated the document with the correct math. I agree that it would
> be nice if a few more folks take a look.

I (and the WG) checked the math in 4953; I don't expect to recheck the
math when it's re-trod (is there a reason the WG should?)

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

iEYEARECAAYFAkjhGGUACgkQE5f5cImnZrsrjQCfd/ecIOoMcppyIWAV0hJrDfGt
eooAoLzy2yEbnaupI+sxg7gtKxmJ7oRI
=0BlW
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Mon Sep 29 11:44:42 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B55A83A6872;
	Mon, 29 Sep 2008 11:44:42 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1EDFF3A6870
	for <tcpm@core3.amsl.com>; Mon, 29 Sep 2008 11:44:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 0YsNvxhcQSt8 for <tcpm@core3.amsl.com>;
	Mon, 29 Sep 2008 11:44:40 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by core3.amsl.com (Postfix) with ESMTP id 3BD133A6872
	for <tcpm@ietf.org>; Mon, 29 Sep 2008 11:44:40 -0700 (PDT)
Received: from zod.isi.edu (zod.isi.edu [128.9.168.221])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m8TIhT3A029008
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 29 Sep 2008 11:43:30 -0700 (PDT)
Received: (from faber@localhost)
	by zod.isi.edu (8.14.3/8.14.2/Submit) id m8TIhT2W049804;
	Mon, 29 Sep 2008 11:43:29 -0700 (PDT) (envelope-from faber)
Date: Mon, 29 Sep 2008 11:43:29 -0700
From: Ted Faber <faber@ISI.EDU>
To: Joe Touch <touch@ISI.EDU>
Message-ID: <20080929184328.GJ2292@zod.isi.edu>
References: <FE34F27F-8DDF-4C94-BC6E-E2ABF6000309@windriver.com>
	<B5A5E01F9387F4409E67604C0257C71E409513@NDJSEVS25A.ndc.nasa.gov>
	<24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>
	<20080906013831.GD2074@zod.isi.edu>
	<0C53DCFB700D144284A584F54711EC5805DF4359@xmb-sjc-21c.amer.cisco.com>
	<20080929160724.GD54282@zod.isi.edu>
	<0C53DCFB700D144284A584F54711EC5805DF4573@xmb-sjc-21c.amer.cisco.com>
	<48E11865.4070702@isi.edu>
Mime-Version: 1.0
In-Reply-To: <48E11865.4070702@isi.edu>
User-Agent: Mutt/1.4.2.3i
X-url: http://www.isi.edu/~faber
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: faber@zod.isi.edu
Cc: David Borman <david.borman@windriver.com>, rrs@cisco.com, tcpm@ietf.org,
	"Anantha Ramaiah \(ananth\)" <ananth@cisco.com>,
	"Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1857924137=="
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org


--===============1857924137==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="/0P/MvzTfyTu5j9Q"
Content-Disposition: inline


--/0P/MvzTfyTu5j9Q
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Sep 29, 2008 at 11:03:17AM -0700, Joe Touch wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
>=20
>=20
> Anantha Ramaiah (ananth) wrote:
> ...
> > I have updated the document with the correct math. I agree that it would
> > be nice if a few more folks take a look.
>=20
> I (and the WG) checked the math in 4953; I don't expect to recheck the
> math when it's re-trod (is there a reason the WG should?)

I don't see the calculations on P.13 of tcpsecure (i.e., data insertion
probabilities) in 4953.  Can you point out what I missed?

--=20
Ted Faber
http://www.isi.edu/~faber           PGP: http://www.isi.edu/~faber/pubkeys.=
asc
Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#=
SIG

--/0P/MvzTfyTu5j9Q
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkjhIdAACgkQaUz3f+Zf+XvBPQCg+VxHo33md9JjveHxuFc+hpIP
RcUAn18d8U69Exk/PL7Asn2wXIV/dUTu
=oHFF
-----END PGP SIGNATURE-----

--/0P/MvzTfyTu5j9Q--

--===============1857924137==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm

--===============1857924137==--


From tcpm-bounces@ietf.org  Mon Sep 29 13:15:24 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A3E0E28C0F0;
	Mon, 29 Sep 2008 13:15:24 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 70B1A3A69BD
	for <tcpm@core3.amsl.com>; Mon, 29 Sep 2008 13:15:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id xI+XBjfmgMat for <tcpm@core3.amsl.com>;
	Mon, 29 Sep 2008 13:15:22 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id B3D2328C10E
	for <tcpm@ietf.org>; Mon, 29 Sep 2008 13:15:22 -0700 (PDT)
Received: from [75.215.184.156] (156.sub-75-215-184.myvzw.com [75.215.184.156])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m8TKExWF002254
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 29 Sep 2008 13:15:02 -0700 (PDT)
Message-ID: <48E13743.6090401@isi.edu>
Date: Mon, 29 Sep 2008 13:14:59 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Ted Faber <faber@ISI.EDU>
References: <FE34F27F-8DDF-4C94-BC6E-E2ABF6000309@windriver.com>
	<B5A5E01F9387F4409E67604C0257C71E409513@NDJSEVS25A.ndc.nasa.gov>
	<24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>
	<20080906013831.GD2074@zod.isi.edu>
	<0C53DCFB700D144284A584F54711EC5805DF4359@xmb-sjc-21c.amer.cisco.com>
	<20080929160724.GD54282@zod.isi.edu>
	<0C53DCFB700D144284A584F54711EC5805DF4573@xmb-sjc-21c.amer.cisco.com>
	<48E11865.4070702@isi.edu> <20080929184328.GJ2292@zod.isi.edu>
In-Reply-To: <20080929184328.GJ2292@zod.isi.edu>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: David Borman <david.borman@windriver.com>, rrs@cisco.com, tcpm@ietf.org,
	"Anantha Ramaiah \(ananth\)" <ananth@cisco.com>,
	"Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Ted Faber wrote:
> On Mon, Sep 29, 2008 at 11:03:17AM -0700, Joe Touch wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>>
>>
>> Anantha Ramaiah (ananth) wrote:
>> ...
>>> I have updated the document with the correct math. I agree that it would
>>> be nice if a few more folks take a look.
>> I (and the WG) checked the math in 4953; I don't expect to recheck the
>> math when it's re-trod (is there a reason the WG should?)
> 
> I don't see the calculations on P.13 of tcpsecure (i.e., data insertion
> probabilities) in 4953.  Can you point out what I missed?

I was talking about section 1.3 on page 6 of tcpsecure, which is
redundant with 4953. Section 5.1 is different.

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

iEYEARECAAYFAkjhN0MACgkQE5f5cImnZruk3ACg+rgzSQaGEvmWwC6JN12OzGYW
QtwAn2/suHW9CghKR/1+xTE5SF8e1fFc
=O8Sm
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Mon Sep 29 14:19:47 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5B79328C128;
	Mon, 29 Sep 2008 14:19:47 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4E52528C114
	for <tcpm@core3.amsl.com>; Mon, 29 Sep 2008 14:19:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level: 
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 78j4uQNSCA7b for <tcpm@core3.amsl.com>;
	Mon, 29 Sep 2008 14:19:45 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by core3.amsl.com (Postfix) with ESMTP id 5ED2028C10E
	for <tcpm@ietf.org>; Mon, 29 Sep 2008 14:19:45 -0700 (PDT)
Received: from zod.isi.edu (zod.isi.edu [128.9.168.221])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m8TLJbME007685
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 29 Sep 2008 14:19:38 -0700 (PDT)
Received: (from faber@localhost)
	by zod.isi.edu (8.14.3/8.14.2/Submit) id m8TLJaZP057079;
	Mon, 29 Sep 2008 14:19:36 -0700 (PDT) (envelope-from faber)
Date: Mon, 29 Sep 2008 14:19:36 -0700
From: Ted Faber <faber@ISI.EDU>
To: Joe Touch <touch@ISI.EDU>
Message-ID: <20080929211936.GA53379@zod.isi.edu>
References: <FE34F27F-8DDF-4C94-BC6E-E2ABF6000309@windriver.com>
	<B5A5E01F9387F4409E67604C0257C71E409513@NDJSEVS25A.ndc.nasa.gov>
	<24D2F5D3-93E7-4B64-BA96-2086F3E5754E@windriver.com>
	<20080906013831.GD2074@zod.isi.edu>
	<0C53DCFB700D144284A584F54711EC5805DF4359@xmb-sjc-21c.amer.cisco.com>
	<20080929160724.GD54282@zod.isi.edu>
	<0C53DCFB700D144284A584F54711EC5805DF4573@xmb-sjc-21c.amer.cisco.com>
	<48E11865.4070702@isi.edu> <20080929184328.GJ2292@zod.isi.edu>
	<48E13743.6090401@isi.edu>
Mime-Version: 1.0
In-Reply-To: <48E13743.6090401@isi.edu>
User-Agent: Mutt/1.4.2.3i
X-url: http://www.isi.edu/~faber
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: faber@zod.isi.edu
Cc: David Borman <david.borman@windriver.com>, rrs@cisco.com, tcpm@ietf.org,
	"Anantha Ramaiah \(ananth\)" <ananth@cisco.com>,
	"Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>
Subject: Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0768946691=="
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org


--===============0768946691==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="AqsLC8rIMeq19msA"
Content-Disposition: inline


--AqsLC8rIMeq19msA
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Sep 29, 2008 at 01:14:59PM -0700, Joe Touch wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
>=20
>=20
> Ted Faber wrote:
> > On Mon, Sep 29, 2008 at 11:03:17AM -0700, Joe Touch wrote:
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >>
> >>
> >>
> >> Anantha Ramaiah (ananth) wrote:
> >> ...
> >>> I have updated the document with the correct math. I agree that it wo=
uld
> >>> be nice if a few more folks take a look.
> >> I (and the WG) checked the math in 4953; I don't expect to recheck the
> >> math when it's re-trod (is there a reason the WG should?)
> >=20
> > I don't see the calculations on P.13 of tcpsecure (i.e., data insertion
> > probabilities) in 4953.  Can you point out what I missed?
>=20
> I was talking about section 1.3 on page 6 of tcpsecure, which is
> redundant with 4953. Section 5.1 is different.

Different thread then, this one's about the example on p. 13. :-)

--=20
Ted Faber
http://www.isi.edu/~faber           PGP: http://www.isi.edu/~faber/pubkeys.=
asc
Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#=
SIG

--AqsLC8rIMeq19msA
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkjhRmgACgkQaUz3f+Zf+XuhlQCgjref6AC3LtY1sv4GGPj8uED/
yr8An1dkax0VlxAg3aXKlXX1bUMsLXzP
=Xdok
-----END PGP SIGNATURE-----

--AqsLC8rIMeq19msA--

--===============0768946691==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm

--===============0768946691==--


From tcpm-bounces@ietf.org  Mon Sep 29 14:58:21 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 420203A6B72;
	Mon, 29 Sep 2008 14:58:21 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 289F33A69DF
	for <tcpm@core3.amsl.com>; Mon, 29 Sep 2008 14:58:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id sq7JHxHYBtej for <tcpm@core3.amsl.com>;
	Mon, 29 Sep 2008 14:58:19 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by core3.amsl.com (Postfix) with ESMTP id 476B03A6896
	for <tcpm@ietf.org>; Mon, 29 Sep 2008 14:58:19 -0700 (PDT)
Received: from zod.isi.edu (zod.isi.edu [128.9.168.221])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m8TLuiTX022181
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 29 Sep 2008 14:56:45 -0700 (PDT)
Received: (from faber@localhost)
	by zod.isi.edu (8.14.3/8.14.2/Submit) id m8TLui5s058675;
	Mon, 29 Sep 2008 14:56:44 -0700 (PDT) (envelope-from faber)
Date: Mon, 29 Sep 2008 14:56:44 -0700
From: Ted Faber <faber@ISI.EDU>
To: David Borman <david.borman@windriver.com>
Message-ID: <20080929215644.GB53379@zod.isi.edu>
References: <53797EED-2C93-4E20-AF60-E3C0EF8F85AC@windriver.com>
Mime-Version: 1.0
In-Reply-To: <53797EED-2C93-4E20-AF60-E3C0EF8F85AC@windriver.com>
User-Agent: Mutt/1.4.2.3i
X-url: http://www.isi.edu/~faber
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: faber@zod.isi.edu
Cc: tcpm@ietf.org, "Anantha Ramaiah \(ananth\)" <ananth@cisco.com>,
	mbashyam@ocarinanetworks.com
Subject: Re: [tcpm] draft-ananth-tcpm-persist-00.txt as a WG document
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2101961663=="
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org


--===============2101961663==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="VrqPEDrXMn8OVzN4"
Content-Disposition: inline


--VrqPEDrXMn8OVzN4
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Sep 26, 2008 at 02:37:52PM -0500, David Borman wrote:
> At Dublin a presentation was made on draft-ananth-tcpm-=20
> persist-00.txt.  Not a lot of people had read the document at the time =
=20
> of the presentation, but there didn't seem to be any objections to =20
> adopting it as a TCPM WG document.

I guess I don't have a strong objection to it in that I believe it's
technically correct, but I'm not sure I see a driving need for it.  I
worry that we're taking work from more pressing tasks.

--=20
Ted Faber
http://www.isi.edu/~faber           PGP: http://www.isi.edu/~faber/pubkeys.=
asc
Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#=
SIG

--VrqPEDrXMn8OVzN4
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkjhTxwACgkQaUz3f+Zf+Xs7KwCgiyrmgqg0mEL0uDzyJEBhjHoJ
81gAoMemUIY4SlUJFDHPhqZ9vclPGy/g
=4Cd6
-----END PGP SIGNATURE-----

--VrqPEDrXMn8OVzN4--

--===============2101961663==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm

--===============2101961663==--


From tcpm-bounces@ietf.org  Mon Sep 29 15:44:44 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6BD9F3A6B78;
	Mon, 29 Sep 2008 15:44:44 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4446E3A6B7C
	for <tcpm@core3.amsl.com>; Mon, 29 Sep 2008 15:44:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.499
X-Spam-Level: 
X-Spam-Status: No, score=-3.499 tagged_above=-999 required=5 tests=[AWL=0.100, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 8lJvUeuThvoI for <tcpm@core3.amsl.com>;
	Mon, 29 Sep 2008 15:44:42 -0700 (PDT)
Received: from mail.wrs.com (mail.windriver.com [147.11.1.11])
	by core3.amsl.com (Postfix) with ESMTP id 23E543A6AEB
	for <tcpm@ietf.org>; Mon, 29 Sep 2008 15:44:41 -0700 (PDT)
Received: from ALA-MAIL03.corp.ad.wrs.com (ala-mail03 [147.11.57.144])
	by mail.wrs.com (8.13.6/8.13.6) with ESMTP id m8TMir8M005144;
	Mon, 29 Sep 2008 15:44:53 -0700 (PDT)
Received: from ala-mail06.corp.ad.wrs.com ([147.11.57.147]) by
	ALA-MAIL03.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 29 Sep 2008 15:44:53 -0700
Received: from dab-restive.wrs.com ([192.168.117.73]) by
	ala-mail06.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 29 Sep 2008 15:44:52 -0700
Message-Id: <26E7B0F8-D0E7-4C3D-B51D-EA89B2045BAC@windriver.com>
From: David Borman <david.borman@windriver.com>
To: Joe Touch <touch@isi.edu>
In-Reply-To: <48DD62F8.3080708@isi.edu>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 29 Sep 2008 17:44:51 -0500
References: <53797EED-2C93-4E20-AF60-E3C0EF8F85AC@windriver.com>
	<48DD62F8.3080708@isi.edu>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 29 Sep 2008 22:44:53.0083 (UTC)
	FILETIME=[FCE78AB0:01C92284]
Cc: tcpm@ietf.org, "Anantha Ramaiah \(ananth\)" <ananth@cisco.com>,
	mbashyam@ocarinanetworks.com
Subject: Re: [tcpm] draft-ananth-tcpm-persist-00.txt as a WG document
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

(WG co-chair hat on)

Its intended status is informational, so it isn't a protocol  
document.  The purpose is clarification of what the standards already  
say. Clarification of confusion is part of maintenance, even if the  
clarification is not needed by everyone.

(WG co-chair hat off)

I was one of the people pointing out that the implementation is  
separate from the protocol, and that though the protocol says that TCP  
must not abort connections in persist state, in the implementation the  
other parts of the OS or the application can abort a TCP connection at  
any time, which includes connections in persist state.  If this  
document helps to make that clearer for some implementors, then that  
is a good thing.

		-David

On Sep 26, 2008, at 5:32 PM, Joe Touch wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Dave,
>
> I'm not sure any of us disagreed with the content. The question is
> whether it's important, useful, or necessary (in that order) to  
> address
> this, or whether we feel that the existing specs are sufficient.
>
> My conclusion was that applications can always terminate TCP
> connections, and so can OS's - e.g., an OS can always just reboot.
>
> This still sounds like an implementation guideline to me. It may be
> useful, and may be useful to document, but since it's implementation
> focused, I'm not sure I see it as a protocol document.
>
> As a result, I don't think this needs to be a WG document (which is
> where I thought things were from Dublin). We talked there about it
> potentially being an errata to 1122, and even the problems with that
> approach.
>
> Finally, it is not clear this is even in scope - it's not a  
> modification
> to TCP, nor is it maintenance.
>
> Joe
>
> David Borman wrote:
>> At Dublin a presentation was made on draft-ananth-tcpm- 
>> persist-00.txt.
>> Not a lot of people had read the document at the time of the
>> presentation, but there didn't seem to be any objections to  
>> adopting it
>> as a TCPM WG document.
>>
>> The authors posted a summary to the mailing list, have responded to  
>> all
>> issues that were raised, and have a new version of the document ready
>> for publication.  We (Wes and I) feel that there is support for  
>> adopting
>> this as a WG document, but as always, we need to verify this on the
>> mailing list.  So, if you have any objections to adopting this as a  
>> WG
>> document, please speak up now.  Also speak up if you support  
>> adopting it
>> as a WG document.
>>
>> I'll be the first to say I support adopting this as a WG document.   
>> If
>> there are no serious objections, the authors can submit their updated
>> version next week and Wes and I will add it to our list of WG  
>> documents.
>>
>>            -David Borman, TCPM WG co-chair
>>
>> _______________________________________________
>> tcpm mailing list
>> tcpm@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcpm
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkjdYvgACgkQE5f5cImnZrsMrACfTV5Bl9beeAJ29JDszVT6sVhY
> XQAAoN8VPIAizeB1Z+IgkD/6iwT1h+HP
> =jSx6
> -----END PGP SIGNATURE-----

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Mon Sep 29 16:16:49 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 166773A6B6B;
	Mon, 29 Sep 2008 16:16:49 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8677D3A6AF3
	for <tcpm@core3.amsl.com>; Mon, 29 Sep 2008 16:16:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 0jN-AQpOPAwz for <tcpm@core3.amsl.com>;
	Mon, 29 Sep 2008 16:16:46 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id ADEAB3A6AEB
	for <tcpm@ietf.org>; Mon, 29 Sep 2008 16:16:46 -0700 (PDT)
Received: from [192.168.1.45] (pool-71-106-119-240.lsanca.dsl-w.verizon.net
	[71.106.119.240])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m8TNGmmI006784
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 29 Sep 2008 16:16:50 -0700 (PDT)
Message-ID: <48E161E0.6050808@isi.edu>
Date: Mon, 29 Sep 2008 16:16:48 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: David Borman <david.borman@windriver.com>
References: <53797EED-2C93-4E20-AF60-E3C0EF8F85AC@windriver.com>
	<48DD62F8.3080708@isi.edu>
	<26E7B0F8-D0E7-4C3D-B51D-EA89B2045BAC@windriver.com>
In-Reply-To: <26E7B0F8-D0E7-4C3D-B51D-EA89B2045BAC@windriver.com>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tcpm@ietf.org, "Anantha Ramaiah \(ananth\)" <ananth@cisco.com>,
	mbashyam@ocarinanetworks.com
Subject: Re: [tcpm] draft-ananth-tcpm-persist-00.txt as a WG document
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David,

I agree overall with your observations; information seems reasonable,
but it also seems like clarification of existing standards is a TSVWG
issue, not a TCPM issue.

Joe

David Borman wrote:
> (WG co-chair hat on)
> 
> Its intended status is informational, so it isn't a protocol document. 
> The purpose is clarification of what the standards already say.
> Clarification of confusion is part of maintenance, even if the
> clarification is not needed by everyone.
> 
> (WG co-chair hat off)
> 
> I was one of the people pointing out that the implementation is separate
> from the protocol, and that though the protocol says that TCP must not
> abort connections in persist state, in the implementation the other
> parts of the OS or the application can abort a TCP connection at any
> time, which includes connections in persist state.  If this document
> helps to make that clearer for some implementors, then that is a good
> thing.
> 
>         -David
> 
> On Sep 26, 2008, at 5:32 PM, Joe Touch wrote:
> 
> Dave,
> 
> I'm not sure any of us disagreed with the content. The question is
> whether it's important, useful, or necessary (in that order) to address
> this, or whether we feel that the existing specs are sufficient.
> 
> My conclusion was that applications can always terminate TCP
> connections, and so can OS's - e.g., an OS can always just reboot.
> 
> This still sounds like an implementation guideline to me. It may be
> useful, and may be useful to document, but since it's implementation
> focused, I'm not sure I see it as a protocol document.
> 
> As a result, I don't think this needs to be a WG document (which is
> where I thought things were from Dublin). We talked there about it
> potentially being an errata to 1122, and even the problems with that
> approach.
> 
> Finally, it is not clear this is even in scope - it's not a modification
> to TCP, nor is it maintenance.
> 
> Joe
> 
> David Borman wrote:
>>>> At Dublin a presentation was made on draft-ananth-tcpm-persist-00.txt.
>>>> Not a lot of people had read the document at the time of the
>>>> presentation, but there didn't seem to be any objections to adopting it
>>>> as a TCPM WG document.
>>>>
>>>> The authors posted a summary to the mailing list, have responded to all
>>>> issues that were raised, and have a new version of the document ready
>>>> for publication.  We (Wes and I) feel that there is support for adopting
>>>> this as a WG document, but as always, we need to verify this on the
>>>> mailing list.  So, if you have any objections to adopting this as a WG
>>>> document, please speak up now.  Also speak up if you support adopting it
>>>> as a WG document.
>>>>
>>>> I'll be the first to say I support adopting this as a WG document.  If
>>>> there are no serious objections, the authors can submit their updated
>>>> version next week and Wes and I will add it to our list of WG documents.
>>>>
>>>>            -David Borman, TCPM WG co-chair
>>>>
>>>> _______________________________________________
>>>> tcpm mailing list
>>>> tcpm@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/tcpm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkjhYeAACgkQE5f5cImnZruu8QCgiDEcz+oayPXE0i8673R4rXxh
QDsAoMOmijUSrLPkpNpL+GZgreo1LuW8
=i3kh
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Mon Sep 29 17:27:46 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3E6A83A6B93;
	Mon, 29 Sep 2008 17:27:46 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E933A3A6B93
	for <tcpm@core3.amsl.com>; Mon, 29 Sep 2008 17:27:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id f02swyXmEDLR for <tcpm@core3.amsl.com>;
	Mon, 29 Sep 2008 17:27:44 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by core3.amsl.com (Postfix) with ESMTP id 1EABF3A6B91
	for <tcpm@ietf.org>; Mon, 29 Sep 2008 17:27:44 -0700 (PDT)
Received: from zod.isi.edu (zod.isi.edu [128.9.168.221])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m8U0Rg3Z022924
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 29 Sep 2008 17:27:43 -0700 (PDT)
Received: (from faber@localhost)
	by zod.isi.edu (8.14.3/8.14.2/Submit) id m8U0RgBp071613;
	Mon, 29 Sep 2008 17:27:42 -0700 (PDT) (envelope-from faber)
Date: Mon, 29 Sep 2008 17:27:42 -0700
From: Ted Faber <faber@ISI.EDU>
To: Joe Touch <touch@ISI.EDU>
Message-ID: <20080930002742.GA71473@zod.isi.edu>
References: <53797EED-2C93-4E20-AF60-E3C0EF8F85AC@windriver.com>
	<48DD62F8.3080708@isi.edu>
	<26E7B0F8-D0E7-4C3D-B51D-EA89B2045BAC@windriver.com>
	<48E161E0.6050808@isi.edu>
Mime-Version: 1.0
In-Reply-To: <48E161E0.6050808@isi.edu>
User-Agent: Mutt/1.4.2.3i
X-url: http://www.isi.edu/~faber
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: faber@zod.isi.edu
Cc: "Anantha Ramaiah \(ananth\)" <ananth@cisco.com>, tcpm@ietf.org,
	David Borman <david.borman@windriver.com>, mbashyam@ocarinanetworks.com
Subject: Re: [tcpm] draft-ananth-tcpm-persist-00.txt as a WG document
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0022501855=="
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org


--===============0022501855==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="EeQfGwPcQSOJBaQU"
Content-Disposition: inline


--EeQfGwPcQSOJBaQU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Sep 29, 2008 at 04:16:48PM -0700, Joe Touch wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> David,
>=20
> I agree overall with your observations; information seems reasonable,
> but it also seems like clarification of existing standards is a TSVWG
> issue, not a TCPM issue.

FWIW, I disagree.  TCPM exists to offload TCP actions from TSVWG,
including informational ones.

--=20
Ted Faber
http://www.isi.edu/~faber           PGP: http://www.isi.edu/~faber/pubkeys.=
asc
Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#=
SIG

--EeQfGwPcQSOJBaQU
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkjhcn4ACgkQaUz3f+Zf+XtykgCfXGyOl6QQAMhfT6fU0ETiCAXD
Um8AoPu8KCWgBrfcXtDBIo1+1BBqhXER
=jao0
-----END PGP SIGNATURE-----

--EeQfGwPcQSOJBaQU--

--===============0022501855==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm

--===============0022501855==--


From tcpm-bounces@ietf.org  Mon Sep 29 21:24:58 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C58783A68B5;
	Mon, 29 Sep 2008 21:24:58 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B5BF13A6974
	for <tcpm@core3.amsl.com>; Mon, 29 Sep 2008 21:24:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.202
X-Spam-Level: 
X-Spam-Status: No, score=-5.202 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 95TktotrElpx for <tcpm@core3.amsl.com>;
	Mon, 29 Sep 2008 21:24:56 -0700 (PDT)
Received: from ndmsnpf02.ndc.nasa.gov (ndmsnpf02.ndc.nasa.gov [198.117.0.122])
	by core3.amsl.com (Postfix) with ESMTP id 9E38A3A68B5
	for <tcpm@ietf.org>; Mon, 29 Sep 2008 21:24:56 -0700 (PDT)
Received: from ndjsppt03.ndc.nasa.gov (ndjsppt03.ndc.nasa.gov [198.117.1.102])
	by ndmsnpf02.ndc.nasa.gov (Postfix) with ESMTP id B8F237A1A2;
	Mon, 29 Sep 2008 23:25:10 -0500 (CDT)
Received: from ndjsxgw03.ndc.nasa.gov (ndjsxgw03.ndc.nasa.gov [129.166.32.111])
	by ndjsppt03.ndc.nasa.gov (8.14.1/8.14.1) with ESMTP id m8U4P9rj019009; 
	Mon, 29 Sep 2008 23:25:09 -0500
Received: from NDJSEVS25A.ndc.nasa.gov ([129.166.32.124]) by
	ndjsxgw03.ndc.nasa.gov with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 29 Sep 2008 23:25:11 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 29 Sep 2008 23:25:10 -0500
Message-ID: <B5A5E01F9387F4409E67604C0257C71E0991C8@NDJSEVS25A.ndc.nasa.gov>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcpm] draft-ananth-tcpm-persist-00.txt as a WG document
Thread-Index: AckihQdHudyMWFA4TMCB0PC/1aEl4wALmbAL
References: <53797EED-2C93-4E20-AF60-E3C0EF8F85AC@windriver.com><48DD62F8.3080708@isi.edu>
	<26E7B0F8-D0E7-4C3D-B51D-EA89B2045BAC@windriver.com>
From: "Eddy, Wesley M. (GRC-RCN0)[VZ]" <Wesley.M.Eddy@nasa.gov>
To: "David Borman" <david.borman@windriver.com>, "Joe Touch" <touch@isi.edu>
X-OriginalArrivalTime: 30 Sep 2008 04:25:11.0035 (UTC)
	FILETIME=[86F3C4B0:01C922B4]
Cc: tcpm@ietf.org, "Anantha Ramaiah \(ananth\)" <ananth@cisco.com>,
	mbashyam@ocarinanetworks.com
Subject: Re: [tcpm] draft-ananth-tcpm-persist-00.txt as a WG document
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1627835457=="
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1627835457==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C922B4.86AF19BA"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C922B4.86AF19BA
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

As an individual, not a co-chair, it's my hope that part of "TCP =
maintenance" would include clarifying questions that implementers are =
bringing when it's legitimately the case that the original specification =
can be viewed as unclear or missing some commentary.  Amazingly, there =
are still new TCP implementations being written in 2008, and likely into =
the future, so it may prove useful.
=20
My personal feeling is that the content of this particular draft is so =
easy to agree on (nobody has objected to it, at least), that it should =
ideally be very quick and easy to make a few editorial passes on it and =
and call it done.  It would probably take less time than debating over =
whether it's absolutely undeniably necessary or what WG it belongs to =
:).  As for where the work should be done, if it is done, I agree with =
Ted that TCPM exists to offload work from the RSVP maintenance and minor =
extensions working group aka TSVWG.
=20
=20

------_=_NextPart_001_01C922B4.86AF19BA
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>Re: [tcpm] draft-ananth-tcpm-persist-00.txt =
as a WG document</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.6001.18099" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText13801 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT size=3D2>As an individual, not a co-chair, it's my =
hope that part of "TCP maintenance" would include clarifying questions =
that implementers are bringing when it's legitimately the case that the =
original specification can be viewed as unclear or missing some =
commentary.&nbsp; Amazingly, there are still new TCP implementations =
being written in 2008, and likely into the future, so it may prove =
useful.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2>My personal feeling is that the content of =
this particular draft is so easy to agree on (nobody has objected to it, =
at least), that it should ideally&nbsp;be very quick and easy to make a =
few editorial passes on it and and call it done.&nbsp; It would probably =
take less time than debating over whether it's absolutely undeniably =
necessary&nbsp;or what WG it belongs to :).&nbsp; As for where the work =
should be done, if it is done, I agree with Ted that TCPM exists to =
offload work from the RSVP maintenance and minor extensions working =
group aka TSVWG.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2></FONT>&nbsp;</DIV></DIV></BODY></HTML>
------_=_NextPart_001_01C922B4.86AF19BA--

--===============1627835457==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm

--===============1627835457==--


From tcpm-bounces@ietf.org  Mon Sep 29 23:10:58 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 18EC93A6783;
	Mon, 29 Sep 2008 23:10:58 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 414393A6783
	for <tcpm@core3.amsl.com>; Mon, 29 Sep 2008 23:10:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id e7334CrKcxCz for <tcpm@core3.amsl.com>;
	Mon, 29 Sep 2008 23:10:51 -0700 (PDT)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31])
	by core3.amsl.com (Postfix) with ESMTP id C53CF3A6452
	for <tcpm@ietf.org>; Mon, 29 Sep 2008 23:10:50 -0700 (PDT)
Received: by yw-out-2324.google.com with SMTP id 3so393588ywj.49
	for <tcpm@ietf.org>; Mon, 29 Sep 2008 23:10:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references;
	bh=lHTz1PDkRKNLrDPeQQ7SIO+kRU+aFr10YsC8MHrXT7M=;
	b=eHdI0Wx+CKbveUR1w1trQBCy9KD56aDQssca81P2+o8tKGIrepPaGO8GJmcN7vjGQe
	cBayXBnCsvRdHfjWkS87ZI8akVAhXDF/zvtwqJbN1DpjTj0sfif0IqHDeHt042HKnOGY
	Jlci045PpkhQuAqKMw4dvkBn6J6/fhoWRpngs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=AM8OVt5vomTw0y2J2jliGFXadb0CQut1ZZ7pqLi2kTPkSXsUHh9L4U3jEnbs4xTFOq
	AZq49yEQ1idpRoUIEWOpIBaP9fpBk5zSwFuFtNE4gDgLzJTFuJq1z7jGHEoLX3rrFd5F
	DSqiF3FC/+VgEzywer5Zyttix/xx/UXbTnV7I=
Received: by 10.100.177.15 with SMTP id z15mr5428822ane.124.1222755001871;
	Mon, 29 Sep 2008 23:10:01 -0700 (PDT)
Received: by 10.100.140.4 with HTTP; Mon, 29 Sep 2008 23:10:01 -0700 (PDT)
Message-ID: <1e41a3230809292310o591b7f98l5048083b9e0966f2@mail.gmail.com>
Date: Mon, 29 Sep 2008 23:10:01 -0700
From: "John Heffner" <johnwheffner@gmail.com>
To: "David Borman" <david.borman@windriver.com>
In-Reply-To: <53797EED-2C93-4E20-AF60-E3C0EF8F85AC@windriver.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <53797EED-2C93-4E20-AF60-E3C0EF8F85AC@windriver.com>
Cc: tcpm@ietf.org, "Anantha Ramaiah \(ananth\)" <ananth@cisco.com>,
	mbashyam@ocarinanetworks.com
Subject: Re: [tcpm] draft-ananth-tcpm-persist-00.txt as a WG document
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

On Fri, Sep 26, 2008 at 12:37 PM, David Borman
<david.borman@windriver.com> wrote:
> At Dublin a presentation was made on draft-ananth-tcpm-persist-00.txt.  Not
> a lot of people had read the document at the time of the presentation, but
> there didn't seem to be any objections to adopting it as a TCPM WG document.
>
> The authors posted a summary to the mailing list, have responded to all
> issues that were raised, and have a new version of the document ready for
> publication.  We (Wes and I) feel that there is support for adopting this as
> a WG document, but as always, we need to verify this on the mailing list.
>  So, if you have any objections to adopting this as a WG document, please
> speak up now.  Also speak up if you support adopting it as a WG document.
>
> I'll be the first to say I support adopting this as a WG document.  If there
> are no serious objections, the authors can submit their updated version next
> week and Wes and I will add it to our list of WG documents.


I have reservations about moving forward with this draft as a wg
document.  While the information is technically correct, it is overly
specific to the point of possibly being misleading rather than
clarifying.  An operating system may terminate a tcp connection at any
time, not just when the connection is in the persist state.  Further,
I would actually argue that terminating a connection *because* it's in
the persist state is a bad idea and should be discouraged.  (The
reason for termination should be for its use of resources, not TCP's
state.)

  -John
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Tue Sep 30 02:43:54 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2CBD43A67C1;
	Tue, 30 Sep 2008 02:43:54 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1DF593A67C1
	for <tcpm@core3.amsl.com>; Tue, 30 Sep 2008 02:43:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.475
X-Spam-Level: 
X-Spam-Status: No, score=-6.475 tagged_above=-999 required=5 tests=[AWL=0.124, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Sz6hGZfwlSOQ for <tcpm@core3.amsl.com>;
	Tue, 30 Sep 2008 02:43:52 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230])
	by core3.amsl.com (Postfix) with ESMTP id ECAEA3A67B4
	for <tcpm@ietf.org>; Tue, 30 Sep 2008 02:43:51 -0700 (PDT)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m8U9hLXO009942; Tue, 30 Sep 2008 12:43:27 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 30 Sep 2008 12:43:15 +0300
Received: from net.118.nrpn.net ([10.241.184.208]) by esebh102.NOE.Nokia.com
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 30 Sep 2008 12:43:12 +0300
Message-Id: <724ED3DF-B4E5-4FF8-93BF-5B84688CC940@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
To: ext Joe Touch <touch@ISI.EDU>
In-Reply-To: <48E110DE.8050903@isi.edu>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Tue, 30 Sep 2008 12:43:10 +0300
References: <200808140650.IAA05627@TR-Sys.de>	<0C53DCFB700D144284A584F54711EC5805DF435A@xmb-sjc-21c.amer.cisco.com>
	<B35986E6-D8D7-4A9E-B8AB-3DB2E5C3FA29@nokia.com>
	<48E110DE.8050903@isi.edu>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 30 Sep 2008 09:43:13.0589 (UTC)
	FILETIME=[F50A6E50:01C922E0]
X-Nokia-AV: Clean
Cc: =?ISO-8859-1?Q?Alfred_H=CEnes?= <ah@tr-sys.de>, tcpm@ietf.org,
	"ext Anantha Ramaiah \(ananth\)" <ananth@cisco.com>,
	rrs@cisco.com, "Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>
Subject: Re: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0775758718=="
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org


--===============0775758718==
Content-Type: multipart/signed; boundary=Apple-Mail-1--352545528; micalg=sha1; protocol="application/pkcs7-signature"


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

Hi,

(individual hat on)

On 2008-9-29, at 20:31, ext Joe Touch wrote:
> Is it possible that a SHOULD isn't considered a "updates"?

RFC2119 language has nothing to do with the "updates" relationship.  
It's the applicability that matters.

"Updates 793" on document X means "if you implement 793 you also need  
to implement X". That is, because "updates" is typically used when a  
new document fixes critical bugs in an existing specification or adds  
mandatory new functionality.

For this document the applicability statement is basically "SHOULD  
implement when vulnerable, MAY otherwise". That's a conditional  
"updates". Unfortunately, the "updates" header isn't expressive enough  
to convey this.

We're left with two less-than-optimal choices: Add "updates 793",  
which doesn't capture the conditional expressed by the applicability  
statement, or omit "updates 793", which is also inaccurate.

My reason for suggesting to omit the "updates" - and this is a  
personal preference, I'll respect the WG decision and would like to  
head other opinions - is that a plain "updates 793" looks like a "you  
must implement this when implementing 793", and we had a long  
discussion around the applicability statement that seemed to indicate  
that the WG didn't want to make this blanket recommendation.

Lars

PS: As an example, look at the recent RFC5348, which is TFRC. It  
obsoletes RFC3448 (which was the old version of TFRC) but it also  
updates RFC4342 (DCCP's CCID3), which implements TFRC inside DCCP. The  
"updates" relationship here means that CCID3 implementations must now  
(also) implement RFC5348, i.e., the new version of TFRC.
--Apple-Mail-1--352545528
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIC/TCCAvkw
ggJioAMCAQICEFcKn6uMJyFYm3ow9AwDVo0wDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ
ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA3MTEyMDA4NTMyMloXDTA4MTExOTA4NTMy
MlowXDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVnZ2Vy
dDEkMCIGCSqGSIb3DQEJARYVbGFycy5lZ2dlcnRAbm9raWEuY29tMIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEAxx0rd8E8VV2l2Y/zV2buSRcCWScJwDJc8moZY88N1Hla1CMhh83tIPQN
pukkPE6GMIJjferzgTV8extFAd6jrk96U6HJLXF/xzxKX/U3ksT/rwyLCO8l9T8OwNtmjWjMwn0Y
1f4V5JnXLyZDz97BaN2rnJjccSIYuDJLXPzaTE3kxYe7j35iIgyaqhLYs3dERHOOJpiuWhHOj45C
m/4hCWiSEtwabUtufw232z2r4tExOXuxH8OJtbbJxmf/tb+/m5pNRQbKl1KWbFlLqeojqgrG56jx
uxNDfMaTNHfygPea8LGjzrE0Ck3lqUYXD2/dk45Y8lJAAhFQ3erCwMw1XwIDAQABozIwMDAgBgNV
HREEGTAXgRVsYXJzLmVnZ2VydEBub2tpYS5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUF
AAOBgQBGcuNVdbuBMUyXaAiENyTmsKPOwd/PJOI540ONxvVyGtycdaMMlUL+tz/Qcznv/hnqN7u2
NqrvBYn+afSlZKQHgbSjFT4b8hD3rWnU6/EeS+HX8k5ogJqyy4et/TomMp4gIxC/jjhFw3XWhKpm
4Wr51tzDI3lUs2PlVNLFSiBhNzGCAxAwggMMAgEBMHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT
HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBG
cmVlbWFpbCBJc3N1aW5nIENBAhBXCp+rjCchWJt6MPQMA1aNMAkGBSsOAwIaBQCgggFvMBgGCSqG
SIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA4MDkzMDA5NDMxMFowIwYJKoZI
hvcNAQkEMRYEFEWLH4zGOuACh/ut+Y6o77U1p1dYMIGFBgkrBgEEAYI3EAQxeDB2MGIxCzAJBgNV
BAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNU
aGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQVwqfq4wnIVibejD0DANWjTCBhwYL
KoZIhvcNAQkQAgsxeKB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGlu
ZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBD
QQIQVwqfq4wnIVibejD0DANWjTANBgkqhkiG9w0BAQEFAASCAQAximnYP2wMeNC4yMS5cpjqo8Ua
F52bOGo/MWHMzDkELOk8RdlKWQhg9EE6WKLXOdgXfAvJ+b1ttX3NDaX7XAl7P8g2TfFBGeNddzas
UvlRxtecd2M3tyh0HoVE1zhwUPzcyL3whBrv+upmKRsK12T5gBuRdKnnLt5gImZyggKLewi1fSvE
qikx4a569DLf3WIvyrfpWNPXwvEGcI0J2e2BS88FzQD8r7hN1GVOjjJhEOIop6lHtwbbzt0Qw03r
0PQS8i2n45Q4iCPNmgVNIsAkQ00NYuvjTGkK4mPpLZUdshZ/Srp3AfIfckXS9wHxPAWzvml2J8iQ
YK3ZueOSnQDhAAAAAAAA

--Apple-Mail-1--352545528--

--===============0775758718==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm

--===============0775758718==--


From tcpm-bounces@ietf.org  Tue Sep 30 07:42:14 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5A5D53A6B23;
	Tue, 30 Sep 2008 07:42:14 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 078313A6B23
	for <tcpm@core3.amsl.com>; Tue, 30 Sep 2008 07:42:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.588
X-Spam-Level: 
X-Spam-Status: No, score=-2.588 tagged_above=-999 required=5 tests=[AWL=0.011, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ZYL6GomNjH00 for <tcpm@core3.amsl.com>;
	Tue, 30 Sep 2008 07:42:12 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id 2340E3A6B1D
	for <tcpm@ietf.org>; Tue, 30 Sep 2008 07:42:12 -0700 (PDT)
Received: from [128.9.176.50] (c1-vpn11.isi.edu [128.9.176.50])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m8UEgBn4001709
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Tue, 30 Sep 2008 07:42:13 -0700 (PDT)
Message-ID: <48E23AC3.50901@isi.edu>
Date: Tue, 30 Sep 2008 07:42:11 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Lars Eggert <lars.eggert@nokia.com>
References: <200808140650.IAA05627@TR-Sys.de>	<0C53DCFB700D144284A584F54711EC5805DF435A@xmb-sjc-21c.amer.cisco.com>
	<B35986E6-D8D7-4A9E-B8AB-3DB2E5C3FA29@nokia.com>
	<48E110DE.8050903@isi.edu>
	<724ED3DF-B4E5-4FF8-93BF-5B84688CC940@nokia.com>
In-Reply-To: <724ED3DF-B4E5-4FF8-93BF-5B84688CC940@nokia.com>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: =?ISO-8859-1?Q?Alfred_H=CEnes?= <ah@tr-sys.de>, tcpm@ietf.org,
	"ext Anantha Ramaiah \(ananth\)" <ananth@cisco.com>,
	rrs@cisco.com, "Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>
Subject: Re: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Lars Eggert wrote:
> Hi,
> 
> (individual hat on)
...
> My reason for suggesting to omit the "updates" - and this is a personal
> preference, I'll respect the WG decision and would like to head other
> opinions - is that a plain "updates 793" looks like a "you must
> implement this when implementing 793", and we had a long discussion
> around the applicability statement that seemed to indicate that the WG
> didn't want to make this blanket recommendation.
> 
> Lars

Right - that's the critical issue, and I agree with your conclusion.

Joe

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

iEYEARECAAYFAkjiOsMACgkQE5f5cImnZrvDHQCg79dDM84rcD4I8N9h2d0e7i6z
LaoAoO12Eiv400l8DPszv9GU1EUf0Djd
=u/IX
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Tue Sep 30 08:54:43 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5AEB728C15C;
	Tue, 30 Sep 2008 08:54:43 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1561628C15C
	for <tcpm@core3.amsl.com>; Tue, 30 Sep 2008 08:54:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.257
X-Spam-Level: 
X-Spam-Status: No, score=-6.257 tagged_above=-999 required=5 tests=[AWL=0.342, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1IqtEAro7gd3 for <tcpm@core3.amsl.com>;
	Tue, 30 Sep 2008 08:54:41 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id 125DF28C11F
	for <tcpm@ietf.org>; Tue, 30 Sep 2008 08:54:41 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,338,1220227200"; d="scan'208";a="84798948"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-1.cisco.com with ESMTP; 30 Sep 2008 15:55:00 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m8UFt0va004644; 
	Tue, 30 Sep 2008 08:55:00 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m8UFt0Fh014294;
	Tue, 30 Sep 2008 15:55:00 GMT
Received: from xmb-sjc-21c.amer.cisco.com ([171.70.151.176]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 30 Sep 2008 08:54:58 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 30 Sep 2008 08:55:03 -0700
Message-ID: <0C53DCFB700D144284A584F54711EC5805DF49D5@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <724ED3DF-B4E5-4FF8-93BF-5B84688CC940@nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
Thread-Index: Acki4RvNIOXVI6qUSC6oKM1Xdr/yTwAK+9Hw
References: <200808140650.IAA05627@TR-Sys.de>	<0C53DCFB700D144284A584F54711EC5805DF435A@xmb-sjc-21c.amer.cisco.com><B35986E6-D8D7-4A9E-B8AB-3DB2E5C3FA29@nokia.com><48E110DE.8050903@isi.edu>
	<724ED3DF-B4E5-4FF8-93BF-5B84688CC940@nokia.com>
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: "Lars Eggert" <lars.eggert@nokia.com>, "ext Joe Touch" <touch@ISI.EDU>
X-OriginalArrivalTime: 30 Sep 2008 15:54:58.0419 (UTC)
	FILETIME=[E3C16430:01C92314]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2989; t=1222790100;
	x=1223654100; c=relaxed/simple; s=sjdkim1004;
	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[tcpm]=20another=20review=20of=20draft-
	ietf-tcpm-tcpsecure[-10] |Sender:=20;
	bh=m6lTl7HPII7leQxg1nky0xhWHT8StPr9VHDFcE7S4mw=;
	b=G7qs0qx4t30yR417qfB91zdJei+u1WbpY8Mg2JDxonNSJQDXrBoeFSLitI
	dQ9IAKvTEUR/jC2WSthGeSTErJV43LoyTL827iCd9fszsxNrrY7DPrA6lsZ+
	rLQpedR438UsQq2CzBszJn/9e4euQYW1E5pe+tza/Stk1+XHvh5TQ=;
Authentication-Results: sj-dkim-1; header.From=ananth@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: "Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>,
	=?iso-8859-1?Q?Alfred_H=CEnes?= <ah@tr-sys.de>, tcpm@ietf.org,
	randall@lakerest.net
Subject: Re: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org


[ I don't need to put on a special "hat" I guess ;-), I am commenting as a =
individual and not as the author]

To me, "updates" is just a quick reference indicating that the current draf=
t contents updates some of the material of the original draft. Now,, nobody=
 would take this as a recommendation or an implementation advice, IMO. The =
word "updates" cannot be perceived as an override of the applicability stat=
ement or the mitigation strengths decsribed in the draft. Therefore, I don'=
t think that the word "updates" has the effect of "if you implement 793 you=
 should also implement this draft". It also doesn't imply a "blanket recomm=
endation" in any sense.

May be it is a good idea to get the opinions of IESG in this matter ?

Thanks,
-Anantha

> -----Original Message-----
> From: tcpm-bounces@ietf.org [mailto:tcpm-bounces@ietf.org] On =

> Behalf Of Lars Eggert
> Sent: Tuesday, September 30, 2008 2:43 AM
> To: ext Joe Touch
> Cc: Alfred H=CEnes; tcpm@ietf.org; Anantha Ramaiah (ananth); =

> rrs@cisco.com; Mitesh Dalal (mdalal)
> Subject: Re: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
> =

> Hi,
> =

> (individual hat on)
> =

> On 2008-9-29, at 20:31, ext Joe Touch wrote:
> > Is it possible that a SHOULD isn't considered a "updates"?
> =

> RFC2119 language has nothing to do with the "updates" relationship.  =

> It's the applicability that matters.
> =

> "Updates 793" on document X means "if you implement 793 you =

> also need to implement X". That is, because "updates" is =

> typically used when a new document fixes critical bugs in an =

> existing specification or adds mandatory new functionality.
> =

> For this document the applicability statement is basically =

> "SHOULD implement when vulnerable, MAY otherwise". That's a =

> conditional "updates". Unfortunately, the "updates" header =

> isn't expressive enough to convey this.
> =

> We're left with two less-than-optimal choices: Add "updates =

> 793", which doesn't capture the conditional expressed by the =

> applicability statement, or omit "updates 793", which is also =

> inaccurate.
> =

> My reason for suggesting to omit the "updates" - and this is =

> a personal preference, I'll respect the WG decision and would =

> like to head other opinions - is that a plain "updates 793" =

> looks like a "you must implement this when implementing 793", =

> and we had a long discussion around the applicability =

> statement that seemed to indicate that the WG didn't want to =

> make this blanket recommendation.
> =

> Lars
> =

> PS: As an example, look at the recent RFC5348, which is TFRC. =

> It obsoletes RFC3448 (which was the old version of TFRC) but =

> it also updates RFC4342 (DCCP's CCID3), which implements TFRC =

> inside DCCP. The "updates" relationship here means that CCID3 =

> implementations must now
> (also) implement RFC5348, i.e., the new version of TFRC.
> =

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Tue Sep 30 08:54:57 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 953C528C0F0;
	Tue, 30 Sep 2008 08:54:57 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 68CC43A691E
	for <tcpm@core3.amsl.com>; Tue, 30 Sep 2008 08:54:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.537
X-Spam-Level: 
X-Spam-Status: No, score=-3.537 tagged_above=-999 required=5 tests=[AWL=0.062, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id WoDHFaR8uydg for <tcpm@core3.amsl.com>;
	Tue, 30 Sep 2008 08:54:55 -0700 (PDT)
Received: from mail.wrs.com (mail.windriver.com [147.11.1.11])
	by core3.amsl.com (Postfix) with ESMTP id 8FCFF3A6951
	for <tcpm@ietf.org>; Tue, 30 Sep 2008 08:54:55 -0700 (PDT)
Received: from ALA-MAIL03.corp.ad.wrs.com (ala-mail03 [147.11.57.144])
	by mail.wrs.com (8.13.6/8.13.6) with ESMTP id m8UFst1l003623;
	Tue, 30 Sep 2008 08:54:55 -0700 (PDT)
Received: from ala-mail06.corp.ad.wrs.com ([147.11.57.147]) by
	ALA-MAIL03.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 30 Sep 2008 08:54:55 -0700
Received: from [172.25.34.50] ([172.25.34.50]) by ala-mail06.corp.ad.wrs.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 30 Sep 2008 08:54:55 -0700
Message-Id: <3B570CE3-309B-4473-9A19-99905A93986A@windriver.com>
From: David Borman <david.borman@windriver.com>
To: Lars Eggert <lars.eggert@nokia.com>, tcpm@ietf.org
In-Reply-To: <724ED3DF-B4E5-4FF8-93BF-5B84688CC940@nokia.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Tue, 30 Sep 2008 10:54:52 -0500
References: <200808140650.IAA05627@TR-Sys.de>	<0C53DCFB700D144284A584F54711EC5805DF435A@xmb-sjc-21c.amer.cisco.com>
	<B35986E6-D8D7-4A9E-B8AB-3DB2E5C3FA29@nokia.com>
	<48E110DE.8050903@isi.edu>
	<724ED3DF-B4E5-4FF8-93BF-5B84688CC940@nokia.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 30 Sep 2008 15:54:55.0230 (UTC)
	FILETIME=[E1DAC9E0:01C92314]
Cc: =?ISO-8859-1?Q?Alfred_H=CEnes?= <ah@tr-sys.de>,
	"Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>,
	"ext Anantha Ramaiah \(ananth\)" <ananth@cisco.com>,
	rrs@cisco.com, ext Joe Touch <touch@isi.edu>
Subject: Re: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

(WG co-chair hats on)

Wes and I discussed this, and we agree with Lars.  "Updates" is  
generally for things that are now required if you implement the cited  
spec.  Tcpsecure doesn't fit that criteria, so the "Updates 793"  
doesn't belong on this document.  As Lars said, this is less than  
perfect, but it is what we currently have.

FWIW, I could only find one RFC that has "Updates 793", and that is  
RFC 3168, "The Addition of Explicit Congestion Notification (ECN) to  
IP", which allocates two of the reserved flags in the TCP header.

			-David & Wes, TCPM WG co-chairs

On Sep 30, 2008, at 4:43 AM, Lars Eggert wrote:

> Hi,
>
> (individual hat on)
>
> On 2008-9-29, at 20:31, ext Joe Touch wrote:
>> Is it possible that a SHOULD isn't considered a "updates"?
>
> RFC2119 language has nothing to do with the "updates" relationship.  
> It's the applicability that matters.
>
> "Updates 793" on document X means "if you implement 793 you also  
> need to implement X". That is, because "updates" is typically used  
> when a new document fixes critical bugs in an existing specification  
> or adds mandatory new functionality.
>
> For this document the applicability statement is basically "SHOULD  
> implement when vulnerable, MAY otherwise". That's a conditional  
> "updates". Unfortunately, the "updates" header isn't expressive  
> enough to convey this.
>
> We're left with two less-than-optimal choices: Add "updates 793",  
> which doesn't capture the conditional expressed by the applicability  
> statement, or omit "updates 793", which is also inaccurate.
>
> My reason for suggesting to omit the "updates" - and this is a  
> personal preference, I'll respect the WG decision and would like to  
> head other opinions - is that a plain "updates 793" looks like a  
> "you must implement this when implementing 793", and we had a long  
> discussion around the applicability statement that seemed to  
> indicate that the WG didn't want to make this blanket recommendation.
>
> Lars
>
> PS: As an example, look at the recent RFC5348, which is TFRC. It  
> obsoletes RFC3448 (which was the old version of TFRC) but it also  
> updates RFC4342 (DCCP's CCID3), which implements TFRC inside DCCP.  
> The "updates" relationship here means that CCID3 implementations  
> must now (also) implement RFC5348, i.e., the new version of  
> TFRC._______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Tue Sep 30 09:43:13 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 697AC3A6A17;
	Tue, 30 Sep 2008 09:43:13 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CE92B3A691E
	for <tcpm@core3.amsl.com>; Tue, 30 Sep 2008 09:43:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.306
X-Spam-Level: 
X-Spam-Status: No, score=-6.306 tagged_above=-999 required=5 tests=[AWL=0.293, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4tVY9k0cojhn for <tcpm@core3.amsl.com>;
	Tue, 30 Sep 2008 09:43:00 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id 3B77A28C17B
	for <tcpm@ietf.org>; Tue, 30 Sep 2008 09:43:00 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,338,1220227200"; d="scan'208";a="84833611"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-1.cisco.com with ESMTP; 30 Sep 2008 16:43:22 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m8UGhLEv009594; 
	Tue, 30 Sep 2008 09:43:21 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m8UGhLQD026415;
	Tue, 30 Sep 2008 16:43:21 GMT
Received: from xmb-sjc-21c.amer.cisco.com ([171.70.151.176]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 30 Sep 2008 09:43:21 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 30 Sep 2008 09:43:14 -0700
Message-ID: <0C53DCFB700D144284A584F54711EC5805DF4A3C@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <3B570CE3-309B-4473-9A19-99905A93986A@windriver.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
Thread-Index: AckjFO+lNnhV8IygRWO9tjxdRj/8mQAASsbw
References: <200808140650.IAA05627@TR-Sys.de>	<0C53DCFB700D144284A584F54711EC5805DF435A@xmb-sjc-21c.amer.cisco.com>
	<B35986E6-D8D7-4A9E-B8AB-3DB2E5C3FA29@nokia.com>
	<48E110DE.8050903@isi.edu>
	<724ED3DF-B4E5-4FF8-93BF-5B84688CC940@nokia.com>
	<3B570CE3-309B-4473-9A19-99905A93986A@windriver.com>
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: "David Borman" <david.borman@windriver.com>,
	"Lars Eggert" <lars.eggert@nokia.com>, <tcpm@ietf.org>
X-OriginalArrivalTime: 30 Sep 2008 16:43:21.0651 (UTC)
	FILETIME=[A6377030:01C9231B]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4175; t=1222793002;
	x=1223657002; c=relaxed/simple; s=sjdkim1004;
	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[tcpm]=20another=20review=20of=20draft-
	ietf-tcpm-tcpsecure[-10] |Sender:=20;
	bh=PDTQ+N8jLuMaoO95Ptn3EYAfOTds4NMVZlIEMW5MZIg=;
	b=ZKnGqFT3K7erlMH3Y3KohljzBZ41LYdFgH7jSccrMp0/Izoy4t9PBiiBYr
	xoKy9GSWQ3EI0TxoSq3NGrNvu3W6ZHv1eZuiOBU+ENkK+JeHnU46kb8ity6o
	U9sv4YZPuBkJ5wz1raq+mwQnXOKCFhMFN7LxGpaytFrfzatChFwXs=;
Authentication-Results: sj-dkim-1; header.From=ananth@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: =?iso-8859-1?Q?Alfred_H=CEnes?= <ah@tr-sys.de>,
	"Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>,
	randall@lakerest.net, ext Joe Touch <touch@isi.edu>
Subject: Re: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org


David/Wes,

I don't intend to prolong this discussion, but the current stance comes acr=
oss very incurrate.

Based on the example which you gave narrated below :

RFC 3168 used up 2 reserved bits in the TCP header, and hence updated the R=
FC 793. Now RFC 3168 is optional. This doesn't prevent the fact that "updat=
es" can be used as a qualifier. =


With TCP secure, it changes the processing rules of certain segments (algor=
ithm), so strictly speaking it does update RFC 793. It is optional since no=
ne of the conditions is MUST and also there is an AS in place. Here you can=
't use "updates" since that becomes too strong a word! This beats me.

It appears that we are reading too much into the word "updates" rather than=
 acknowledging its simplicity, i.e, it is just a quick reference point.

So, I guess I am confused as to how and where the lines are drawn. Hence, I=
 think that it would be expedient to seek the advice of IESG as well in thi=
s matter. Isn't a good thing ? =


$0.02,
-Anantha
> -----Original Message-----
> From: David Borman [mailto:david.borman@windriver.com] =

> Sent: Tuesday, September 30, 2008 8:55 AM
> To: Lars Eggert; tcpm@ietf.org
> Cc: ext Joe Touch; Alfred H=CEnes; Anantha Ramaiah (ananth); =

> rrs@cisco.com; Mitesh Dalal (mdalal)
> Subject: Re: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
> =

> (WG co-chair hats on)
> =

> Wes and I discussed this, and we agree with Lars.  "Updates" =

> is generally for things that are now required if you =

> implement the cited spec.  Tcpsecure doesn't fit that =

> criteria, so the "Updates 793"  =

> doesn't belong on this document.  As Lars said, this is less =

> than perfect, but it is what we currently have.
> =

> FWIW, I could only find one RFC that has "Updates 793", and =

> that is RFC 3168, "The Addition of Explicit Congestion =

> Notification (ECN) to IP", which allocates two of the =

> reserved flags in the TCP header.
> =

> 			-David & Wes, TCPM WG co-chairs
> =

> On Sep 30, 2008, at 4:43 AM, Lars Eggert wrote:
> =

> > Hi,
> >
> > (individual hat on)
> >
> > On 2008-9-29, at 20:31, ext Joe Touch wrote:
> >> Is it possible that a SHOULD isn't considered a "updates"?
> >
> > RFC2119 language has nothing to do with the "updates" =

> relationship.  =

> > It's the applicability that matters.
> >
> > "Updates 793" on document X means "if you implement 793 you =

> also need =

> > to implement X". That is, because "updates" is typically =

> used when a =

> > new document fixes critical bugs in an existing =

> specification or adds =

> > mandatory new functionality.
> >
> > For this document the applicability statement is basically "SHOULD =

> > implement when vulnerable, MAY otherwise". That's a conditional =

> > "updates". Unfortunately, the "updates" header isn't =

> expressive enough =

> > to convey this.
> >
> > We're left with two less-than-optimal choices: Add "updates 793", =

> > which doesn't capture the conditional expressed by the =

> applicability =

> > statement, or omit "updates 793", which is also inaccurate.
> >
> > My reason for suggesting to omit the "updates" - and this is a =

> > personal preference, I'll respect the WG decision and would like to =

> > head other opinions - is that a plain "updates 793" looks =

> like a "you =

> > must implement this when implementing 793", and we had a long =

> > discussion around the applicability statement that seemed =

> to indicate =

> > that the WG didn't want to make this blanket recommendation.
> >
> > Lars
> >
> > PS: As an example, look at the recent RFC5348, which is TFRC. It =

> > obsoletes RFC3448 (which was the old version of TFRC) but it also =

> > updates RFC4342 (DCCP's CCID3), which implements TFRC inside DCCP.
> > The "updates" relationship here means that CCID3 =

> implementations must =

> > now (also) implement RFC5348, i.e., the new version of =

> > TFRC._______________________________________________
> > tcpm mailing list
> > tcpm@ietf.org
> > https://www.ietf.org/mailman/listinfo/tcpm
> =

> =

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Tue Sep 30 10:06:14 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 661BF28C115;
	Tue, 30 Sep 2008 10:06:14 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DFE8528C115
	for <tcpm@core3.amsl.com>; Tue, 30 Sep 2008 10:06:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.901
X-Spam-Level: 
X-Spam-Status: No, score=-5.901 tagged_above=-999 required=5 tests=[AWL=0.699, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OwMgMzZm-Do6 for <tcpm@core3.amsl.com>;
	Tue, 30 Sep 2008 10:06:09 -0700 (PDT)
Received: from ndjsnpf02.ndc.nasa.gov (ndjsnpf02.ndc.nasa.gov [198.117.1.122])
	by core3.amsl.com (Postfix) with ESMTP id E80F33A6A32
	for <tcpm@ietf.org>; Tue, 30 Sep 2008 10:06:08 -0700 (PDT)
Received: from ndjsppt03.ndc.nasa.gov (ndjsppt03.ndc.nasa.gov [198.117.1.102])
	by ndjsnpf02.ndc.nasa.gov (Postfix) with ESMTP id 411B2A818A;
	Tue, 30 Sep 2008 12:06:24 -0500 (CDT)
Received: from ndjsxgw03.ndc.nasa.gov (ndjsxgw03.ndc.nasa.gov [129.166.32.111])
	by ndjsppt03.ndc.nasa.gov (8.14.1/8.14.1) with ESMTP id m8UH6Rec029338; 
	Tue, 30 Sep 2008 12:06:27 -0500
Received: from NDJSEVS25A.ndc.nasa.gov ([129.166.32.124]) by
	ndjsxgw03.ndc.nasa.gov with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 30 Sep 2008 12:06:28 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 30 Sep 2008 12:06:28 -0500
Message-ID: <B5A5E01F9387F4409E67604C0257C71E56038C@NDJSEVS25A.ndc.nasa.gov>
In-Reply-To: <0C53DCFB700D144284A584F54711EC5805DF4A3C@xmb-sjc-21c.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
Thread-Index: AckjFO+lNnhV8IygRWO9tjxdRj/8mQAASsbwAAIBL4A=
References: <200808140650.IAA05627@TR-Sys.de>	<0C53DCFB700D144284A584F54711EC5805DF435A@xmb-sjc-21c.amer.cisco.com><B35986E6-D8D7-4A9E-B8AB-3DB2E5C3FA29@nokia.com><48E110DE.8050903@isi.edu><724ED3DF-B4E5-4FF8-93BF-5B84688CC940@nokia.com><3B570CE3-309B-4473-9A19-99905A93986A@windriver.com>
	<0C53DCFB700D144284A584F54711EC5805DF4A3C@xmb-sjc-21c.amer.cisco.com>
From: "Eddy, Wesley M. (GRC-RCN0)[VZ]" <Wesley.M.Eddy@nasa.gov>
To: "Anantha Ramaiah (ananth)" <ananth@cisco.com>,
	"David Borman" <david.borman@windriver.com>,
	"Lars Eggert" <lars.eggert@nokia.com>, <tcpm@ietf.org>
X-OriginalArrivalTime: 30 Sep 2008 17:06:28.0739 (UTC)
	FILETIME=[E0FC4530:01C9231E]
Cc: =?iso-8859-1?Q?Alfred_H=CEnes?= <ah@tr-sys.de>,
	"Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>,
	randall@lakerest.net, ext Joe Touch <touch@isi.edu>
Subject: Re: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

>-----Original Message-----
>From: tcpm-bounces@ietf.org [mailto:tcpm-bounces@ietf.org] On 
>Behalf Of Anantha Ramaiah (ananth)
>Sent: Tuesday, September 30, 2008 12:43 PM
>
>David/Wes,
>
>I don't intend to prolong this discussion, but the current 
>stance comes across very incurrate.
>
>Based on the example which you gave narrated below :
>
>RFC 3168 used up 2 reserved bits in the TCP header, and hence 
>updated the RFC 793. Now RFC 3168 is optional. This doesn't 
>prevent the fact that "updates" can be used as a qualifier. 
>
>With TCP secure, it changes the processing rules of certain 
>segments (algorithm), so strictly speaking it does update RFC 
>793. It is optional since none of the conditions is MUST and 
>also there is an AS in place. Here you can't use "updates" 
>since that becomes too strong a word! This beats me.
>
>It appears that we are reading too much into the word 
>"updates" rather than acknowledging its simplicity, i.e, it is 
>just a quick reference point.
>
>So, I guess I am confused as to how and where the lines are 
>drawn. Hence, I think that it would be expedient to seek the 
>advice of IESG as well in this matter. Isn't a good thing ? 


My personal opinion on the number of angels on the head of this
pin is that 3168 redefines bits that were formerly reserved.  Thus
it "updates" the description of those bits in 793 (they're no longer
reserved).  *Regardless* of the fact that 3168 is itself optional,
those bits are no longer available in the way 793 describes.  *That*
is why it has to "update" even though it's optional itself.

The tcpsecure document does not "update" in that sense, as it only
contains optional alternative state machine arcs; the arcs defined
in 793 are still able to be used in the way 793 describes ... they
aren't "updated", but there's now an alternative to them.
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Tue Sep 30 10:46:24 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5BF563A6A11;
	Tue, 30 Sep 2008 10:46:24 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 34E303A6A11
	for <tcpm@core3.amsl.com>; Tue, 30 Sep 2008 10:46:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.343
X-Spam-Level: 
X-Spam-Status: No, score=-6.343 tagged_above=-999 required=5 tests=[AWL=0.256, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id VXTyUSPwnTHG for <tcpm@core3.amsl.com>;
	Tue, 30 Sep 2008 10:46:21 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id D858C3A6804
	for <tcpm@ietf.org>; Tue, 30 Sep 2008 10:46:21 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,339,1220227200"; d="scan'208";a="165976598"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 30 Sep 2008 17:46:41 +0000
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m8UHkfNa017634; 
	Tue, 30 Sep 2008 10:46:41 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-3.cisco.com (8.13.8/8.13.8) with ESMTP id m8UHkfjq007571;
	Tue, 30 Sep 2008 17:46:41 GMT
Received: from xmb-sjc-21c.amer.cisco.com ([171.70.151.176]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 30 Sep 2008 10:46:41 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 30 Sep 2008 10:46:38 -0700
Message-ID: <0C53DCFB700D144284A584F54711EC5805DF4AE2@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <B5A5E01F9387F4409E67604C0257C71E56038C@NDJSEVS25A.ndc.nasa.gov>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
Thread-Index: AckjFO+lNnhV8IygRWO9tjxdRj/8mQAASsbwAAIBL4AAANa5QA==
References: <200808140650.IAA05627@TR-Sys.de>	<0C53DCFB700D144284A584F54711EC5805DF435A@xmb-sjc-21c.amer.cisco.com><B35986E6-D8D7-4A9E-B8AB-3DB2E5C3FA29@nokia.com><48E110DE.8050903@isi.edu><724ED3DF-B4E5-4FF8-93BF-5B84688CC940@nokia.com><3B570CE3-309B-4473-9A19-99905A93986A@windriver.com>
	<0C53DCFB700D144284A584F54711EC5805DF4A3C@xmb-sjc-21c.amer.cisco.com>
	<B5A5E01F9387F4409E67604C0257C71E56038C@NDJSEVS25A.ndc.nasa.gov>
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: "Eddy, Wesley M. (GRC-RCN0)[VZ]" <Wesley.M.Eddy@nasa.gov>,
	"David Borman" <david.borman@windriver.com>,
	"Lars Eggert" <lars.eggert@nokia.com>, <tcpm@ietf.org>
X-OriginalArrivalTime: 30 Sep 2008 17:46:41.0538 (UTC)
	FILETIME=[7F202E20:01C92324]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1394; t=1222796801;
	x=1223660801; c=relaxed/simple; s=sjdkim4002;
	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[tcpm]=20another=20review=20of=20draft-
	ietf-tcpm-tcpsecure[-10] |Sender:=20;
	bh=kjJ11S+Kb8ChlZEEaOdXseW/wFznE5dwyxgAFCTAc8k=;
	b=JzDXyrGyXOavmu5KUrg3vUw29ZZPlK3O5Ckl0VOYs9RqJvuW/dWpLPoRVt
	eRe4rxhXZZa+QSlFwn5ph3CaOggokUtvnCld1hXGNdfkZis7EbGLO4MB/hV4
	4aM9GP9tgq;
Authentication-Results: sj-dkim-4; header.From=ananth@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: =?iso-8859-1?Q?Alfred_H=CEnes?= <ah@tr-sys.de>,
	"Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>,
	randall@lakerest.net, ext Joe Touch <touch@isi.edu>
Subject: Re: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

Wes, 

> 
> 
> My personal opinion on the number of angels on the head of this
> pin is that 3168 redefines bits that were formerly reserved.  Thus
> it "updates" the description of those bits in 793 (they're no longer
> reserved).  *Regardless* of the fact that 3168 is itself optional,
> those bits are no longer available in the way 793 describes.  *That*
> is why it has to "update" even though it's optional itself.
> 
> The tcpsecure document does not "update" in that sense, as it only
> contains optional alternative state machine arcs; the arcs defined
> in 793 are still able to be used in the way 793 describes ... they
> aren't "updated", but there's now an alternative to them.

Are you saying that we should construe that "alternate processing" doesn't update the RFC?. Now, the update itself can be optional. In other words, my point is that the current meaning and usage of "updates" is to be used for any updates to the RFC, irrespective of the fact it is minor, major or optional. Agreed that, currently there is fine granularity in describing an update i.e, "minor update, medium update or conditinal update " etc., until such a granularity is available, we should use the existing documented mechanisms. This is the reason I think it would be expedient to seek the advice of IESG in this matter.

Thanks,
-Anantha

> 
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Tue Sep 30 10:57:41 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E554F3A6BBE;
	Tue, 30 Sep 2008 10:57:41 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4704F3A6BD8
	for <tcpm@core3.amsl.com>; Tue, 30 Sep 2008 10:57:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.25
X-Spam-Level: 
X-Spam-Status: No, score=-6.25 tagged_above=-999 required=5 tests=[AWL=0.349, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id xJJDxpz03yGI for <tcpm@core3.amsl.com>;
	Tue, 30 Sep 2008 10:57:40 -0700 (PDT)
Received: from ndjsnpf02.ndc.nasa.gov (ndjsnpf02.ndc.nasa.gov [198.117.1.122])
	by core3.amsl.com (Postfix) with ESMTP id 4607B3A6BBE
	for <tcpm@ietf.org>; Tue, 30 Sep 2008 10:57:40 -0700 (PDT)
Received: from ndjsppt02.ndc.nasa.gov (ndjsppt02.ndc.nasa.gov [198.117.1.101])
	by ndjsnpf02.ndc.nasa.gov (Postfix) with ESMTP id 4CDCDA8143;
	Tue, 30 Sep 2008 12:57:56 -0500 (CDT)
Received: from ndjsxgw04.ndc.nasa.gov (ndjsxgw04.ndc.nasa.gov [129.166.32.112])
	by ndjsppt02.ndc.nasa.gov (8.14.1/8.14.1) with ESMTP id m8UHw1J8017125; 
	Tue, 30 Sep 2008 12:58:01 -0500
Received: from NDJSEVS25A.ndc.nasa.gov ([129.166.32.124]) by
	ndjsxgw04.ndc.nasa.gov with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 30 Sep 2008 12:58:00 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 30 Sep 2008 12:58:00 -0500
Message-ID: <B5A5E01F9387F4409E67604C0257C71E5603CD@NDJSEVS25A.ndc.nasa.gov>
In-Reply-To: <0C53DCFB700D144284A584F54711EC5805DF4AE2@xmb-sjc-21c.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
Thread-Index: AckjFO+lNnhV8IygRWO9tjxdRj/8mQAASsbwAAIBL4AAANa5QAAA1Gww
References: <200808140650.IAA05627@TR-Sys.de>	<0C53DCFB700D144284A584F54711EC5805DF435A@xmb-sjc-21c.amer.cisco.com><B35986E6-D8D7-4A9E-B8AB-3DB2E5C3FA29@nokia.com><48E110DE.8050903@isi.edu><724ED3DF-B4E5-4FF8-93BF-5B84688CC940@nokia.com><3B570CE3-309B-4473-9A19-99905A93986A@windriver.com>
	<0C53DCFB700D144284A584F54711EC5805DF4A3C@xmb-sjc-21c.amer.cisco.com>
	<B5A5E01F9387F4409E67604C0257C71E56038C@NDJSEVS25A.ndc.nasa.gov>
	<0C53DCFB700D144284A584F54711EC5805DF4AE2@xmb-sjc-21c.amer.cisco.com>
From: "Eddy, Wesley M. (GRC-RCN0)[VZ]" <Wesley.M.Eddy@nasa.gov>
To: "Anantha Ramaiah (ananth)" <ananth@cisco.com>,
	"David Borman" <david.borman@windriver.com>,
	"Lars Eggert" <lars.eggert@nokia.com>, <tcpm@ietf.org>
X-OriginalArrivalTime: 30 Sep 2008 17:58:00.0579 (UTC)
	FILETIME=[13DD9D30:01C92326]
Cc: =?iso-8859-1?Q?Alfred_H=CEnes?= <ah@tr-sys.de>,
	"Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>,
	randall@lakerest.net, ext Joe Touch <touch@isi.edu>
Subject: Re: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

>-----Original Message-----
>From: Anantha Ramaiah (ananth) [mailto:ananth@cisco.com] =

>Sent: Tuesday, September 30, 2008 1:47 PM
>To: Eddy, Wesley M. (GRC-RCN0)[VZ]; David Borman; Lars Eggert; =

>tcpm@ietf.org
>Cc: Alfred H=CEnes; Mitesh Dalal (mdalal); randall@lakerest.net; =

>ext Joe Touch
>Subject: RE: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
>
>Wes, =

>
>> =

>> =

>> My personal opinion on the number of angels on the head of this
>> pin is that 3168 redefines bits that were formerly reserved.  Thus
>> it "updates" the description of those bits in 793 (they're no longer
>> reserved).  *Regardless* of the fact that 3168 is itself optional,
>> those bits are no longer available in the way 793 describes.  *That*
>> is why it has to "update" even though it's optional itself.
>> =

>> The tcpsecure document does not "update" in that sense, as it only
>> contains optional alternative state machine arcs; the arcs defined
>> in 793 are still able to be used in the way 793 describes ... they
>> aren't "updated", but there's now an alternative to them.
>
>Are you saying that we should construe that "alternate =

>processing" doesn't update the RFC?. Now, the update itself =

>can be optional. In other words, my point is that the current =

>meaning and usage of "updates" is to be used for any updates =

>to the RFC, irrespective of the fact it is minor, major or =

>optional. Agreed that, currently there is fine granularity in =

>describing an update i.e, "minor update, medium update or =

>conditinal update " etc., until such a granularity is =

>available, we should use the existing documented mechanisms. =

>This is the reason I think it would be expedient to seek the =

>advice of IESG in this matter.


My position is very simple:
What part of RFC 793 is no longer correct?  Which text is no
longer accurate in RFC 793?

With ECN, it's very clear, the answer is "the 2 reserved bits
are not reserved anymore".  With tcpsecure, the answer is also
very clear: "nothing".  You need to point to some part of 793
that is actually updated and not just alternatively defined,
IMO.  If 2581, 1323, and others don't update 793, then I don't
see how tcpsecure can have any valid claim to.

That's just my personal opinion, though.
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Tue Sep 30 13:03:43 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 978C428C19B;
	Tue, 30 Sep 2008 13:03:43 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3CAEA28C17A;
	Tue, 30 Sep 2008 13:03:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.274
X-Spam-Level: *
X-Spam-Status: No, score=1.274 tagged_above=-999 required=5 tests=[AWL=0.023, 
	BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35,
	MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id CQVpeVlk6dXf; Tue, 30 Sep 2008 13:03:41 -0700 (PDT)
Received: from WOTAN.TR-Sys.de (gateway.tr-sys.de [213.178.172.147])
	by core3.amsl.com (Postfix) with ESMTP id F322C28C10C;
	Tue, 30 Sep 2008 13:03:39 -0700 (PDT)
Received: from ZEUS.TR-Sys.de by w. with ESMTP
	($Revision: 1.37.109.26 $/16.3) id AA149314964;
	Tue, 30 Sep 2008 22:02:45 +0200
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id
	WAA09122; Tue, 30 Sep 2008 22:02:43 +0200 (MESZ)
From: Alfred =?hp-roman8?B?SM5uZXM=?= <ah@tr-sys.de>
Message-Id: <200809302002.WAA09122@TR-Sys.de>
To: tcpm@ietf.org
Date: Tue, 30 Sep 2008 22:02:43 +0200 (MESZ)
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Cc: iesg@iesg.org
Subject: [tcpm] exegesis of 'Updates' -- was: ... review of
	draft-ietf-tcpm-tcpsecure[-10]
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

Folks,
I observe that this discussion (which my initial posting has
triggered involuntarily) is getting ridiculous.

Let's return from fine-grained nano-arguments to the roots.

We are discussing the simple "relations" in the metadata of RFCs.

These serve the purpose to visibly link these documents together
in a coarse, qualified manner, and thus enable any reader not
aware of lengthy WG discussion list threads to find a web of
pointers which should assist her/him in finding the related
documents, when starting with a 'well known' base document.

Admittedly, the 'vocabulary' available is very simple, but one
of the main issue I had when I once started reading RFCs was the
very scarce and poor usage of this simple vocabulary, "Updates",
"Obsoletes", and "Also".
My perception frequently was that there were far too many MUSTs
and SHOULDs and MAYs inside the documents, and far too few
"Udates" helping the reader navigate the RFCs, in the metadata.
(It's similar to web pages with no hyperlinks on 'home pages'
[or equivalent] pointing to them!)

Any implementor or analyst reading RFC 793 should be made aware
of the tcpsecure RFC, as soon as it is out (and I really hope to
see it soon in the RFC index!), because that document contains
qualified statements this working group has judged.
[... in an incommensurate long period of discussion holding off
this long-expected document -- personal note.]
He/she should be pointed to this document by the RFC metadata,
and should read it (the latter seems to be the consensus of
the WG, isn't it?) -- otherwise publishing the document would
be rather moot.

The "Updated by" metadata links do not imply requirements
language in any way, they point the reader to documents that
(hopefully) contain an applicability statement and their own,
and detailed requirements language.

If a new document adds, e.g., new options, to properly designed
extensibility hooks of a protocol, without affecting/changing
processing rules of the protocol, that memo does not "Update"
the base document for that protocol, and that document can be
easily picked up by tracing the IANA Registry for the namespace
forming the extensibility hook.  But if a document discusses
new requirements for a protocol that have come up in the real
world, and it contains 'considerations' about modifications
to the processing rules laid down in another document (which
in this particular case already have been adopted by most
significant players in the marketplace as inevitable and
indispensible changes for security reasons), this new document
SHOULD be tagged in the RFC metadata as "Updates <the old one>".

Don't forget:
This WG is chartered for the *MAINTENANCE* of TCP.
If you don't want to make that maintenace visible, you are in
danger to dismiss your mission (and the mission of the IETF and
its Standards Process).  Since RFCs are immutable, RFC Errata
and additions to the RFC metadata are the only ways to make
an act of maintenance for a document visible at first place.

I only see one other option (but I guess that's not a real option
in practice, due to workload): *regularly* update RFC 4614 .
Such documents (and there are far too few of this kind!)
provide enough space to discuss the nuances of conditional
MUSTs and SHOULDs in case of applicability etc. etc. at length,
if deemed necessary.

Therefore my recommendation:

+++   Be very careful with "Obsoletes", but be generous
+++   with "Updates", for the benefit of RFC readers !

Kind regards,
  Alfred.


P.S.:
The discussion has mentioned the tiny number of "Updated by"
for RFC 793, one of the oldest and most important standards
of the IETF.  Many technicians not aware of the discussions
in this WG would take this as a severe indication, or even
evidence for lack of maintenance for TCP!

-- 

+------------------------+--------------------------------------------+
| TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math., Dipl.-Phys.  |
| Gerlinger Strasse 12   |  Phone: (+49)7156/9635-0, Fax: -18         |
| D-71254  Ditzingen     |  E-Mail:  ah@TR-Sys.de                     |
+------------------------+--------------------------------------------+



_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Tue Sep 30 13:47:28 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 907C43A6BE7;
	Tue, 30 Sep 2008 13:47:28 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 175AD3A6BE7
	for <tcpm@core3.amsl.com>; Tue, 30 Sep 2008 13:47:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.371
X-Spam-Level: 
X-Spam-Status: No, score=-6.371 tagged_above=-999 required=5 tests=[AWL=0.228, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id h1G1e+PFGXv5 for <tcpm@core3.amsl.com>;
	Tue, 30 Sep 2008 13:47:26 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86])
	by core3.amsl.com (Postfix) with ESMTP id 1BC053A6BE5
	for <tcpm@ietf.org>; Tue, 30 Sep 2008 13:47:26 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,339,1220227200"; d="scan'208";a="22413628"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-4.cisco.com with ESMTP; 30 Sep 2008 20:47:48 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m8UKlm0X016488; 
	Tue, 30 Sep 2008 13:47:48 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m8UKlmxb005491;
	Tue, 30 Sep 2008 20:47:48 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); 
	Tue, 30 Sep 2008 13:47:47 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 30 Sep 2008 13:47:44 -0700
Message-ID: <0C53DCFB700D144284A584F54711EC5805DF4C45@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <B5A5E01F9387F4409E67604C0257C71E5603CD@NDJSEVS25A.ndc.nasa.gov>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
Thread-Index: AckjFO+lNnhV8IygRWO9tjxdRj/8mQAASsbwAAIBL4AAANa5QAAA1GwwAASOJxA=
References: <200808140650.IAA05627@TR-Sys.de>	<0C53DCFB700D144284A584F54711EC5805DF435A@xmb-sjc-21c.amer.cisco.com><B35986E6-D8D7-4A9E-B8AB-3DB2E5C3FA29@nokia.com><48E110DE.8050903@isi.edu><724ED3DF-B4E5-4FF8-93BF-5B84688CC940@nokia.com><3B570CE3-309B-4473-9A19-99905A93986A@windriver.com><0C53DCFB700D144284A584F54711EC5805DF4A3C@xmb-sjc-21c.amer.cisco.com><B5A5E01F9387F4409E67604C0257C71E56038C@NDJSEVS25A.ndc.nasa.gov><0C53DCFB700D144284A584F54711EC5805DF4AE2@xmb-sjc-21c.amer.cisco.com>
	<B5A5E01F9387F4409E67604C0257C71E5603CD@NDJSEVS25A.ndc.nasa.gov>
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: "Eddy, Wesley M. (GRC-RCN0)[VZ]" <Wesley.M.Eddy@nasa.gov>,
	"David Borman" <david.borman@windriver.com>,
	"Lars Eggert" <lars.eggert@nokia.com>, <tcpm@ietf.org>
X-OriginalArrivalTime: 30 Sep 2008 20:47:47.0972 (UTC)
	FILETIME=[CC066C40:01C9233D]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2469; t=1222807668;
	x=1223671668; 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[tcpm]=20another=20review=20of=20draft-
	ietf-tcpm-tcpsecure[-10] |Sender:=20;
	bh=6tw4KQ3qtIhMtMkwO8eYaLWS/yEPjVfqDMeHCNC762g=;
	b=Lquz15ZzOiFhdTEzOD+Jq786usQLrKe50hCULvt9QvvPk2zvSVBEcX9Fwy
	g2DaRiagoWztvKqavntFaKRD8+kY6GTDnijlJ48KAAckN559mNq4FKvX++t1
	f410xEUWL7;
Authentication-Results: sj-dkim-2; header.From=ananth@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: =?iso-8859-1?Q?Alfred_H=CEnes?= <ah@tr-sys.de>,
	"Mitesh Dalal \(mdalal\)" <mdalal@cisco.com>,
	randall@lakerest.net, ext Joe Touch <touch@isi.edu>
Subject: Re: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

 

> >Are you saying that we should construe that "alternate processing" 
> >doesn't update the RFC?. Now, the update itself can be optional. In 
> >other words, my point is that the current meaning and usage of 
> >"updates" is to be used for any updates to the RFC, 
> irrespective of the 
> >fact it is minor, major or optional. Agreed that, currently there is 
> >fine granularity in describing an update i.e, "minor update, medium 
> >update or conditinal update " etc., until such a granularity is 
> >available, we should use the existing documented mechanisms.
> >This is the reason I think it would be expedient to seek the 
> advice of 
> >IESG in this matter.
> 
> 
> My position is very simple:
> What part of RFC 793 is no longer correct?  Which text is no 
> longer accurate in RFC 793?
> 
> With ECN, it's very clear, the answer is "the 2 reserved bits 
> are not reserved anymore".  With tcpsecure, the answer is 
> also very clear: "nothing".  You need to point to some part 
> of 793 that is actually updated and not just alternatively 
> defined, IMO.  If 2581, 1323, and others don't update 793, 
> then I don't see how tcpsecure can have any valid claim to.

So, in other words, are we saying that only changes to TCP header is considered as an update and not the stuff that changes the semantics ? This is probably a general question w.r.t updates, nothing specific to 793 update.

"Alternatively defined" is also trying to change the RFC 793 semantics i.e, in the current case segment processing rules w.r.t RST, SYN and Data. 

FWIW, 1323 talks "TCP extensions for High performance" about window scaling ( a new TCP option), timestamps ( a new TCP option) and PAWS (which is possible only when you use timestamps), these don't update RFC 793 and just supplements it, IMO.

RFC 1122 standarided the TCP congestion control algorithms and not RFC 793. So if it all 2581 has to update something it had to be 1122 not 793.

> 
> That's just my personal opinion, though.

Sure, my opinion is similar but I am confused with the meaning and applicability of the term "updates". We need to have a consistent story. That is the reason I suggested seeking IESG advice in this matter.

-Anantha
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm
> 
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Tue Sep 30 15:03:40 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1A8703A68C8;
	Tue, 30 Sep 2008 15:03:40 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E6BA33A68C8
	for <tcpm@core3.amsl.com>; Tue, 30 Sep 2008 15:03:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id PnCZnk3Hd8vY for <tcpm@core3.amsl.com>;
	Tue, 30 Sep 2008 15:03:38 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id 130F63A6800
	for <tcpm@ietf.org>; Tue, 30 Sep 2008 15:03:38 -0700 (PDT)
Received: from [192.168.1.45] (pool-71-106-119-240.lsanca.dsl-w.verizon.net
	[71.106.119.240])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m8UM3Pgn002992
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Tue, 30 Sep 2008 15:03:27 -0700 (PDT)
Message-ID: <48E2A22A.8000209@isi.edu>
Date: Tue, 30 Sep 2008 15:03:22 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "Eddy, Wesley M. (GRC-RCN0)[VZ]" <Wesley.M.Eddy@nasa.gov>
References: <200808140650.IAA05627@TR-Sys.de>	<0C53DCFB700D144284A584F54711EC5805DF435A@xmb-sjc-21c.amer.cisco.com><B35986E6-D8D7-4A9E-B8AB-3DB2E5C3FA29@nokia.com><48E110DE.8050903@isi.edu><724ED3DF-B4E5-4FF8-93BF-5B84688CC940@nokia.com><3B570CE3-309B-4473-9A19-99905A93986A@windriver.com>
	<0C53DCFB700D144284A584F54711EC5805DF4A3C@xmb-sjc-21c.amer.cisco.com>
	<B5A5E01F9387F4409E67604C0257C71E56038C@NDJSEVS25A.ndc.nasa.gov>
	<0C53DCFB700D144284A584F54711EC5805DF4AE2@xmb-sjc-21c.amer.cisco.com>
	<B5A5E01F9387F4409E67604C0257C71E5603CD@NDJSEVS25A.ndc.nasa.gov>
In-Reply-To: <B5A5E01F9387F4409E67604C0257C71E5603CD@NDJSEVS25A.ndc.nasa.gov>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: =?ISO-8859-1?Q?d_H=CEnes?= <ah@tr-sys.de>, tcpm@ietf.org,
	David Borman <david.borman@windriver.com>, randall@lakerest.net,
	"Anantha Ramaiah (ananth)" <ananth@cisco.com>,
	=?ISO-8859-1?Q?Alfre?=@core3.amsl.com,
	"Mitesh Dalal (mdalal)" <mdalal@cisco.com>
Subject: Re: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Eddy, Wesley M. (GRC-RCN0)[VZ] wrote:
>> -----Original Message-----
>> From: Anantha Ramaiah (ananth) [mailto:ananth@cisco.com] =

>> Sent: Tuesday, September 30, 2008 1:47 PM
>> To: Eddy, Wesley M. (GRC-RCN0)[VZ]; David Borman; Lars Eggert; =

>> tcpm@ietf.org
>> Cc: Alfred H=CEnes; Mitesh Dalal (mdalal); randall@lakerest.net; =

>> ext Joe Touch
>> Subject: RE: [tcpm] another review of draft-ietf-tcpm-tcpsecure[-10]
>>
>> Wes, =

>>
>>>
>>> My personal opinion on the number of angels on the head of this
>>> pin is that 3168 redefines bits that were formerly reserved.  Thus
>>> it "updates" the description of those bits in 793 (they're no longer
>>> reserved).  *Regardless* of the fact that 3168 is itself optional,
>>> those bits are no longer available in the way 793 describes.  *That*
>>> is why it has to "update" even though it's optional itself.
>>>
>>> The tcpsecure document does not "update" in that sense, as it only
>>> contains optional alternative state machine arcs; the arcs defined
>>> in 793 are still able to be used in the way 793 describes ... they
>>> aren't "updated", but there's now an alternative to them.
>> Are you saying that we should construe that "alternate =

>> processing" doesn't update the RFC?. Now, the update itself =

>> can be optional. In other words, my point is that the current =

>> meaning and usage of "updates" is to be used for any updates =

>> to the RFC, irrespective of the fact it is minor, major or =

>> optional. Agreed that, currently there is fine granularity in =

>> describing an update i.e, "minor update, medium update or =

>> conditinal update " etc., until such a granularity is =

>> available, we should use the existing documented mechanisms. =

>> This is the reason I think it would be expedient to seek the =

>> advice of IESG in this matter.
> =

> =

> My position is very simple:
> What part of RFC 793 is no longer correct?  Which text is no
> longer accurate in RFC 793?
> =

> With ECN, it's very clear, the answer is "the 2 reserved bits
> are not reserved anymore".  With tcpsecure, the answer is also
> very clear: "nothing".  You need to point to some part of 793
> that is actually updated and not just alternatively defined,
> IMO.  If 2581, 1323, and others don't update 793, then I don't
> see how tcpsecure can have any valid claim to.
> =

> That's just my personal opinion, though.


This makes sense to me.

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

iEYEARECAAYFAkjioioACgkQE5f5cImnZrvyfACgk+tXUy6Q1TdshUpvN9Zixv/i
2FEAoNoBwdYFzVM+r0wokwbAaJKLJ3PI
=3Dq5ru
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Tue Sep 30 15:21:25 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9E2163A691B;
	Tue, 30 Sep 2008 15:21:25 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 487F33A691B
	for <tcpm@core3.amsl.com>; Tue, 30 Sep 2008 15:21:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.244
X-Spam-Level: 
X-Spam-Status: No, score=-6.244 tagged_above=-999 required=5 tests=[AWL=0.055, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id fFQkAgw4ae5m for <tcpm@core3.amsl.com>;
	Tue, 30 Sep 2008 15:21:23 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id 340873A68C8
	for <tcpm@ietf.org>; Tue, 30 Sep 2008 15:21:23 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,340,1220227200"; d="scan'208";a="91104570"
Received: from sj-dkim-7.cisco.com ([171.68.10.88])
	by sj-iport-2.cisco.com with ESMTP; 30 Sep 2008 22:21:41 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-7.cisco.com (8.12.11/8.12.11) with ESMTP id m8UMLeNm003847; 
	Tue, 30 Sep 2008 15:21:40 -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.13.8/8.13.8) with ESMTP id m8UMLe29019087;
	Tue, 30 Sep 2008 22:21:40 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); 
	Tue, 30 Sep 2008 15:21:40 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 30 Sep 2008 15:21:42 -0700
Message-ID: <0C53DCFB700D144284A584F54711EC5805DF4CF9@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <200809302002.WAA09122@TR-Sys.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcpm] exegesis of 'Updates' -- was: ... review
	ofdraft-ietf-tcpm-tcpsecure[-10]
Thread-Index: AckjN7cUOnG2XLx/QZiaqB4emubhgQAEj8CA
References: <200809302002.WAA09122@TR-Sys.de>
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: =?iso-8859-1?Q?Alfred_H=CEnes?= <ah@tr-sys.de>, <tcpm@ietf.org>
X-OriginalArrivalTime: 30 Sep 2008 22:21:40.0322 (UTC)
	FILETIME=[E92AD420:01C9234A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=6502; t=1222813300;
	x=1223677300; c=relaxed/simple; s=sjdkim7002;
	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[tcpm]=20exegesis=20of=20'Updates'=20--
	=20was=3A=20...=20review=20ofdraft-ietf-tcpm-tcpsecure[-10]
	|Sender:=20; bh=AVp5DcNcJNu04Pay+cziWC99HKFrxfFxnLSlWSbTD8k=;
	b=BdkdkxaJ6C8aoG1BsDRceP5lFKtqmnZ2JJOqHs3KiYRZRKfttrVzQnTeMM
	4WnUr0jI4qmzqgoV3sndRVbsP2edFeu2gv4cyQ5SxHNHDF2PqJGkWPKH+jz8
	j+8MYNxJ3/;
Authentication-Results: sj-dkim-7; header.From=ananth@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim7002 verified; ); 
Cc: iesg@iesg.org
Subject: Re: [tcpm] exegesis of 'Updates' -- was: ... review
	ofdraft-ietf-tcpm-tcpsecure[-10]
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

Alfred,
   Excellent points. I completley agree with your sentiments. Some notable =
excerpts from your below email (cut & pasted) which I fully support :

A)
 > Any implementor or analyst reading RFC 793 should be made =

> aware of the tcpsecure RFC, as soon as it is out (and I =

> really hope to see it soon in the RFC index!), because that =

> document contains qualified statements this working group has judged.
> [... in an incommensurate long period of discussion holding =

> off this long-expected document -- personal note.] He/she =

> should be pointed to this document by the RFC metadata, and =

> should read it (the latter seems to be the consensus of the =

> WG, isn't it?) -- otherwise publishing the document would be =

> rather moot.

B)
 > Don't forget:
> This WG is chartered for the *MAINTENANCE* of TCP.
> If you don't want to make that maintenace visible, you are in =

> danger to dismiss your mission (and the mission of the IETF =

> and its Standards Process).  Since RFCs are immutable, RFC =

> Errata and additions to the RFC metadata are the only ways to =

> make an act of maintenance for a document visible at first place.

C) =


> Therefore my recommendation:
> =

> +++   Be very careful with "Obsoletes", but be generous
> +++   with "Updates", for the benefit of RFC readers !
> =


Thanks,
-Anantha
> -----Original Message-----
> From: tcpm-bounces@ietf.org [mailto:tcpm-bounces@ietf.org] On =

> Behalf Of Alfred H=CEnes
> Sent: Tuesday, September 30, 2008 1:03 PM
> To: tcpm@ietf.org
> Cc: iesg@iesg.org
> Subject: [tcpm] exegesis of 'Updates' -- was: ... review =

> ofdraft-ietf-tcpm-tcpsecure[-10]
> =

> Folks,
> I observe that this discussion (which my initial posting has =

> triggered involuntarily) is getting ridiculous.
> =

> Let's return from fine-grained nano-arguments to the roots.
> =

> We are discussing the simple "relations" in the metadata of RFCs.
> =

> These serve the purpose to visibly link these documents =

> together in a coarse, qualified manner, and thus enable any =

> reader not aware of lengthy WG discussion list threads to =

> find a web of pointers which should assist her/him in finding =

> the related documents, when starting with a 'well known' base =

> document.
> =

> Admittedly, the 'vocabulary' available is very simple, but =

> one of the main issue I had when I once started reading RFCs =

> was the very scarce and poor usage of this simple vocabulary, =

> "Updates", "Obsoletes", and "Also".
> My perception frequently was that there were far too many =

> MUSTs and SHOULDs and MAYs inside the documents, and far too =

> few "Udates" helping the reader navigate the RFCs, in the metadata.
> (It's similar to web pages with no hyperlinks on 'home pages'
> [or equivalent] pointing to them!)
> =

> Any implementor or analyst reading RFC 793 should be made =

> aware of the tcpsecure RFC, as soon as it is out (and I =

> really hope to see it soon in the RFC index!), because that =

> document contains qualified statements this working group has judged.
> [... in an incommensurate long period of discussion holding =

> off this long-expected document -- personal note.] He/she =

> should be pointed to this document by the RFC metadata, and =

> should read it (the latter seems to be the consensus of the =

> WG, isn't it?) -- otherwise publishing the document would be =

> rather moot.
> =

> The "Updated by" metadata links do not imply requirements =

> language in any way, they point the reader to documents that
> (hopefully) contain an applicability statement and their own, =

> and detailed requirements language.
> =

> If a new document adds, e.g., new options, to properly =

> designed extensibility hooks of a protocol, without =

> affecting/changing processing rules of the protocol, that =

> memo does not "Update"
> the base document for that protocol, and that document can be =

> easily picked up by tracing the IANA Registry for the =

> namespace forming the extensibility hook.  But if a document =

> discusses new requirements for a protocol that have come up =

> in the real world, and it contains 'considerations' about =

> modifications to the processing rules laid down in another =

> document (which in this particular case already have been =

> adopted by most significant players in the marketplace as =

> inevitable and indispensible changes for security reasons), =

> this new document SHOULD be tagged in the RFC metadata as =

> "Updates <the old one>".
> =

> Don't forget:
> This WG is chartered for the *MAINTENANCE* of TCP.
> If you don't want to make that maintenace visible, you are in =

> danger to dismiss your mission (and the mission of the IETF =

> and its Standards Process).  Since RFCs are immutable, RFC =

> Errata and additions to the RFC metadata are the only ways to =

> make an act of maintenance for a document visible at first place.
> =

> I only see one other option (but I guess that's not a real =

> option in practice, due to workload): *regularly* update RFC 4614 .
> Such documents (and there are far too few of this kind!) =

> provide enough space to discuss the nuances of conditional =

> MUSTs and SHOULDs in case of applicability etc. etc. at =

> length, if deemed necessary.
> =

> Therefore my recommendation:
> =

> +++   Be very careful with "Obsoletes", but be generous
> +++   with "Updates", for the benefit of RFC readers !
> =

> Kind regards,
>   Alfred.
> =

> =

> P.S.:
> The discussion has mentioned the tiny number of "Updated by"
> for RFC 793, one of the oldest and most important standards =

> of the IETF.  Many technicians not aware of the discussions =

> in this WG would take this as a severe indication, or even =

> evidence for lack of maintenance for TCP!
> =

> -- =

> =

> +------------------------+------------------------------------
> --------+
> | TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math., =

> Dipl.-Phys.  |
> | Gerlinger Strasse 12   |  Phone: (+49)7156/9635-0, Fax: -18 =

>         |
> | D-71254  Ditzingen     |  E-Mail:  ah@TR-Sys.de             =

>         |
> +------------------------+------------------------------------
> --------+
> =

> =

> =

> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm
> =

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Tue Sep 30 15:30:25 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7C29F3A6BCF;
	Tue, 30 Sep 2008 15:30:25 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 308013A6800;
	Tue, 30 Sep 2008 15:30:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5
	tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3hM7ufbE340q; Tue, 30 Sep 2008 15:30:23 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id 6CA983A691B;
	Tue, 30 Sep 2008 15:30:23 -0700 (PDT)
Received: from [192.168.1.45] (pool-71-106-119-240.lsanca.dsl-w.verizon.net
	[71.106.119.240])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m8UMU6K6019036
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Tue, 30 Sep 2008 15:30:08 -0700 (PDT)
Message-ID: <48E2A86E.5050602@isi.edu>
Date: Tue, 30 Sep 2008 15:30:06 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: =?UTF-8?B?QWxmcmVkIO+/vQ==?= <ah@tr-sys.de>
References: <200809302002.WAA09122@TR-Sys.de>
In-Reply-To: <200809302002.WAA09122@TR-Sys.de>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tcpm@ietf.org, iesg@iesg.org
Subject: Re: [tcpm] exegesis of 'Updates' -- was: ... review
	of	draft-ietf-tcpm-tcpsecure[-10]
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQpIYXNoOiBTSEExCgoKCkFsZnJlZCDv
v70gd3JvdGU6Ci4uLgo+IFRoZXJlZm9yZSBteSByZWNvbW1lbmRhdGlvbjoKPiAKPiArKysgICBC
ZSB2ZXJ5IGNhcmVmdWwgd2l0aCAiT2Jzb2xldGVzIiwgYnV0IGJlIGdlbmVyb3VzCj4gKysrICAg
d2l0aCAiVXBkYXRlcyIsIGZvciB0aGUgYmVuZWZpdCBvZiBSRkMgcmVhZGVycyAhCgpXZWxsLCB3
ZSB1c2VkIHRvIGhhdmUgYSBnZW5lcmFsIHJ1bGU6CgoJQmUgY29uc2VydmF0aXZlIGluIHdoYXQg
eW91IHNlbmQsCgliZSBsaWJlcmFsIGluIHdoYXQgeW91IHJlY2VpdmUuCgpUaGUgc2Vjb25kIHJ1
bGUgaXMgYmVudCBieSB0Y3BzZWN1cmUsIHdoaWNoIGludGVycHJldHMgdW5leHBlY3RlZApzZWdt
ZW50cyBhcyBhdHRhY2tzIG5lZWRpbmcgZGVmZW5zZS4KCkFzIGEgcmVzdWx0LCB3ZSdyZSBoZXJl
IGNvbnNpZGVyaW5nIHJlYXNvbnMgbm90IHRvIHB1dCBVcGRhdGVzIGluIHRoZQpoZWFkZXIsIHRv
IGF2b2lkIHRvbyBzdHJvbmdseSBpbXBseWluZyB0aGF0IGFsbCBUQ1BzIGV2ZXJ5d2hlcmUgbmVl
ZCB0bwpiZSBhdWdtZW50ZWQgd2l0aCBhbiBJUFItZW5jdW1iZXJlZCBwb29yIHN1YnN0aXR1dGUg
Zm9yIHRydWUgc2VjdXJpdHkuCgpNeSBjb25jbHVzaW9uIGlzIHRoYXQsIGFsdGhvdWdoIEkgYWdy
ZWUgd2l0aCBBbGZyZWQgaW4gc3Bpcml0LCBJIGNhbid0CnNlZSB3aHkgd2Ugc2hvdWxkIGJlIG1v
cmUgbGliZXJhbCB3aXRoIFVwZGF0ZXMgdGhhbiB3ZSBhcmUgd2l0aCBzZWdtZW50cwp3ZSByZWNl
aXZlLgoKSm9lCi0tLS0tQkVHSU4gUEdQIFNJR05BVFVSRS0tLS0tClZlcnNpb246IEdudVBHIHYx
LjQuOSAoTWluZ1czMikKQ29tbWVudDogVXNpbmcgR251UEcgd2l0aCBNb3ppbGxhIC0gaHR0cDov
L2VuaWdtYWlsLm1vemRldi5vcmcKCmlFWUVBUkVDQUFZRkFramlxRzRBQ2drUUU1ZjVjSW1uWnJ1
dzR3Q2NESUhzcmpGOG1Ud3dNUk0xTjhZQjd2YzAKU1JZQW5qNlpYRmZ6aEZnekN6VWdJTW9mR1V1
MlNWZ2oKPVpBUFEKLS0tLS1FTkQgUEdQIFNJR05BVFVSRS0tLS0tCl9fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCnRjcG0gbWFpbGluZyBsaXN0CnRjcG1AaWV0
Zi5vcmcKaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby90Y3BtCg==


From tcpm-bounces@ietf.org  Tue Sep 30 16:19:19 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6CA793A6B26;
	Tue, 30 Sep 2008 16:19:19 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A5DFF3A68DA
	for <tcpm@core3.amsl.com>; Tue, 30 Sep 2008 16:19:17 -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=[AWL=0.050, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5CmX3dUNqq4r for <tcpm@core3.amsl.com>;
	Tue, 30 Sep 2008 16:19:16 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id 687373A69E1
	for <tcpm@ietf.org>; Tue, 30 Sep 2008 16:19:16 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,341,1220227200"; d="scan'208";a="85047212"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-1.cisco.com with ESMTP; 30 Sep 2008 23:19:38 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m8UNJcvx001701; 
	Tue, 30 Sep 2008 16:19:38 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m8UNJcvt005235;
	Tue, 30 Sep 2008 23:19:38 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); 
	Tue, 30 Sep 2008 16:19:38 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 30 Sep 2008 16:19:36 -0700
Message-ID: <0C53DCFB700D144284A584F54711EC5805DF4D6F@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <48E2A86E.5050602@isi.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcpm] exegesis of 'Updates' -- was: ...
	reviewof	draft-ietf-tcpm-tcpsecure[-10]
Thread-Index: AckjTDC6+yaiS2DHTIeZTjxJ9pyv5wAA5YEQ
References: <200809302002.WAA09122@TR-Sys.de> <48E2A86E.5050602@isi.edu>
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: "Joe Touch" <touch@ISI.EDU>, =?UTF-8?B?QWxmcmVkIO+/vQ==?= <ah@tr-sys.de>
X-OriginalArrivalTime: 30 Sep 2008 23:19:38.0599 (UTC)
	FILETIME=[0261C770:01C92353]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4296; t=1222816778;
	x=1223680778; 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[tcpm]=20exegesis=20of=20'Updates'=20--
	=20was=3A=20...=20reviewof=09draft-ietf-tcpm-tcpsecure[-10]
	|Sender:=20; bh=iaYqFBVzaUXxyxZPHucSeL4gWpael5ZfJjwcztxJ4uU=;
	b=vahSnUFAUiIaDCkg4lLe++nDU5Xn7HR9zroG1bGlz8woqhfqqrmlMTHy3B
	/2DiXdBeYyd9nREF3Pbp3Qy+pN5SJpDIRrR9yq/T9MyLobK8bq0/JPkIhgeL
	fmgeXrEuPS;
Authentication-Results: sj-dkim-2; header.From=ananth@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: tcpm@ietf.org, iesg@iesg.org
Subject: Re: [tcpm] exegesis of 'Updates' -- was: ...
	reviewof	draft-ietf-tcpm-tcpsecure[-10]
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

Joe, 

> -----Original Message-----
> From: tcpm-bounces@ietf.org [mailto:tcpm-bounces@ietf.org] On 
> Behalf Of Joe Touch
> Sent: Tuesday, September 30, 2008 3:30 PM
> To: Alfred  
> Cc: tcpm@ietf.org; iesg@iesg.org
> Subject: Re: [tcpm] exegesis of 'Updates' -- was: ... 
> reviewof draft-ietf-tcpm-tcpsecure[-10]
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> 
> Alfred   wrote:
> ...
> > Therefore my recommendation:
> > 
> > +++   Be very careful with "Obsoletes", but be generous
> > +++   with "Updates", for the benefit of RFC readers !
> 
> Well, we used to have a general rule:
> 
> 	Be conservative in what you send,
> 	be liberal in what you receive.
> 
> The second rule is bent by tcpsecure, which interprets 
> unexpected segments as attacks needing defense.

You have blown this trumphet from day one, so nothing new, really. Like it has been clarified by many folks umpteen number of times, tcp-secure improves robustness of TCP w.r.t processing in-window RSTs, SYNs and Data injection. If you think by doing so we have punched a hole in "liberality", that is your personal take. Not sure why we are even debating this now, during last call! We have moved on from this line a long time back!

> 
> As a result, we're here considering reasons not to put 
> Updates in the header, to avoid too strongly implying that 
> all TCPs everywhere need to be augmented with an 
> IPR-encumbered poor substitute for true security.

IPR issue was raised when the document was initially presented 3+ years ago!. Scott Bradner made a presentation to clarify the IPR intent and after that this, the IPR issue was never considered as a hindrance for the draft to move forward. Agreed that the IPR issue might have had some influence w.r.t the verbiage on the strength of mitigations. Lars Eggert suggested an applicability statement to be added, we added the same. Not sure why you are bringing this up now, the IPR issue was beaten to death long time back.

Again, my current understanding (which is inline with Alfred) is about "if a draft changes the TCP RFC 793 rules in some way, then it is considered as an update and we should mark it accordingly upfront for easy reference purposes" Also, update doesn't mean that "all TCP's everywhere need to be augumented with the changes". An implementer would read the mitigations, AS and the strength of recommended mitigations and would make his/her own choice!

> 
> My conclusion is that, although I agree with Alfred in 
> spirit, I can't see why we should be more liberal with 
> Updates than we are with segments we receive.

IMO, these two are completely 2 different things!

-Anantha
> 
> Joe
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iEYEARECAAYFAkjiqG4ACgkQE5f5cImnZruw4wCcDIHsrjF8mTwwMRM1N8YB7vc0
> SRYAnj6ZXFfzhFgzCzUgIMofGUu2SVgj
> =ZAPQ
> -----END PGP SIGNATURE-----
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm
> 
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Tue Sep 30 16:42:17 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AD4D328C19E;
	Tue, 30 Sep 2008 16:42:17 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1AB0F3A6B31;
	Tue, 30 Sep 2008 16:42:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.582
X-Spam-Level: 
X-Spam-Status: No, score=-2.582 tagged_above=-999 required=5 tests=[AWL=0.017, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jVnCF+PoCEdN; Tue, 30 Sep 2008 16:42:16 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id 430DF3A68DA;
	Tue, 30 Sep 2008 16:42:16 -0700 (PDT)
Received: from [192.168.1.45] (pool-71-106-119-240.lsanca.dsl-w.verizon.net
	[71.106.119.240])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m8UNgB17003712
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Tue, 30 Sep 2008 16:42:13 -0700 (PDT)
Message-ID: <48E2B952.6080109@isi.edu>
Date: Tue, 30 Sep 2008 16:42:10 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
References: <200809302002.WAA09122@TR-Sys.de> <48E2A86E.5050602@isi.edu>
	<0C53DCFB700D144284A584F54711EC5805DF4D6F@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <0C53DCFB700D144284A584F54711EC5805DF4D6F@xmb-sjc-21c.amer.cisco.com>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: =?UTF-8?B?QWxmcmVkIO+/vQ==?= <ah@tr-sys.de>, tcpm@ietf.org, iesg@iesg.org
Subject: Re: [tcpm] exegesis of 'Updates' -- was: ...
	reviewof	draft-ietf-tcpm-tcpsecure[-10]
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Anantha Ramaiah (ananth) wrote:
...
> As a result, we're here considering reasons not to put 
> Updates in the header, to avoid too strongly implying that 
> all TCPs everywhere need to be augmented with an 
> IPR-encumbered poor substitute for true security.
>--- 
> IPR issue was raised when the document was initially presented 3+
> years ago!. Scott Bradner made a presentation to clarify the IPR intent
> and after that this, the IPR issue was never considered as a hindrance
> for the draft to move forward. 

That is proven incorrect by your next sentence.

> Agreed that the IPR issue might have had
> some influence w.r.t the verbiage on the strength of mitigations. Lars
> Eggert suggested an applicability statement to be added, we added the
> same. Not sure why you are bringing this up now, the IPR issue was
> beaten to death long time back.

It is relevant to the issue of Updates, just as it was during the
MUST/SHOULD/MAY discussions.

> Again, my current understanding (which is inline with Alfred) is
> about "if a draft changes the TCP RFC 793 rules in some way, then it
> is considered as an update and we should mark it accordingly upfront
> for easy reference purposes" Also, update doesn't mean that "all
> TCP's everywhere need to be augumented with the changes". An
> implementer would read the mitigations, AS and the strength of
> recommended mitigations and would make his/her own choice!

Others have shown cases where modifications with more ubiquitous utility
do not carry the Updates tag. There is no evidence this mod is more
deserving of that tag.

Joe

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

iEYEARECAAYFAkjiuVIACgkQE5f5cImnZrtfDgCfX5bTX25wVirTbOC34+pVjrfm
djgAoIXI3OFh2rmsgDJgVMEDcYpH4rXB
=isFm
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Tue Sep 30 17:35:27 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D9D933A6A2E;
	Tue, 30 Sep 2008 17:35:27 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3789E28C158
	for <tcpm@core3.amsl.com>; Tue, 30 Sep 2008 17:35:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.403
X-Spam-Level: 
X-Spam-Status: No, score=-6.403 tagged_above=-999 required=5 tests=[AWL=0.196, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id bve+TcbBnp6j for <tcpm@core3.amsl.com>;
	Tue, 30 Sep 2008 17:35:25 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id 057923A6A2E
	for <tcpm@ietf.org>; Tue, 30 Sep 2008 17:35:25 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,341,1220227200"; d="scan'208";a="85079773"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-1.cisco.com with ESMTP; 01 Oct 2008 00:35:25 +0000
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 m910ZPrK023102; 
	Tue, 30 Sep 2008 17:35:25 -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.13.8/8.13.8) with ESMTP id m910ZPAQ025425;
	Wed, 1 Oct 2008 00:35:25 GMT
Received: from xmb-sjc-21c.amer.cisco.com ([171.70.151.176]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 30 Sep 2008 17:35:25 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 30 Sep 2008 17:35:24 -0700
Message-ID: <0C53DCFB700D144284A584F54711EC5805DF4DF8@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <48E2B952.6080109@isi.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcpm] exegesis of 'Updates' -- was: ...
	reviewof	draft-ietf-tcpm-tcpsecure[-10]
Thread-Index: AckjVjj2hg+qd60LT8CzKuMibdO8YQAAT8Iw
References: <200809302002.WAA09122@TR-Sys.de> <48E2A86E.5050602@isi.edu>
	<0C53DCFB700D144284A584F54711EC5805DF4D6F@xmb-sjc-21c.amer.cisco.com>
	<48E2B952.6080109@isi.edu>
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: "Joe Touch" <touch@ISI.EDU>
X-OriginalArrivalTime: 01 Oct 2008 00:35:25.0403 (UTC)
	FILETIME=[987D02B0:01C9235D]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3568; t=1222821325;
	x=1223685325; c=relaxed/simple; s=sjdkim1004;
	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[tcpm]=20exegesis=20of=20'Updates'=20--
	=20was=3A=20...=20reviewof=09draft-ietf-tcpm-tcpsecure[-10]
	|Sender:=20; bh=Oh5TvDf1auw4C10DZvKGWEqH6HBC8Yr2paJix/rFjrE=;
	b=nepR98cBIkMJ3D/Wx+vKYYd07LdAArA6k5kY72QgBLMl4FHZkOBrFdtIAf
	FBWZsT38a8E3M+POweK0sOhdtrVOCKAEC0WMm0/tRAZ1+mKZDYyjFIiW9oY3
	SwoKjvGrLpfhnu612GMjMAHS18Nr0fOQPSOYkh/9sOrMk2F28qw2w=;
Authentication-Results: sj-dkim-1; header.From=ananth@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: =?UTF-8?B?QWxmcmVkIO+/vQ==?= <ah@tr-sys.de>, tcpm@ietf.org, iesg@iesg.org
Subject: Re: [tcpm] exegesis of 'Updates' -- was: ...
	reviewof	draft-ietf-tcpm-tcpsecure[-10]
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org


<snip>
 
> 
> > Agreed that the IPR issue might have had some influence w.r.t the 
> > verbiage on the strength of mitigations. Lars Eggert suggested an 
> > applicability statement to be added, we added the same. Not 
> sure why 
> > you are bringing this up now, the IPR issue was beaten to 
> death long 
> > time back.
> 
> It is relevant to the issue of Updates, just as it was during 
> the MUST/SHOULD/MAY discussions.

Atleast this is the first time I am hearing that IPR issue is relevant to the "updates" issue.


> 
> > Again, my current understanding (which is inline with 
> Alfred) is about 
> > "if a draft changes the TCP RFC 793 rules in some way, then it is 
> > considered as an update and we should mark it accordingly 
> upfront for 
> > easy reference purposes" Also, update doesn't mean that "all TCP's 
> > everywhere need to be augumented with the changes". An implementer 
> > would read the mitigations, AS and the strength of recommended 
> > mitigations and would make his/her own choice!
> 
> Others have shown cases where modifications with more 
> ubiquitous utility do not carry the Updates tag. There is no 
> evidence this mod is more deserving of that tag.

The word deserving comes across quite funny to me! Even though modifications with more ubiquitous utility in the past might have missed the "updates" clause (may be due to hindsight), that is a not a reason why we shouldn't use the "updates" tag for a document which actually updates something in 793, IMO. To quote Alfred : [ sorry, it is easier rather than me framing a new sentence altogether]

"
This WG is chartered for the *MAINTENANCE* of TCP.
If you don't want to make that maintenace visible, you are in danger to dismiss your mission (and the mission of the IETF and its Standards Process).  Since RFCs are immutable, RFC Errata and additions to the RFC metadata are the only ways to make an act of maintenance for a document visible at first place."

Well, 1323 and 2581 was mentioned as mods (if that is what you are referring to above). My reply was :

" FWIW, 1323 talks "TCP extensions for High performance" about window scaling ( a new TCP option), timestamps ( a new TCP option) and PAWS (which "is possible only when you use timestamps), these don't update RFC 793 and just supplements it, IMO.

RFC 1122 standardized the TCP congestion control algorithms and not RFC 793. So if it all 2581 has to update something it had to be 1122 not 793."

Anyways, this is my line of thinking and I haven't heard any convincing arguments so far. 

-Anantha
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From tcpm-bounces@ietf.org  Tue Sep 30 17:53:04 2008
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 760BA28C166;
	Tue, 30 Sep 2008 17:53:04 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9D8043A68BC;
	Tue, 30 Sep 2008 17:53:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.584
X-Spam-Level: 
X-Spam-Status: No, score=-2.584 tagged_above=-999 required=5 tests=[AWL=0.015, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vD7rx5rPB0Fi; Tue, 30 Sep 2008 17:53:01 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id C518E3A691C;
	Tue, 30 Sep 2008 17:53:01 -0700 (PDT)
Received: from [192.168.1.45] (pool-71-106-119-240.lsanca.dsl-w.verizon.net
	[71.106.119.240])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m910qiLb016266
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Tue, 30 Sep 2008 17:52:46 -0700 (PDT)
Message-ID: <48E2C9DC.5000607@isi.edu>
Date: Tue, 30 Sep 2008 17:52:44 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
References: <200809302002.WAA09122@TR-Sys.de> <48E2A86E.5050602@isi.edu>
	<0C53DCFB700D144284A584F54711EC5805DF4D6F@xmb-sjc-21c.amer.cisco.com>
	<48E2B952.6080109@isi.edu>
	<0C53DCFB700D144284A584F54711EC5805DF4DF8@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <0C53DCFB700D144284A584F54711EC5805DF4DF8@xmb-sjc-21c.amer.cisco.com>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: =?UTF-8?B?QWxmcmVkIO+/vQ==?= <ah@tr-sys.de>, tcpm@ietf.org, iesg@iesg.org
Subject: Re: [tcpm] exegesis of 'Updates' -- was: ...
	reviewof	draft-ietf-tcpm-tcpsecure[-10]
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>,
	<mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Anantha Ramaiah (ananth) wrote:
> <snip>
...
> RFC 1122 standardized the TCP congestion control algorithms and not RFC 793.
> So if it all 2581 has to update something it had to be 1122 not 793."
> 
> Anyways, this is my line of thinking and I haven't heard any convincing arguments so far. 

So why do you believe that 2581 updates 1122 and not 793? Or that 1122
wouldn't thus also update 793? Changes to the congestion control
algorithm are equivalent to the changes you propose - they change
behavior (reaction to certain events), but not the fundamental state
machine.

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

iEYEARECAAYFAkjiydwACgkQE5f5cImnZrufsgCffeaSP9EpzLYtfrXNzsnU5c3u
sXoAoNjRH8UgQEkfo9lhQZxq7MrahoDs
=Flme
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


