
From KENNETH.G.CARLBERG@saic.com  Tue Jun  2 07:16:02 2009
Return-Path: <KENNETH.G.CARLBERG@saic.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D90143A693A for <tsvwg@core3.amsl.com>; Tue,  2 Jun 2009 07:16:02 -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 9tSq8EmXUeyn for <tsvwg@core3.amsl.com>; Tue,  2 Jun 2009 07:16:02 -0700 (PDT)
Received: from mclmx2.mail.saic.com (mclmx2.mail.saic.com [149.8.64.32]) by core3.amsl.com (Postfix) with ESMTP id 30E2E3A6ECB for <tsvwg@ietf.org>; Tue,  2 Jun 2009 07:15:58 -0700 (PDT)
Received: from 0015-ITS-SMS02 ([149.8.64.21] [149.8.64.21]) by mclmx2.mail.saic.com with ESMTP id BT-MMP-5643581; Tue, 2 Jun 2009 10:15:25 -0400
X-AuditID: 9508402f-abbb0ba000006bc2-a8-4a2533fce7c3
Received: from 0015-its-exbh03.us.saic.com (unknown [149.8.64.21]) by 0015-ITS-SMS02 (Symantec Mail Security) with ESMTP id EBFE5594124; Tue,  2 Jun 2009 10:15:24 -0400 (EDT)
Received: from 0015-its-exmb11.us.saic.com ([10.43.229.22]) by 0015-its-exbh03.us.saic.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 2 Jun 2009 10:15:25 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 2 Jun 2009 10:15:24 -0400
Message-Id: <B111EEAA42CD0F4D85A5E486368D155A024D109B@0015-its-exmb11.us.saic.com>
In-Reply-To: <D24156B9-B8A6-4552-9642-B366DE07B7EB@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Tsvwg] Review of draft-ietf-tsvwg-rsvp-security-groupkeying-04
Thread-Index: AcnN3C7N8rc/XN/qQkSJrm3ALaOEKwVqtm2g
References: <D24156B9-B8A6-4552-9642-B366DE07B7EB@cisco.com>
From: "Carlberg, Kenneth G." <KENNETH.G.CARLBERG@saic.com>
To: "Francois Le Faucheur IMAP" <flefauch@cisco.com>, "Michael Behringer" <mbehring@cisco.com>
X-OriginalArrivalTime: 02 Jun 2009 14:15:25.0304 (UTC) FILETIME=[92B51F80:01C9E38C]
X-Brightmail-Tracker: AAAAAA==
Cc: tsvwg IETF list <tsvwg@ietf.org>
Subject: Re: [Tsvwg] Review of draft-ietf-tsvwg-rsvp-security-groupkeying-04
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jun 2009 14:16:02 -0000

Francois & Michael,

Here is another review of the draft.  Its mostly comprised of nits and
requests for additional clarification.

-ken


1) page 4,  "Implicitly each node trusts each other node with which
   it has a trust relationship established via the mechanisms here to
   adhere to the protocol specifications laid out by the various
   standards."

The sentence is a bit long and confusing.  You need to break up the
sentence and clarify the content of the word "here".  Also,
s/other/other's
=20

2) page 5, 3'rd para.  s/R2 and will ignore/R2 will ignore

3) page 5, 5'th para. =20
   "With neighbor based keys, an RSVP key is bound to an interface plus
a
   neighbor on that interface.  It allows the distinction of different
   trust groups on a single subnet.  (Assuming that layer-2 security is
   correctly implemented to prevent layer-2 attacks.)"

Does the above text concerning neighbor based keys allow for different
trust groups per interface?  If so, this should be stated to the reader.

4) Page 6, 5'th para.  s/domains however/domains. However

5) page 14, 2'nd para.
   "In
   particular, such keying can be used for RSVP authentication (e.g.,
   using RSVP authentication or IPsec AH) and/ or for RSVP encryption
   (e.g., using IPsec ESP in tunnel mode)."

The sentence is a bit unclear with respect to using the term RSVP
authentication as an example of keying "used for RSVP authentication".
You'll either need to clarify the text, or just rely on IPsec AH as a
single example.

6) Page 15, late sentence of 4'th para. =20
   "Therefore the impact of subverted nodes on the path is comparable,
   independently whether per-interface, per-neighbor or group keys are
   used."

The reader would probably ask, comparable to what?  It would be helpful
if you could complete the object of the sentence.


From sheela@cisco.com  Tue Jun  2 21:55:06 2009
Return-Path: <sheela@cisco.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4B2AF3A6AC8 for <tsvwg@core3.amsl.com>; Tue,  2 Jun 2009 21:55:06 -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 OG1O-064pc-D for <tsvwg@core3.amsl.com>; Tue,  2 Jun 2009 21:55:04 -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 70F9E3A6870 for <tsvwg@ietf.org>; Tue,  2 Jun 2009 21:54:54 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.41,295,1241395200"; d="scan'208";a="78845917"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-5.cisco.com with ESMTP; 03 Jun 2009 04:54:55 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n534stlN030943;  Tue, 2 Jun 2009 21:54:55 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n534st0Y027148; Wed, 3 Jun 2009 04:54:55 GMT
Received: from xmb-sjc-224.amer.cisco.com ([128.107.191.98]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Tue, 2 Jun 2009 21:54:55 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 2 Jun 2009 21:54:53 -0700
Message-ID: <6B9C4B97B82F924485E26968EB05A6EE070D9B08@xmb-sjc-224.amer.cisco.com>
In-Reply-To: <B111EEAA42CD0F4D85A5E486368D155A024D109B@0015-its-exmb11.us.saic.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Tsvwg] Review of draft-ietf-tsvwg-rsvp-security-groupkeying-04
Thread-Index: AcnN3C7N8rc/XN/qQkSJrm3ALaOEKwVqtm2gACAPW/A=
References: <D24156B9-B8A6-4552-9642-B366DE07B7EB@cisco.com> <B111EEAA42CD0F4D85A5E486368D155A024D109B@0015-its-exmb11.us.saic.com>
From: "Sheela Rowles (sheela)" <sheela@cisco.com>
To: "Carlberg, Kenneth G." <KENNETH.G.CARLBERG@saic.com>, "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>, "Michael Behringer (mbehring)" <mbehring@cisco.com>
X-OriginalArrivalTime: 03 Jun 2009 04:54:55.0761 (UTC) FILETIME=[7059D810:01C9E407]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2346; t=1244004895; x=1244868895; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=sheela@cisco.com; z=From:=20=22Sheela=20Rowles=20(sheela)=22=20<sheela@cisco.c om> |Subject:=20RE=3A=20[Tsvwg]=20Review=20of=20draft-ietf-tsvw g-rsvp-security-groupkeying-04 |Sender:=20; bh=EXff4nAFuLrATdMzSWDrAKYCJ/X8sANajgpDDd0O8+I=; b=WGWpmTuP7uglMGndnuHk7EIWGHIsXANJWmhS7todP8o3j5uY2fDtQZjQ0u YFT5yrakq4G1HJSXItgxvmF97FBHJJN3s6jxYHgkws4aVN0/IRjOI1lgeo1K qhqjxN1VZ3;
Authentication-Results: sj-dkim-2; header.From=sheela@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Cc: tsvwg IETF list <tsvwg@ietf.org>
Subject: Re: [Tsvwg] Review of draft-ietf-tsvwg-rsvp-security-groupkeying-04
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jun 2009 04:55:06 -0000

Francois & Michael,

I'm also planning to review the draft.  I hope to complete the review
within a week or two. =20

Sheela=20

-----Original Message-----
From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf
Of Carlberg, Kenneth G.
Sent: Tuesday, June 02, 2009 7:15 AM
To: Francois Le Faucheur (flefauch); Michael Behringer (mbehring)
Cc: tsvwg IETF list
Subject: Re: [Tsvwg] Review of
draft-ietf-tsvwg-rsvp-security-groupkeying-04

Francois & Michael,

Here is another review of the draft.  Its mostly comprised of nits and
requests for additional clarification.

-ken


1) page 4,  "Implicitly each node trusts each other node with which
   it has a trust relationship established via the mechanisms here to
   adhere to the protocol specifications laid out by the various
   standards."

The sentence is a bit long and confusing.  You need to break up the
sentence and clarify the content of the word "here".  Also,
s/other/other's
=20

2) page 5, 3'rd para.  s/R2 and will ignore/R2 will ignore

3) page 5, 5'th para. =20
   "With neighbor based keys, an RSVP key is bound to an interface plus
a
   neighbor on that interface.  It allows the distinction of different
   trust groups on a single subnet.  (Assuming that layer-2 security is
   correctly implemented to prevent layer-2 attacks.)"

Does the above text concerning neighbor based keys allow for different
trust groups per interface?  If so, this should be stated to the reader.

4) Page 6, 5'th para.  s/domains however/domains. However

5) page 14, 2'nd para.
   "In
   particular, such keying can be used for RSVP authentication (e.g.,
   using RSVP authentication or IPsec AH) and/ or for RSVP encryption
   (e.g., using IPsec ESP in tunnel mode)."

The sentence is a bit unclear with respect to using the term RSVP
authentication as an example of keying "used for RSVP authentication".
You'll either need to clarify the text, or just rely on IPsec AH as a
single example.

6) Page 15, late sentence of 4'th para. =20
   "Therefore the impact of subverted nodes on the path is comparable,
   independently whether per-interface, per-neighbor or group keys are
   used."

The reader would probably ask, comparable to what?  It would be helpful
if you could complete the object of the sentence.


From flefauch@cisco.com  Wed Jun  3 01:33:53 2009
Return-Path: <flefauch@cisco.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B6BD73A6781 for <tsvwg@core3.amsl.com>; Wed,  3 Jun 2009 01:33:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QXTKiis+4ndU for <tsvwg@core3.amsl.com>; Wed,  3 Jun 2009 01:33:52 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id C921D3A6BAE for <tsvwg@ietf.org>; Wed,  3 Jun 2009 01:33:36 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.41,297,1241395200"; d="scan'208";a="41909825"
Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 03 Jun 2009 08:33:36 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n538XaKQ009998;  Wed, 3 Jun 2009 10:33:36 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com [144.254.231.87]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n538XajX028542; Wed, 3 Jun 2009 08:33:36 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 3 Jun 2009 10:33:36 +0200
Received: from ams-flefauch-8712.cisco.com ([10.55.161.195]) by xfe-ams-332.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 3 Jun 2009 10:33:35 +0200
Message-Id: <24A68080-B12A-41F9-8516-81B33E273A41@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
To: "James Polk M." <jmpolk@cisco.com>, Gorry Fairhurst <gorry@erg.abdn.ac.uk>, Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <6B9C4B97B82F924485E26968EB05A6EE070D9B08@xmb-sjc-224.amer.cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Wed, 3 Jun 2009 10:33:33 +0200
References: <D24156B9-B8A6-4552-9642-B366DE07B7EB@cisco.com> <B111EEAA42CD0F4D85A5E486368D155A024D109B@0015-its-exmb11.us.saic.com> <6B9C4B97B82F924485E26968EB05A6EE070D9B08@xmb-sjc-224.amer.cisco.com>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 03 Jun 2009 08:33:36.0118 (UTC) FILETIME=[FCB17160:01C9E425]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2934; t=1244018016; x=1244882016; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=flefauch@cisco.com; z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco. com> |Subject:=20Re=3A=20[Tsvwg]=20Review=20of=20draft-ietf-tsvw g-rsvp-security-groupkeying-04 |Sender:=20; bh=MMSfx1dO9MBtS/RRfA+av5DOYtA5gVe4nem1Z1QRUyY=; b=Ob+HttTJVn2on3DOgGXNDryUUQCberVOVscB3wnmrkipsUmkC7EyjfD3MD L9DSeWBN4mBhh147lTnjJPQh4Rro+gGqaYZ/eRiFwWEguxSWS90Vbe7ysfTt 7IxRYIA/9Y;
Authentication-Results: ams-dkim-1; header.From=flefauch@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; ); 
Cc: tsvwg IETF list <tsvwg@ietf.org>, "Michael Behringer \(mbehring\)" <mbehring@cisco.com>
Subject: Re: [Tsvwg] Review of draft-ietf-tsvwg-rsvp-security-groupkeying-04
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jun 2009 08:33:53 -0000

Hi James, Gorry, Lars,

At last IETF, Lars conditioned Last Calling of rsvp-security- 
groupkeying on getting explicit commitments from subject experts that  
they will indeed review the doc.
Considering that, since then, Brian Weis, Bob Briscoe and Ken Carlberg  
have posted their full review comments and Sheela just committed to  
also do a review, would it be appropriate to move to Last Call now?

Thanks

Francois

On 3 Jun 2009, at 06:54, Sheela Rowles (sheela) wrote:

> Francois & Michael,
>
> I'm also planning to review the draft.  I hope to complete the review
> within a week or two.
>
> Sheela
>
> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf
> Of Carlberg, Kenneth G.
> Sent: Tuesday, June 02, 2009 7:15 AM
> To: Francois Le Faucheur (flefauch); Michael Behringer (mbehring)
> Cc: tsvwg IETF list
> Subject: Re: [Tsvwg] Review of
> draft-ietf-tsvwg-rsvp-security-groupkeying-04
>
> Francois & Michael,
>
> Here is another review of the draft.  Its mostly comprised of nits and
> requests for additional clarification.
>
> -ken
>
>
> 1) page 4,  "Implicitly each node trusts each other node with which
>   it has a trust relationship established via the mechanisms here to
>   adhere to the protocol specifications laid out by the various
>   standards."
>
> The sentence is a bit long and confusing.  You need to break up the
> sentence and clarify the content of the word "here".  Also,
> s/other/other's
>
>
> 2) page 5, 3'rd para.  s/R2 and will ignore/R2 will ignore
>
> 3) page 5, 5'th para.
>   "With neighbor based keys, an RSVP key is bound to an interface plus
> a
>   neighbor on that interface.  It allows the distinction of different
>   trust groups on a single subnet.  (Assuming that layer-2 security is
>   correctly implemented to prevent layer-2 attacks.)"
>
> Does the above text concerning neighbor based keys allow for different
> trust groups per interface?  If so, this should be stated to the  
> reader.
>
> 4) Page 6, 5'th para.  s/domains however/domains. However
>
> 5) page 14, 2'nd para.
>   "In
>   particular, such keying can be used for RSVP authentication (e.g.,
>   using RSVP authentication or IPsec AH) and/ or for RSVP encryption
>   (e.g., using IPsec ESP in tunnel mode)."
>
> The sentence is a bit unclear with respect to using the term RSVP
> authentication as an example of keying "used for RSVP authentication".
> You'll either need to clarify the text, or just rely on IPsec AH as a
> single example.
>
> 6) Page 15, late sentence of 4'th para.
>   "Therefore the impact of subverted nodes on the path is comparable,
>   independently whether per-interface, per-neighbor or group keys are
>   used."
>
> The reader would probably ask, comparable to what?  It would be  
> helpful
> if you could complete the object of the sentence.
>


From mbehring@cisco.com  Wed Jun  3 02:58:09 2009
Return-Path: <mbehring@cisco.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E5EBA3A6C66 for <tsvwg@core3.amsl.com>; Wed,  3 Jun 2009 02:58:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wHBQjmPHU-NY for <tsvwg@core3.amsl.com>; Wed,  3 Jun 2009 02:58:09 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 87E663A68FA for <tsvwg@ietf.org>; Wed,  3 Jun 2009 02:58:08 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.41,297,1241395200"; d="scan'208";a="41923996"
Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 03 Jun 2009 09:58:08 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n539w8UE010927 for <tsvwg@ietf.org>; Wed, 3 Jun 2009 11:58:08 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com [144.254.231.87]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n539w8E2005484 for <tsvwg@ietf.org>; Wed, 3 Jun 2009 09:58:08 GMT
Received: from xmb-ams-335.cisco.com ([144.254.231.80]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 3 Jun 2009 11:58:08 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 3 Jun 2009 11:58:06 +0200
Message-ID: <DD0238A0AAE9B74A8F70A91BDF497C2F056AC865@xmb-ams-335.emea.cisco.com>
In-Reply-To: <D24156B9-B8A6-4552-9642-B366DE07B7EB@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Review of draft-ietf-tsvwg-rsvp-security-groupkeying-04
Thread-Index: AcnN3CfvlR6zcqHgTTuR+RWcj1pUSQWVMOqg
References: <D24156B9-B8A6-4552-9642-B366DE07B7EB@cisco.com>
From: "Michael Behringer (mbehring)" <mbehring@cisco.com>
To: "Brian Weis (bew)" <bew@cisco.com>, "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
X-OriginalArrivalTime: 03 Jun 2009 09:58:08.0735 (UTC) FILETIME=[CC355EF0:01C9E431]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2164; t=1244023088; x=1244887088; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mbehring@cisco.com; z=From:=20=22Michael=20Behringer=20(mbehring)=22=20<mbehring @cisco.com> |Subject:=20RE=3A=20Review=20of=20draft-ietf-tsvwg-rsvp-sec urity-groupkeying-04 |Sender:=20; bh=euUGpP2mYNmQSYN3Pb7SLbOJ08AQMJ/MBAmehKSsm/o=; b=XFm93HzBCaxizB495wNkMfV7dxsZBR6C8+cnOo3WaWWL20blao5nHHR/cb 9XORDdhQuMMbJL9YpxlCdf2EyARgGo3MNrHwpVEZGr0rVUzsuI0bbOodzVrC kSaBAispDD;
Authentication-Results: ams-dkim-1; header.From=mbehring@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; ); 
Cc: tsvwg IETF list <tsvwg@ietf.org>
Subject: Re: [Tsvwg] Review of draft-ietf-tsvwg-rsvp-security-groupkeying-04
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jun 2009 09:58:10 -0000

Hi Brian,=20

Thanks for your review - this is very useful.=20

Regarding your comment, I agree that the statement is confusing. And to
be honest, the point wasn't so much about distinguishing between
explicit or implicit, the point was that in a group keying scenario you
trust all members of the group. We'll simplify the sentence to "Note
that in any group keying scheme like GDOI a node trusts all the other
members of the group."

I thought about adding more on implicit vs explicit, but came to the
conclusion that this makes this section a lot more confusing, while not
really adding much value over the beginning of that paragraph.=20

Does this address your concern? Is this appropriate?=20

Michael

> -----Original Message-----
> From: Brian Weis (bew)
> Sent: 06 May 2009 1:50
> To: Francois Le Faucheur (flefauch); Michael Behringer (mbehring)
> Cc: tsvwg IETF list
> Subject: Review of draft-ietf-tsvwg-rsvp-security-groupkeying-04
>=20
> Hi Francois & Michael,
>=20
> I have reviewed this document and have only one comment. Section 2
> discussed "implicit" and "explicit" trust. Generally, I agree with it
> except for the following sentence:
>=20
> "Note that in any group keying scheme like GDOI a node trusts
> explicitly as well as implicitly all the other members of the group."
>=20
> I don't see where the fact that multiple parties hold the same key to
> make the trust explicit. For example, when manual keying is used the
> node doesn't really have any idea how many other nodes share that key
> (i.e., whether it is a pairwise or group key). It simply sends and
> receives RSVP messages and explicitly trusts the next RSVP node to
> handle the message to do the right thing, regardless of whether its
> identity is known or unknown. Non-neighbors are always trusted
> implicitly whether or not they happen to share a key.
>=20
> Were you thinking of some other attribute of group keying that makes
> the trust explicit?
>=20
> Thanks,
> Brian
>=20
> --
> Brian Weis
> Router/Switch Security Group, ARTG, Cisco Systems
> Telephone: +1 408 526 4796
> Email: bew@cisco.com
>=20
>=20


From mbehring@cisco.com  Wed Jun  3 07:01:48 2009
Return-Path: <mbehring@cisco.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5209E3A6F51 for <tsvwg@core3.amsl.com>; Wed,  3 Jun 2009 07:01:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zlB0qVZtGPWI for <tsvwg@core3.amsl.com>; Wed,  3 Jun 2009 07:01:47 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id C32AA3A6F38 for <tsvwg@ietf.org>; Wed,  3 Jun 2009 07:01:46 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.41,298,1241395200"; d="scan'208";a="41951840"
Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 03 Jun 2009 14:01:47 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n53E1lsM001028;  Wed, 3 Jun 2009 16:01:47 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com [144.254.231.87]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n53E1lV6012798; Wed, 3 Jun 2009 14:01:47 GMT
Received: from xmb-ams-335.cisco.com ([144.254.231.80]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 3 Jun 2009 16:01:47 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 3 Jun 2009 16:01:45 +0200
Message-ID: <DD0238A0AAE9B74A8F70A91BDF497C2F056AC9F3@xmb-ams-335.emea.cisco.com>
In-Reply-To: <B111EEAA42CD0F4D85A5E486368D155A024D109B@0015-its-exmb11.us.saic.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Tsvwg] Review of draft-ietf-tsvwg-rsvp-security-groupkeying-04
Thread-Index: AcnN3C7N8rc/XN/qQkSJrm3ALaOEKwVqtm2gACsWUJA=
References: <D24156B9-B8A6-4552-9642-B366DE07B7EB@cisco.com> <B111EEAA42CD0F4D85A5E486368D155A024D109B@0015-its-exmb11.us.saic.com>
From: "Michael Behringer (mbehring)" <mbehring@cisco.com>
To: "Carlberg, Kenneth G." <KENNETH.G.CARLBERG@saic.com>, "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
X-OriginalArrivalTime: 03 Jun 2009 14:01:47.0242 (UTC) FILETIME=[D58484A0:01C9E453]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3282; t=1244037707; x=1244901707; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mbehring@cisco.com; z=From:=20=22Michael=20Behringer=20(mbehring)=22=20<mbehring @cisco.com> |Subject:=20RE=3A=20[Tsvwg]=20Review=20of=20draft-ietf-tsvw g-rsvp-security-groupkeying-04 |Sender:=20; bh=2N+N/Ik27w3FUrl87FoJdsdZmUqBWGQEP9gqienYsnE=; b=J/MTbj7h3v2VRmeiWaPZ8kQhMdjnmmWfzADgA4O1GDgsKusrKvpkR06xcs Uo36czOC/9giCuF2ep2o7Gqqb5Ckdiu69+/NRd0Se+sxhonh9z5WtH6QvzBd 0+8sXc9tbH;
Authentication-Results: ams-dkim-1; header.From=mbehring@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; ); 
Cc: tsvwg IETF list <tsvwg@ietf.org>
Subject: Re: [Tsvwg] Review of draft-ietf-tsvwg-rsvp-security-groupkeying-04
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jun 2009 14:01:48 -0000

Ken,=20

Thanks for the feedback, this is very helpful! Inline...

> -----Original Message-----
> From: Carlberg, Kenneth G. [mailto:KENNETH.G.CARLBERG@saic.com]
> Sent: 02 June 2009 16:15
> To: Francois Le Faucheur (flefauch); Michael Behringer (mbehring)
> Cc: tsvwg IETF list
> Subject: RE: [Tsvwg] Review of draft-ietf-tsvwg-rsvp-security-
> groupkeying-04
>=20
> Francois & Michael,
>=20
> Here is another review of the draft.  Its mostly comprised of nits and
> requests for additional clarification.
>=20
> -ken
>=20
>=20
> 1) page 4,  "Implicitly each node trusts each other node with which
>    it has a trust relationship established via the mechanisms here to
>    adhere to the protocol specifications laid out by the various
>    standards."
>=20
> The sentence is a bit long and confusing.  You need to break up the
> sentence and clarify the content of the word "here".  Also,
> s/other/other's

Agreed. We simplified that sentence to:=20

Implicitly each node trusts each other node in the RSVP domain to adhere
to the protocol specifications laid out by the various standards.=20

> 2) page 5, 3'rd para.  s/R2 and will ignore/R2 will ignore

Done. Good catch!

> 3) page 5, 5'th para.
>    "With neighbor based keys, an RSVP key is bound to an interface
plus
> a
>    neighbor on that interface.  It allows the distinction of different
>    trust groups on a single subnet.  (Assuming that layer-2 security
is
>    correctly implemented to prevent layer-2 attacks.)"
>=20
> Does the above text concerning neighbor based keys allow for different
> trust groups per interface?  If so, this should be stated to the
> reader.

Ken - I don't understand this one. Isn't the sentence "It allows the
distinction of different trust groups on a single subnet." addressing
exactly your point?=20

> 4) Page 6, 5'th para.  s/domains however/domains. However

Reworded.=20
=20
> 5) page 14, 2'nd para.
>    "In
>    particular, such keying can be used for RSVP authentication (e.g.,
>    using RSVP authentication or IPsec AH) and/ or for RSVP encryption
>    (e.g., using IPsec ESP in tunnel mode)."
>=20
> The sentence is a bit unclear with respect to using the term RSVP
> authentication as an example of keying "used for RSVP authentication".
> You'll either need to clarify the text, or just rely on IPsec AH as a
> single example.

Re-worded: "such keying can be used for RSVP authentication (e.g., using
the RSVP INTEGRITY object or IPsec AH) and/ or for RSVP encryption
(e.g., using IPsec ESP in tunnel mode)."=20
=20
> 6) Page 15, late sentence of 4'th para.
>    "Therefore the impact of subverted nodes on the path is comparable,
>    independently whether per-interface, per-neighbor or group keys are
>    used."
>=20
> The reader would probably ask, comparable to what?  It would be
helpful
> if you could complete the object of the sentence.

Re-worded: "Therefore the impact of subverted nodes on the path is
comparable for all keying schemes discussed here (per-interface,
per-neighbor, group keys)."

Thanks again for your thorough review, and all your comments. Please let
us know if our corrections are still not clear or have introduced new
questions.=20

Michael


From KENNETH.G.CARLBERG@saic.com  Wed Jun  3 07:22:26 2009
Return-Path: <KENNETH.G.CARLBERG@saic.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 919113A6ECE for <tsvwg@core3.amsl.com>; Wed,  3 Jun 2009 07:22:26 -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 HbUEMpX1lu8P for <tsvwg@core3.amsl.com>; Wed,  3 Jun 2009 07:22:25 -0700 (PDT)
Received: from mclmx.mail.saic.com (mclmx.mail.saic.com [149.8.64.10]) by core3.amsl.com (Postfix) with ESMTP id A5EEE3A688A for <tsvwg@ietf.org>; Wed,  3 Jun 2009 07:22:25 -0700 (PDT)
Received: from 0015-ITS-SMS01 ([149.8.64.21] [149.8.64.21]) by mclmx.mail.saic.com with ESMTP id BT-MMP-5845249; Wed, 3 Jun 2009 10:22:00 -0400
X-AuditID: 9508402e-a8757ba000000d82-37-4a268708b311
Received: from 0015-its-exbh03.us.saic.com (unknown [149.8.64.21]) by 0015-ITS-SMS01 (Symantec Mail Security) with ESMTP id C6069C4811A; Wed,  3 Jun 2009 10:22:00 -0400 (EDT)
Received: from 0015-its-exmb11.us.saic.com ([10.43.229.22]) by 0015-its-exbh03.us.saic.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 3 Jun 2009 10:22:00 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 3 Jun 2009 10:21:59 -0400
Message-Id: <B111EEAA42CD0F4D85A5E486368D155A024D1982@0015-its-exmb11.us.saic.com>
In-Reply-To: <DD0238A0AAE9B74A8F70A91BDF497C2F056AC9F3@xmb-ams-335.emea.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Tsvwg] Review of draft-ietf-tsvwg-rsvp-security-groupkeying-04
Thread-Index: AcnN3C7N8rc/XN/qQkSJrm3ALaOEKwVqtm2gACsWUJAACG8f0A==
References: <D24156B9-B8A6-4552-9642-B366DE07B7EB@cisco.com><B111EEAA42CD0F4D85A5E486368D155A024D109B@0015-its-exmb11.us.saic.com> <DD0238A0AAE9B74A8F70A91BDF497C2F056AC9F3@xmb-ams-335.emea.cisco.com>
From: "Carlberg, Kenneth G." <KENNETH.G.CARLBERG@saic.com>
To: "Michael Behringer (mbehring)" <mbehring@cisco.com>, "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
X-OriginalArrivalTime: 03 Jun 2009 14:22:00.0998 (UTC) FILETIME=[A8F8FC60:01C9E456]
X-Brightmail-Tracker: AAAAAA==
Cc: tsvwg IETF list <tsvwg@ietf.org>
Subject: Re: [Tsvwg] Review of draft-ietf-tsvwg-rsvp-security-groupkeying-04
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jun 2009 14:22:26 -0000

Michael,=20

>  > 3) page 5, 5'th para.
>  >    "With neighbor based keys, an RSVP key is bound to an interface
>  plus
>  > a
>  >    neighbor on that interface.  It allows the distinction=20
>  of different
>  >    trust groups on a single subnet.  (Assuming that=20
>  layer-2 security
>  is
>  >    correctly implemented to prevent layer-2 attacks.)"
>  >=20
>  > Does the above text concerning neighbor based keys allow=20
>  for different=20
>  > trust groups per interface?  If so, this should be stated to the=20
>  > reader.
> =20
>  Ken - I don't understand this one. Isn't the sentence "It=20
>  allows the distinction of different trust groups on a single=20
>  subnet." addressing exactly your point?=20

I may be too picky, but in only saying "a single subnet", the reader
could have the impression that in (for example) a broadcast subnet, the
text may be refering to a ships-in-the-night scenario where I have some
nodes operating in one trust group and other nodes in another trust
group.  By extending your text to explicitly say that neighbor based
keys allows for different trust groups per interface in a subnet, there
is no ambiguity.

Its not a major issue so feel free to disregard the suggestion.

-ken
=20

From mbehring@cisco.com  Wed Jun  3 09:54:59 2009
Return-Path: <mbehring@cisco.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4643F28C189 for <tsvwg@core3.amsl.com>; Wed,  3 Jun 2009 09:54:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gb4RJNPse0gT for <tsvwg@core3.amsl.com>; Wed,  3 Jun 2009 09:54:58 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id EA6DD3A6945 for <tsvwg@ietf.org>; Wed,  3 Jun 2009 09:54:57 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.41,299,1241395200"; d="scan'208";a="41967871"
Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 03 Jun 2009 16:54:57 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n53Gsv6F021903;  Wed, 3 Jun 2009 18:54:57 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com [144.254.231.87]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n53Gsv6Y009604; Wed, 3 Jun 2009 16:54:57 GMT
Received: from xmb-ams-335.cisco.com ([144.254.231.80]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 3 Jun 2009 18:54:57 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 3 Jun 2009 18:51:52 +0200
Message-ID: <DD0238A0AAE9B74A8F70A91BDF497C2F056ACB27@xmb-ams-335.emea.cisco.com>
In-Reply-To: <B111EEAA42CD0F4D85A5E486368D155A024D1982@0015-its-exmb11.us.saic.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Tsvwg] Review of draft-ietf-tsvwg-rsvp-security-groupkeying-04
Thread-Index: AcnN3C7N8rc/XN/qQkSJrm3ALaOEKwVqtm2gACsWUJAACG8f0AAFih7A
References: <D24156B9-B8A6-4552-9642-B366DE07B7EB@cisco.com><B111EEAA42CD0F4D85A5E486368D155A024D109B@0015-its-exmb11.us.saic.com> <DD0238A0AAE9B74A8F70A91BDF497C2F056AC9F3@xmb-ams-335.emea.cisco.com> <B111EEAA42CD0F4D85A5E486368D155A024D1982@0015-its-exmb11.us.saic.com>
From: "Michael Behringer (mbehring)" <mbehring@cisco.com>
To: "Carlberg, Kenneth G." <KENNETH.G.CARLBERG@saic.com>, "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
X-OriginalArrivalTime: 03 Jun 2009 16:54:57.0774 (UTC) FILETIME=[06C1E0E0:01C9E46C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1681; t=1244048097; x=1244912097; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mbehring@cisco.com; z=From:=20=22Michael=20Behringer=20(mbehring)=22=20<mbehring @cisco.com> |Subject:=20RE=3A=20[Tsvwg]=20Review=20of=20draft-ietf-tsvw g-rsvp-security-groupkeying-04 |Sender:=20; bh=zrY/02q+BU/Xn5LcS6pOEDzXccaVaaYEINn9nCdoZhs=; b=kCGQx+wV6Az/Dn9PEBnlOR2LmBTRYIg2Hrnp5CThSj9CHRtmqtP1JK2ioL QDxBVaYVKEyM0Ngu4vI+HCXfBcFhvFBNe3AQdQumfSx4an8fq8EBctbKR0Ls MKbNj+5B0N;
Authentication-Results: ams-dkim-1; header.From=mbehring@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; ); 
Cc: tsvwg IETF list <tsvwg@ietf.org>
Subject: Re: [Tsvwg] Review of draft-ietf-tsvwg-rsvp-security-groupkeying-04
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jun 2009 16:54:59 -0000

> -----Original Message-----
> From: Carlberg, Kenneth G. [mailto:KENNETH.G.CARLBERG@saic.com]
> Sent: 03 June 2009 16:22
> To: Michael Behringer (mbehring); Francois Le Faucheur (flefauch)
> Cc: tsvwg IETF list
> Subject: RE: [Tsvwg] Review of draft-ietf-tsvwg-rsvp-security-
> groupkeying-04
>=20
> Michael,
>=20
> >  > 3) page 5, 5'th para.
> >  >    "With neighbor based keys, an RSVP key is bound to an
interface
> >  plus
> >  > a
> >  >    neighbor on that interface.  It allows the distinction
> >  of different
> >  >    trust groups on a single subnet.  (Assuming that
> >  layer-2 security
> >  is
> >  >    correctly implemented to prevent layer-2 attacks.)"
> >  >
> >  > Does the above text concerning neighbor based keys allow
> >  for different
> >  > trust groups per interface?  If so, this should be stated to the
> >  > reader.
> >
> >  Ken - I don't understand this one. Isn't the sentence "It
> >  allows the distinction of different trust groups on a single
> >  subnet." addressing exactly your point?
>=20
> I may be too picky, but in only saying "a single subnet", the reader
> could have the impression that in (for example) a broadcast subnet,
the
> text may be refering to a ships-in-the-night scenario where I have
some
> nodes operating in one trust group and other nodes in another trust
> group.  By extending your text to explicitly say that neighbor based
> keys allows for different trust groups per interface in a subnet,
there
> is no ambiguity.

Got it! Will incorporate this point as well, thanks!

Michael

> Its not a major issue so feel free to disregard the suggestion.
>=20
> -ken
>=20

From mbehring@cisco.com  Thu Jun  4 03:35:01 2009
Return-Path: <mbehring@cisco.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AC0083A6809 for <tsvwg@core3.amsl.com>; Thu,  4 Jun 2009 03:35:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tnHEE5QExecw for <tsvwg@core3.amsl.com>; Thu,  4 Jun 2009 03:34:59 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 6E1F83A6959 for <tsvwg@ietf.org>; Thu,  4 Jun 2009 03:34:58 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.41,305,1241395200"; d="scan'208";a="42027883"
Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 04 Jun 2009 10:34:47 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n54AYlFe013657;  Thu, 4 Jun 2009 12:34:47 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com [144.254.231.87]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n54AYllP008565; Thu, 4 Jun 2009 10:34:47 GMT
Received: from xmb-ams-335.cisco.com ([144.254.231.80]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 4 Jun 2009 12:34:47 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 4 Jun 2009 12:34:45 +0200
Message-ID: <DD0238A0AAE9B74A8F70A91BDF497C2F056ACDF7@xmb-ams-335.emea.cisco.com>
In-Reply-To: <24A68080-B12A-41F9-8516-81B33E273A41@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Tsvwg] Review of draft-ietf-tsvwg-rsvp-security-groupkeying-04
Thread-Index: AcnkJfznqq/7G6iBQB+KzGtw39HEvwA2amrw
References: <D24156B9-B8A6-4552-9642-B366DE07B7EB@cisco.com> <B111EEAA42CD0F4D85A5E486368D155A024D109B@0015-its-exmb11.us.saic.com> <6B9C4B97B82F924485E26968EB05A6EE070D9B08@xmb-sjc-224.amer.cisco.com> <24A68080-B12A-41F9-8516-81B33E273A41@cisco.com>
From: "Michael Behringer (mbehring)" <mbehring@cisco.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>, "James Polk (jmpolk)" <jmpolk@cisco.com>, "Gorry Fairhurst" <gorry@erg.abdn.ac.uk>, "Lars Eggert" <lars.eggert@nokia.com>
X-OriginalArrivalTime: 04 Jun 2009 10:34:47.0761 (UTC) FILETIME=[1557DC10:01C9E500]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4177; t=1244111687; x=1244975687; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mbehring@cisco.com; z=From:=20=22Michael=20Behringer=20(mbehring)=22=20<mbehring @cisco.com> |Subject:=20RE=3A=20[Tsvwg]=20Review=20of=20draft-ietf-tsvw g-rsvp-security-groupkeying-04 |Sender:=20; bh=9m6kK9SzY6D/ELU2MriBHxCorZ4SxNIrObraiweESYo=; b=STubsXXsY10BabgjsPxyKJgsrtyOF9n0MkL7AnX72OsKNpwT2KXgtTJiLH +MqXav+py5bGha8o9T5TuBCeVZ4Lqo6AGvoJ+nlINitiwRSWzOOxAynNWdmV 62nGmROSg1;
Authentication-Results: ams-dkim-2; header.From=mbehring@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; ); 
Cc: tsvwg IETF list <tsvwg@ietf.org>
Subject: Re: [Tsvwg] Review of draft-ietf-tsvwg-rsvp-security-groupkeying-04
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jun 2009 10:35:01 -0000

We have just uploaded version -05, incorporating the latest comments
received:

   o  Clarified in section 6.3 that IPsec AH also secures the immutable
      fields of the outer header (comment from Bob Briscoe)
   o  Simplified in section 2 the comment that trust in group keying
      extends to all members of the group (deleted the words on
      "explicit and implicit"). (comment from Brian Weis)
   o  A number of corrections, re-wordings and clarifications in
      response to Kenneth Carlberg's email from 2 June 2009

This would be the right version of the document for LC now, if
applicable.=20
http://tools.ietf.org/html/draft-ietf-tsvwg-rsvp-security-groupkeying

Thanks,=20
Michael


> -----Original Message-----
> From: Francois Le Faucheur (flefauch)
> Sent: 03 June 2009 10:34
> To: James Polk (jmpolk); Gorry Fairhurst; Lars Eggert
> Cc: Francois Le Faucheur (flefauch); Michael Behringer (mbehring);
> tsvwg IETF list
> Subject: Re: [Tsvwg] Review of draft-ietf-tsvwg-rsvp-security-
> groupkeying-04
>=20
> Hi James, Gorry, Lars,
>=20
> At last IETF, Lars conditioned Last Calling of rsvp-security-
> groupkeying on getting explicit commitments from subject experts that
> they will indeed review the doc.
> Considering that, since then, Brian Weis, Bob Briscoe and Ken Carlberg
> have posted their full review comments and Sheela just committed to
> also do a review, would it be appropriate to move to Last Call now?
>=20
> Thanks
>=20
> Francois
>=20
> On 3 Jun 2009, at 06:54, Sheela Rowles (sheela) wrote:
>=20
> > Francois & Michael,
> >
> > I'm also planning to review the draft.  I hope to complete the
review
> > within a week or two.
> >
> > Sheela
> >
> > -----Original Message-----
> > From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On
> Behalf
> > Of Carlberg, Kenneth G.
> > Sent: Tuesday, June 02, 2009 7:15 AM
> > To: Francois Le Faucheur (flefauch); Michael Behringer (mbehring)
> > Cc: tsvwg IETF list
> > Subject: Re: [Tsvwg] Review of
> > draft-ietf-tsvwg-rsvp-security-groupkeying-04
> >
> > Francois & Michael,
> >
> > Here is another review of the draft.  Its mostly comprised of nits
> and
> > requests for additional clarification.
> >
> > -ken
> >
> >
> > 1) page 4,  "Implicitly each node trusts each other node with which
> >   it has a trust relationship established via the mechanisms here to
> >   adhere to the protocol specifications laid out by the various
> >   standards."
> >
> > The sentence is a bit long and confusing.  You need to break up the
> > sentence and clarify the content of the word "here".  Also,
> > s/other/other's
> >
> >
> > 2) page 5, 3'rd para.  s/R2 and will ignore/R2 will ignore
> >
> > 3) page 5, 5'th para.
> >   "With neighbor based keys, an RSVP key is bound to an interface
> plus
> > a
> >   neighbor on that interface.  It allows the distinction of
different
> >   trust groups on a single subnet.  (Assuming that layer-2 security
> is
> >   correctly implemented to prevent layer-2 attacks.)"
> >
> > Does the above text concerning neighbor based keys allow for
> different
> > trust groups per interface?  If so, this should be stated to the
> > reader.
> >
> > 4) Page 6, 5'th para.  s/domains however/domains. However
> >
> > 5) page 14, 2'nd para.
> >   "In
> >   particular, such keying can be used for RSVP authentication (e.g.,
> >   using RSVP authentication or IPsec AH) and/ or for RSVP encryption
> >   (e.g., using IPsec ESP in tunnel mode)."
> >
> > The sentence is a bit unclear with respect to using the term RSVP
> > authentication as an example of keying "used for RSVP
> authentication".
> > You'll either need to clarify the text, or just rely on IPsec AH as
a
> > single example.
> >
> > 6) Page 15, late sentence of 4'th para.
> >   "Therefore the impact of subverted nodes on the path is
comparable,
> >   independently whether per-interface, per-neighbor or group keys
are
> >   used."
> >
> > The reader would probably ask, comparable to what?  It would be
> > helpful
> > if you could complete the object of the sentence.
> >


From root@core3.amsl.com  Thu Jun  4 03:45:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: tsvwg@ietf.org
Delivered-To: tsvwg@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 40DEB3A6ADA; Thu,  4 Jun 2009 03:45:00 -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: <20090604104501.40DEB3A6ADA@core3.amsl.com>
Date: Thu,  4 Jun 2009 03:45:01 -0700 (PDT)
Cc: tsvwg@ietf.org
Subject: [Tsvwg] I-D Action:draft-ietf-tsvwg-rsvp-security-groupkeying-05.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jun 2009 10:45:01 -0000

--NextPart

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


	Title           : Applicability of Keying Methods for RSVP Security
	Author(s)       : M. Behringer, F. Le Faucheur
	Filename        : draft-ietf-tsvwg-rsvp-security-groupkeying-05.txt
	Pages           : 19
	Date            : 2009-06-04

The Resource reSerVation Protocol (RSVP) allows hop-by-hop
authentication of RSVP neighbors.  This requires messages to be
cryptographically signed using a shared secret between participating
nodes.  This document compares group keying for RSVP with per
neighbor or per interface keying, and discusses the associated key
provisioning methods as well as applicability and limitations of
these approaches.  The present document also discusses applicability
of group keying to RSVP encryption.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rsvp-security-groupkeying-05.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-tsvwg-rsvp-security-groupkeying-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-06-04033109.I-D@ietf.org>


--NextPart--

From bew@cisco.com  Thu Jun  4 23:09:26 2009
Return-Path: <bew@cisco.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2C3D93A6872 for <tsvwg@core3.amsl.com>; Thu,  4 Jun 2009 23:09:26 -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 sdU1mOwwVqdx for <tsvwg@core3.amsl.com>; Thu,  4 Jun 2009 23:09:24 -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 DB8A03A682E for <tsvwg@ietf.org>; Thu,  4 Jun 2009 23:09:24 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.41,309,1241395200"; d="scan'208";a="195230509"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-1.cisco.com with ESMTP; 05 Jun 2009 06:09:27 +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 n5569Rrh004483 for <tsvwg@ietf.org>; Thu, 4 Jun 2009 23:09:27 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n5569R9s013605 for <tsvwg@ietf.org>; Fri, 5 Jun 2009 06:09:27 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 4 Jun 2009 23:09:27 -0700
Received: from stealth-10-32-244-211.cisco.com ([10.32.244.211]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 4 Jun 2009 23:09:26 -0700
Message-Id: <BFE9B73C-56A7-4AC6-BD78-65D1CB3216EE@cisco.com>
From: Brian Weis <bew@cisco.com>
To: Michael Behringer (mbehring) <mbehring@cisco.com>
In-Reply-To: <DD0238A0AAE9B74A8F70A91BDF497C2F056AC865@xmb-ams-335.emea.cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Thu, 4 Jun 2009 23:09:25 -0700
References: <D24156B9-B8A6-4552-9642-B366DE07B7EB@cisco.com> <DD0238A0AAE9B74A8F70A91BDF497C2F056AC865@xmb-ams-335.emea.cisco.com>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 05 Jun 2009 06:09:27.0287 (UTC) FILETIME=[2E6A1070:01C9E5A4]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2555; t=1244182167; x=1245046167; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=bew@cisco.com; z=From:=20Brian=20Weis=20<bew@cisco.com> |Subject:=20Re=3A=20Review=20of=20draft-ietf-tsvwg-rsvp-sec urity-groupkeying-04 |Sender:=20; bh=vSLqrZQZvj2t4Bt3g/wC0R6JvlPK/+G1QVR1X6p1B3s=; b=SqL8TCCEQVkGk7DJL+VlJKJssSd3xXhmN1jv0VzJu2K8nq9FiQkDK6MWsk 1CYXACG75cbKxFkfi9FAKm1BFsINPiQJdqOtS6hFUMs9yoNrjLxvn3F8Egys PLROiQ2yen;
Authentication-Results: sj-dkim-4; header.From=bew@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); 
Cc: tsvwg IETF list <tsvwg@ietf.org>
Subject: Re: [Tsvwg] Review of draft-ietf-tsvwg-rsvp-security-groupkeying-04
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Jun 2009 06:09:26 -0000

Hi Michael,

On Jun 3, 2009, at 2:58 AM, Michael Behringer (mbehring) wrote:

> Hi Brian,
>
> Thanks for your review - this is very useful.
>
> Regarding your comment, I agree that the statement is confusing. And  
> to
> be honest, the point wasn't so much about distinguishing between
> explicit or implicit, the point was that in a group keying scenario  
> you
> trust all members of the group. We'll simplify the sentence to "Note
> that in any group keying scheme like GDOI a node trusts all the other
> members of the group."
>
> I thought about adding more on implicit vs explicit, but came to the
> conclusion that this makes this section a lot more confusing, while  
> not
> really adding much value over the beginning of that paragraph.
>
> Does this address your concern? Is this appropriate?

Thanks for the clarification. The proposed change works for me, and I  
see you've already included it in -05.

Thanks,
Brian

>
>
> Michael
>
>> -----Original Message-----
>> From: Brian Weis (bew)
>> Sent: 06 May 2009 1:50
>> To: Francois Le Faucheur (flefauch); Michael Behringer (mbehring)
>> Cc: tsvwg IETF list
>> Subject: Review of draft-ietf-tsvwg-rsvp-security-groupkeying-04
>>
>> Hi Francois & Michael,
>>
>> I have reviewed this document and have only one comment. Section 2
>> discussed "implicit" and "explicit" trust. Generally, I agree with it
>> except for the following sentence:
>>
>> "Note that in any group keying scheme like GDOI a node trusts
>> explicitly as well as implicitly all the other members of the group."
>>
>> I don't see where the fact that multiple parties hold the same key to
>> make the trust explicit. For example, when manual keying is used the
>> node doesn't really have any idea how many other nodes share that key
>> (i.e., whether it is a pairwise or group key). It simply sends and
>> receives RSVP messages and explicitly trusts the next RSVP node to
>> handle the message to do the right thing, regardless of whether its
>> identity is known or unknown. Non-neighbors are always trusted
>> implicitly whether or not they happen to share a key.
>>
>> Were you thinking of some other attribute of group keying that makes
>> the trust explicit?
>>
>> Thanks,
>> Brian
>>
>> --
>> Brian Weis
>> Router/Switch Security Group, ARTG, Cisco Systems
>> Telephone: +1 408 526 4796
>> Email: bew@cisco.com
>>
>>
>


-- 
Brian Weis
Router/Switch Security Group, ARTG, Cisco Systems
Telephone: +1 408 526 4796
Email: bew@cisco.com




From sa2086@columbia.edu  Sun Jun  7 13:29:03 2009
Return-Path: <sa2086@columbia.edu>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EAF603A6D99 for <tsvwg@core3.amsl.com>; Sun,  7 Jun 2009 13:29:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.981
X-Spam-Level: 
X-Spam-Status: No, score=-5.981 tagged_above=-999 required=5 tests=[AWL=0.618,  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 J18A5S17-nap for <tsvwg@core3.amsl.com>; Sun,  7 Jun 2009 13:29:03 -0700 (PDT)
Received: from jalapeno.cc.columbia.edu (jalapeno.cc.columbia.edu [128.59.29.5]) by core3.amsl.com (Postfix) with ESMTP id 0CE163A6D93 for <tsvwg@ietf.org>; Sun,  7 Jun 2009 13:29:02 -0700 (PDT)
Received: from banana.cc.columbia.edu (banana.cc.columbia.edu [128.59.29.54]) by jalapeno.cc.columbia.edu (8.14.3/8.14.3) with ESMTP id n57KT6CL011035 for <tsvwg@ietf.org>; Sun, 7 Jun 2009 16:29:06 -0400 (EDT)
Received: from banana.cc.columbia.edu (localhost [127.0.0.1]) by banana.cc.columbia.edu (8.14.3/8.14.3) with ESMTP id n57KT6d2003377 for <tsvwg@ietf.org>; Sun, 7 Jun 2009 16:29:06 -0400 (EDT)
Received: from localhost (sa2086@localhost) by banana.cc.columbia.edu (8.14.3/8.14.3/Submit) with ESMTP id n57KT6d9003374 for <tsvwg@ietf.org>; Sun, 7 Jun 2009 16:29:06 -0400 (EDT)
X-Authentication-Warning: banana.cc.columbia.edu: sa2086 owned process doing -bs
Date: Sun, 7 Jun 2009 16:29:06 -0400 (EDT)
From: Salman  Abdul Baset <sa2086@columbia.edu>
Sender: sa2086@columbia.edu
To: tsvwg@ietf.org
Message-ID: <alpine.SOC.1.00.0906071625340.2993@banana.cc.columbia.edu>
User-Agent: Alpine 1.00 (SOC 882 2007-12-20)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.65 on 128.59.29.5
Subject: [tsvwg] TCP-over-UDP draft-01
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Jun 2009 20:29:04 -0000

We have submitted -01 version of TCP-over-UDP draft that incorporates the 
comments from list discussion.

http://tools.ietf.org/html/draft-baset-tsvwg-tcp-over-udp-01

Feedback is appreciated.

Thanks
Salman

From mallman@icir.org  Mon Jun 15 05:38:08 2009
Return-Path: <mallman@icir.org>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5AF893A6C86 for <tsvwg@core3.amsl.com>; Mon, 15 Jun 2009 05:38:08 -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 FPkBYtGDokDE for <tsvwg@core3.amsl.com>; Mon, 15 Jun 2009 05:38:07 -0700 (PDT)
Received: from pork.ICSI.Berkeley.EDU (pork.ICSI.Berkeley.EDU [192.150.186.19]) by core3.amsl.com (Postfix) with ESMTP id AE84B3A6A28 for <tsvwg@ietf.org>; Mon, 15 Jun 2009 05:38:07 -0700 (PDT)
Received: from guns.icir.org (adsl-69-222-35-58.dsl.bcvloh.ameritech.net [69.222.35.58]) by pork.ICSI.Berkeley.EDU (8.12.11.20060308/8.12.11) with ESMTP id n5FCbNo9020061; Mon, 15 Jun 2009 05:37:23 -0700
Received: from lawyers.icir.org (adsl-69-222-35-58.dsl.bcvloh.ameritech.net [69.222.35.58]) by guns.icir.org (Postfix) with ESMTP id ED95D3AC5C4D; Mon, 15 Jun 2009 08:37:17 -0400 (EDT)
Received: from lawyers.icir.org (localhost [127.0.0.1]) by lawyers.icir.org (Postfix) with ESMTP id B09372E00C3; Mon, 15 Jun 2009 08:37:17 -0400 (EDT)
To: Fernando Gont <fernando@gont.com.ar>
From: Mark Allman <mallman@icir.org>
In-Reply-To: <4A1DB1C3.3040205@gont.com.ar> 
Organization: International Computer Science Institute (ICSI)
Song-of-the-Day: Love Stinks
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="--------ma16509-1"; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Mon, 15 Jun 2009 08:37:17 -0400
Sender: mallman@icir.org
Message-Id: <20090615123717.B09372E00C3@lawyers.icir.org>
Cc: =?ISO-8859-1?Q?Alfred_H=F6nes?= <ah@tr-sys.de>, "James M. Polk" <jmpolk@cisco.com>, tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] [Tsvwg] lookup time (was Re: WGLC for Port Randomization starts now (April 1st))
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: mallman@icir.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jun 2009 12:38:08 -0000

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


> If you retry random port, chances are that you may retry the same port
> more than once, instead of trying a different port that might be
> available. The larger the number of ports in uses, the more likely
> this would be. (see the pseudo-code).

Sure.  Of course.  But, we can put this in concrete terms it would
seem.  I.e., if we use something like alg. 3 then for a given connection
ID we will not test for some port X again before exhausting all the
non-X ports.  In something like alg. 2 you can in fact check X more than
once with a probability defined by the port usage at the given time and
also not test for all possible ports.

allman




----------ma16509-1
Content-Type: application/pgp-signature

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

iEYEARECAAYFAko2QH0ACgkQWyrrWs4yIs7g9QCdE5Mtj/gmh+NAzsURmwFNZAQ1
zdkAnjx5pE33lp2a5bW1qRRbJ8TfytYE
=kJYI
-----END PGP SIGNATURE-----
----------ma16509-1--

From mbehring@cisco.com  Mon Jun 15 06:27:16 2009
Return-Path: <mbehring@cisco.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 472623A68A4 for <tsvwg@core3.amsl.com>; Mon, 15 Jun 2009 06:27:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.164
X-Spam-Level: 
X-Spam-Status: No, score=-10.164 tagged_above=-999 required=5 tests=[AWL=-0.435, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_MLH_Stock1=0.87]
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 HyKEiFu6C2bq for <tsvwg@core3.amsl.com>; Mon, 15 Jun 2009 06:27:12 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 356D13A63C9 for <tsvwg@ietf.org>; Mon, 15 Jun 2009 06:27:12 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,222,1243814400"; d="scan'208";a="42822582"
Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 15 Jun 2009 13:27:21 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n5FDRL1P013481;  Mon, 15 Jun 2009 15:27:21 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com [144.254.231.71]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n5FDRLYP020659; Mon, 15 Jun 2009 13:27:21 GMT
Received: from xmb-ams-335.cisco.com ([144.254.231.80]) by xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 15 Jun 2009 15:27:21 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 15 Jun 2009 15:27:20 +0200
Message-ID: <DD0238A0AAE9B74A8F70A91BDF497C2F057C1364@xmb-ams-335.emea.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Meeting in Stockholm?
Thread-Index: AcntvQJM0ohwkn3kT/yGa98iWPtmMQ==
From: "Michael Behringer (mbehring)" <mbehring@cisco.com>
To: "James Polk (jmpolk)" <jmpolk@cisco.com>, "Gorry Fairhurst" <gorry@erg.abdn.ac.uk>
X-OriginalArrivalTime: 15 Jun 2009 13:27:21.0334 (UTC) FILETIME=[0318F960:01C9EDBD]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=366; t=1245072441; x=1245936441; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mbehring@cisco.com; z=From:=20=22Michael=20Behringer=20(mbehring)=22=20<mbehring @cisco.com> |Subject:=20Meeting=20in=20Stockholm? |Sender:=20; bh=dWKVhfm3ADsxtxpkQ1bb7zKV98ldcqme6GGKdp3tUiE=; b=PEwp3dJR396PdUIxOF8j37vEzG9SXLy8V3ubaAVYe+qtCwZzn4Z48zSlu5 Z6YesBq8lOA2+K3bV6ewpvXYTSRzKAosEO8CPm016uLH5f+OTDtakxD0sKFP nrkzzhIY9O;
Authentication-Results: ams-dkim-2; header.From=mbehring@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; ); 
Cc: tsvwg IETF list <tsvwg@ietf.org>
Subject: [tsvwg] Meeting in Stockholm?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jun 2009 13:27:16 -0000

TSVWG chairs,=20

Are we meeting in Stockholm? If so, could we request a brief slot to
present
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rsvp-security-group
keying-05.txt

Also, regarding Francois' question from June 3rd whether we can move
this draft to WGLC, can you let us know if there is anything else we
need to do?=20

Thanks,
Michael


From fernando.gont.netbook.win@gmail.com  Tue Jun 16 05:50:50 2009
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DED843A69C3 for <tsvwg@core3.amsl.com>; Tue, 16 Jun 2009 05:50:50 -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 UMkM+oglsbmm for <tsvwg@core3.amsl.com>; Tue, 16 Jun 2009 05:50:50 -0700 (PDT)
Received: from mail-gx0-f168.google.com (mail-gx0-f168.google.com [209.85.217.168]) by core3.amsl.com (Postfix) with ESMTP id E8F763A698B for <tsvwg@ietf.org>; Tue, 16 Jun 2009 05:50:49 -0700 (PDT)
Received: by gxk12 with SMTP id 12so623353gxk.13 for <tsvwg@ietf.org>; Tue, 16 Jun 2009 05:49:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=5Mx7GYBVjk9fWx6S1aWttOw73Q2/JxfbcgqcUcLvvkw=; b=ZuDZEN3xxJ6m51G3H5/Vz0dc2qhXMrnS/AVvIz8/zzrstv7FO29sKYXs7hWN6tY2b9 +w6TfAFgLlrLWHgvn//CQNu1SW/qIyQ9Rf3NvtDiVg4U75mlt4tm3YhCpuBRcX+T4kRI 7mdS3uq5AU1geYCMHcHPHkULpySweXeZQSTgQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=elmp5x+qnKIzwgR6DQZcSOu1e3ni2vOCBwfTOo4zYS3YlD1jHDbLtdJwjM4jcaKD1T mO3wLNfuS+TDq5XvolpKtKGMZoaRDz3i+cFWzq3JTYyXOd0bG9EQhGg7nT6/KInrMXMk U5Nl11St9ku7iAr0POG4wAx7U5ofY6iYdUZdg=
Received: by 10.100.208.8 with SMTP id f8mr10397382ang.64.1245156552304; Tue, 16 Jun 2009 05:49:12 -0700 (PDT)
Received: from ?172.16.1.132? (host97.190-139-184.telecom.net.ar [190.139.184.97]) by mx.google.com with ESMTPS id 6sm2242210ywi.5.2009.06.16.05.49.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 16 Jun 2009 05:49:11 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4A3794C0.6000002@gont.com.ar>
Date: Tue, 16 Jun 2009 09:49:04 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: mallman@icir.org
References: <20090615123717.B09372E00C3@lawyers.icir.org>
In-Reply-To: <20090615123717.B09372E00C3@lawyers.icir.org>
X-Enigmail-Version: 0.95.7
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: =?ISO-8859-1?Q?Alfred_H=F6nes?= <ah@tr-sys.de>, "James M. Polk" <jmpolk@cisco.com>, tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] [Tsvwg] lookup time (was Re: WGLC for Port Randomization starts now (April 1st))
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jun 2009 12:50:51 -0000

Mark Allman wrote:

>> If you retry random port, chances are that you may retry the same port
>> more than once, instead of trying a different port that might be
>> available. The larger the number of ports in uses, the more likely
>> this would be. (see the pseudo-code).
> 
> Sure.  Of course.  But, we can put this in concrete terms it would
> seem.  I.e., if we use something like alg. 3 then for a given connection
> ID we will not test for some port X again before exhausting all the
> non-X ports.  In something like alg. 2 you can in fact check X more than
> once with a probability defined by the port usage at the given time and
> also not test for all possible ports.

Agreed. And in the worst case, because of checking X more than once, you
may end up not checking other port numbers that might have worked.

-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1





From jmpolk@cisco.com  Tue Jun 16 11:16:30 2009
Return-Path: <jmpolk@cisco.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F1C7128C19A for <tsvwg@core3.amsl.com>; Tue, 16 Jun 2009 11:16:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.077
X-Spam-Level: 
X-Spam-Status: No, score=-6.077 tagged_above=-999 required=5 tests=[AWL=-0.348, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_MLH_Stock1=0.87]
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 dRwlruVZTQhv for <tsvwg@core3.amsl.com>; Tue, 16 Jun 2009 11:16:29 -0700 (PDT)
Received: from syd-iport-1.cisco.com (syd-iport-1.cisco.com [64.104.193.196]) by core3.amsl.com (Postfix) with ESMTP id 48E0B28C1A4 for <tsvwg@ietf.org>; Tue, 16 Jun 2009 11:16:24 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,230,1243814400"; d="scan'208";a="55878630"
Received: from syd-dkim-1.cisco.com ([64.104.193.116]) by syd-iport-1.cisco.com with ESMTP; 16 Jun 2009 18:16:32 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by syd-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n5GIGVm2018229;  Wed, 17 Jun 2009 04:16:32 +1000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n5GIGVAD010729; Tue, 16 Jun 2009 18:16:31 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 16 Jun 2009 11:16:31 -0700
Received: from jmpolk-wxp01.cisco.com ([10.89.1.244]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 16 Jun 2009 11:16:30 -0700
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 16 Jun 2009 13:16:29 -0500
To: "Michael Behringer (mbehring)" <mbehring@cisco.com>, "Gorry Fairhurst" <gorry@erg.abdn.ac.uk>
From: "James M. Polk" <jmpolk@cisco.com>
In-Reply-To: <DD0238A0AAE9B74A8F70A91BDF497C2F057C1364@xmb-ams-335.emea. cisco.com>
References: <DD0238A0AAE9B74A8F70A91BDF497C2F057C1364@xmb-ams-335.emea.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-ID: <XFE-SJC-2111tIzmQVu000008ad@xfe-sjc-211.amer.cisco.com>
X-OriginalArrivalTime: 16 Jun 2009 18:16:31.0040 (UTC) FILETIME=[92BDC400:01C9EEAE]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=746; t=1245176192; x=1246040192; c=relaxed/simple; s=syddkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jmpolk@cisco.com; z=From:=20=22James=20M.=20Polk=22=20<jmpolk@cisco.com> |Subject:=20Re=3A=20Meeting=20in=20Stockholm? |Sender:=20; bh=fzlQ8Iv2Efb1QlKuCYSHVFxqXHhV6E4JJIf4Z2PEvq8=; b=XIsqnbGIejJ9uLFy1iwoIw9OFXwNlQjWkgqffkyNAqstJDQZjhuTn5TL0L 0i29IaW7jMz3GtYzpm3mCXD4ac1X0HRIfCsOTA0w7a0UzkqGy/I+o3FV8+/v 8WAEqPM9YAE3EAAwwlpYjDT+K7XkyiWSiqnGcRlvgbmDnXpgOL4y4=;
Authentication-Results: syd-dkim-1; header.From=jmpolk@cisco.com; dkim=pass ( sig from cisco.com/syddkim1002 verified; ); 
Cc: tsvwg IETF list <tsvwg@ietf.org>
Subject: Re: [tsvwg] Meeting in Stockholm?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jun 2009 18:16:30 -0000

TSVWG

Yes - we are meeting in Stockholm.

I am planning on asking the WG if anyone would like a presentation 
slot (in Stockholm) in a few days, provided there is a new ID to 
present.  Your message beat me to this request.

I now have the Groupkeying-05 ID down for a timeslot.

James
TSVWG chair

At 08:27 AM 6/15/2009, Michael Behringer (mbehring) wrote:
>TSVWG chairs,
>
>Are we meeting in Stockholm? If so, could we request a brief slot to
>present
>http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rsvp-security-group
>keying-05.txt
>
>Also, regarding Francois' question from June 3rd whether we can move
>this draft to WGLC, can you let us know if there is anything else we
>need to do?
>
>Thanks,
>Michael


From jmpolk@cisco.com  Tue Jun 23 13:53:11 2009
Return-Path: <jmpolk@cisco.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F10FA28C43A for <tsvwg@core3.amsl.com>; Tue, 23 Jun 2009 13:53:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.656
X-Spam-Level: 
X-Spam-Status: No, score=-5.656 tagged_above=-999 required=5 tests=[AWL=0.073,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_MLH_Stock1=0.87]
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 pzSzxgqfaxRj for <tsvwg@core3.amsl.com>; Tue, 23 Jun 2009 13:53:10 -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 2413428C416 for <tsvwg@ietf.org>; Tue, 23 Jun 2009 13:53:10 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,277,1243814400"; d="scan'208";a="179625495"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-2.cisco.com with ESMTP; 23 Jun 2009 20:53:26 +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 n5NKrQ7U005952 for <tsvwg@ietf.org>; Tue, 23 Jun 2009 13:53:26 -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.14.3) with ESMTP id n5NKrQvl017716 for <tsvwg@ietf.org>; Tue, 23 Jun 2009 20:53:26 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 23 Jun 2009 13:53:26 -0700
Received: from jmpolk-wxp01.cisco.com ([10.89.14.55]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 23 Jun 2009 13:53:26 -0700
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 23 Jun 2009 15:53:24 -0500
To: tsvwg <tsvwg@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-ID: <XFE-SJC-212FKqhx2rf00002e1a@xfe-sjc-212.amer.cisco.com>
X-OriginalArrivalTime: 23 Jun 2009 20:53:26.0295 (UTC) FILETIME=[A78FEA70:01C9F444]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1065; t=1245790406; x=1246654406; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jmpolk@cisco.com; z=From:=20=22James=20M.=20Polk=22=20<jmpolk@cisco.com> |Subject:=20Call=20for=20presentation=20time=20at=20IETF75= 20(Stockholm) |Sender:=20; bh=ekvW/6kYrLrdHssOSyWe/zr+GMpapMdOSaSkupqw9oY=; b=gAMxA1na+N26GJ3rr21Ar3cN0P3FyX1FnGyifRpgeKbTIa+gT1m8fjgFpZ HWul5f1LpX8JCQgP9Q2vAZjgz7vhmCQiCttdYTjHrdDPP4PCESgEO9S/RpKj tvzh9HbQqnfjrGX1eTC09Iuwh9+VLFikbpTsjgzNfrNLqpEeubDbg=;
Authentication-Results: sj-dkim-1; header.From=jmpolk@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); 
Subject: [tsvwg] Call for presentation time at IETF75 (Stockholm)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jun 2009 20:53:11 -0000

TSVWG

If you have a recently new or revised ID (as of each deadline) that 
you would like to present to the WG, you need to let me know, as I'm 
building the WG schedule now.

New IDs that are individual -00s can be presented more informatively 
than revised IDs, which need to focus on what's changed since the 
last version. Please no more that one slide overviews of a given 
presentation. The WG should be familiar with the ID, so that is - 
bluntly - wasting valuable presentation time.

If you want to present, please send me the following information:

- Name of authors
- Name of presenter
- title of ID
- filename of ID (WHICH INCLUDES "-tsvwg-" !!)
- amount of time you want for presentation
	- this is usually around 10 minutes per, based on how full we get,
	  this could change up or down.

I'll need the presentations 24 hours before the session, which right 
now is the last slot on Monday evening (1740-1940), but could change 
as the Secretariat finalizes the agenda.

James
Gorry (our new WG chair!)
    TSVWG chairs


From flefauch@cisco.com  Wed Jun 24 02:11:17 2009
Return-Path: <flefauch@cisco.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F2C383A6F4F for <tsvwg@core3.amsl.com>; Wed, 24 Jun 2009 02:11:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.053
X-Spam-Level: 
X-Spam-Status: No, score=-8.053 tagged_above=-999 required=5 tests=[AWL=-2.324, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_MLH_Stock1=0.87]
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 IdGPfjlRKcVx for <tsvwg@core3.amsl.com>; Wed, 24 Jun 2009 02:11: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 B55493A6A35 for <tsvwg@ietf.org>; Wed, 24 Jun 2009 02:11:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,282,1243814400"; d="scan'208";a="204828840"
Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by sj-iport-1.cisco.com with ESMTP; 24 Jun 2009 09:11:32 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n5O9BV29032319 for <tsvwg@ietf.org>; Wed, 24 Jun 2009 11:11:31 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com [144.254.231.87]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n5O9BVGD020249 for <tsvwg@ietf.org>; Wed, 24 Jun 2009 09:11:31 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 24 Jun 2009 11:11:31 +0200
Received: from ams-flefauch-8712.cisco.com ([10.55.161.195]) by xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 24 Jun 2009 11:11:30 +0200
Message-Id: <16B1D5F4-CA86-4BCF-ACC4-F54DD843267A@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
To: "James M. Polk" <jmpolk@cisco.com>
In-Reply-To: <XFE-SJC-212FKqhx2rf00002e1a@xfe-sjc-212.amer.cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Wed, 24 Jun 2009 11:11:29 +0200
References: <XFE-SJC-212FKqhx2rf00002e1a@xfe-sjc-212.amer.cisco.com>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 24 Jun 2009 09:11:30.0766 (UTC) FILETIME=[C329EEE0:01C9F4AB]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1919; t=1245834691; x=1246698691; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=flefauch@cisco.com; z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco. com> |Subject:=20Re=3A=20[tsvwg]=20Call=20for=20presentation=20t ime=20at=20IETF75=20(Stockholm) |Sender:=20; bh=1IEYU4jhuvzfnU8aJlOC6EoWxXxOJiTCucKxLBwME4k=; b=OLSs5j2OPyGCwUmZV7Mwj7cX8y1loqRVIsG6N0daBHYqL1mh5TtM0j4bDs x4hOtiAswJPjpTBktVqjphATtuML56n9sVfmun0b55oAm9pmwkIzMNdrB+SG ghEMMAbucu;
Authentication-Results: ams-dkim-2; header.From=flefauch@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; ); 
Cc: tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] Call for presentation time at IETF75 (Stockholm)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Jun 2009 09:11:17 -0000

Hi James, Gorry,

I'd like slots for the following:

*A*
- Name of authors: F. Le Faucheur, A. Narayanan, A. Kudur
- Name of presenter: F. Le Faucheur
- title of ID:  Multiple Preemption Priority Policy Element for RSVP
- filename of ID : draft-lefaucheur-tsvwg-rsvp-multiple- 
preemption-00.txt
- amount of time : 10 mins

*B*
- filename of ID :draft-ietf-tsvwg-emergency-rsvp-12.txt
- amount of time : 5 mins  (just to keep WG posted on the key changes  
of -12 resulting from IESG review)

*C* (possibly, depending on discussions with IESG)
- filename of ID :draft-ietf-tsvwg-proxy-approaches/proto
- amount of time : 10 mins  (depending on discussions with IESG, a new  
rev may be issued)


Thanks

Francois


On 23 Jun 2009, at 22:53, James M. Polk wrote:

> TSVWG
>
> If you have a recently new or revised ID (as of each deadline) that  
> you would like to present to the WG, you need to let me know, as I'm  
> building the WG schedule now.
>
> New IDs that are individual -00s can be presented more informatively  
> than revised IDs, which need to focus on what's changed since the  
> last version. Please no more that one slide overviews of a given  
> presentation. The WG should be familiar with the ID, so that is -  
> bluntly - wasting valuable presentation time.
>
> If you want to present, please send me the following information:
>
> - Name of authors
> - Name of presenter
> - title of ID
> - filename of ID (WHICH INCLUDES "-tsvwg-" !!)
> - amount of time you want for presentation
> 	- this is usually around 10 minutes per, based on how full we get,
> 	  this could change up or down.
>
> I'll need the presentations 24 hours before the session, which right  
> now is the last slot on Monday evening (1740-1940), but could change  
> as the Secretariat finalizes the agenda.
>
> James
> Gorry (our new WG chair!)
>   TSVWG chairs
>


From gorry@erg.abdn.ac.uk  Thu Jun 25 12:51:19 2009
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 892BB3A69C0 for <tsvwg@core3.amsl.com>; Thu, 25 Jun 2009 12:51:19 -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 oyH4F16EFQwk for <tsvwg@core3.amsl.com>; Thu, 25 Jun 2009 12:51:18 -0700 (PDT)
Received: from erg.abdn.ac.uk (dee.erg.abdn.ac.uk [IPv6:2001:630:241:204:203:baff:fe9a:8c9b]) by core3.amsl.com (Postfix) with ESMTP id B719B3A6817 for <tsvwg@ietf.org>; Thu, 25 Jun 2009 12:51:16 -0700 (PDT)
Received: from Gorry-Fairhursts-Laptop-6.local (ra-gorry.erg.abdn.ac.uk [139.133.204.42]) (authenticated bits=0) by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id n5PJpD6E007806 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 25 Jun 2009 20:51:14 +0100 (BST)
Message-ID: <4A43D532.6040906@erg.abdn.ac.uk>
Date: Thu, 25 Jun 2009 20:51:14 +0100
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683. 
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
MIME-Version: 1.0
To: tsvwg <tsvwg@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: gorry@erg.abdn.ac.uk
Subject: [tsvwg] Some comments on draft-ietf-tsvwg-ecn-tunnel-02]]
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jun 2009 19:51:19 -0000

Bob,

I've just read draft-ietf-tsvwg-ecn-tunnel-02, and have some comments.
Thanks for preparing this new version, which is certainly easier to read
(and seems a little shorter) than the previous one, I think as I said at 
the IETF, the general approach in this draft seems good to me.

I've separated my comments into two parts. The first parts are comments
which I'd hope you may be able to respond to. The second parts I think 
may be editorial comments (but do ask questions, if you do not 
agree/understand).

Best wishes,

Gorry


---
1) Updates RFC4301?

I do not understand whether the document updates RFC 4301, or is an
update that aligns with the changes made in RFC 4301. At some points,
the document says the former, whereas at other points I interpret it as
the latter. This needs to be very clear in the abstract and the document
text.
---
2) Abstract

I'd be happier if the abstract could call-out that this updates the 
behaviour of tunnel end points and middleboxes. That is say something so 
that people using and configuring these devices know to read this document.

I'd also like the abstract to be clear that there is more than one mode
and say something of this topic - I'm not sure what, because I still
have questions in this space (see below).

The abstract should say the set of RFCs that are updated by the document 
(but not cite these as references), e.g.  This specification updates 
RFC3168 {and RFC4301 --- if it does}.	
---
3) Current status of PCN work

Section 3 includes:
/  A  number of wasteful or convoluted work-rounds to this problem are
       being considered for standardisation by the PCN working group (see
       Appendix D), but by far the simplest approach is just to remove
       the covert channel blockages from tunnelling behaviour, that are
       now deemed unnecessary anyway./
- Is this still the case? If this document removes this constraint, can
we just say so?
---
4) Recommended default and tunnel negotiation method for non-IPsec case?

- The following set of points are all very much related, and I would 
like some more detail on what you envisage:
---
Section 4.1
- The current section seems to step-back from actually recommending what
the mode that SHOULD be used when there is no tunnel negotiation. This
leaves me with some questions about  what a tunnel endpoint needs to do
by default.
- What do you think the document should say?
---
Section 5:
   /Before switching to normal mode, a compliant tunnel ingress that does
    not know the egress ECN capability MUST negotiate with the tunnel
    egress./
-It is not clear to me *HOW* this tunnel negotiation would normally be
performed. Can you clarify?
I found this paragraph in Section 5.3
/   Therefore, a compliant tunnel ingress MUST at least implement `normal
    mode' and, if it might be used with arbitrary tunnel egress nodes, it
    MUST also implement `compatibility mode'./
---
Section 5.3, para 2:
Section 5.3, para 4:
- Para 2 and later talks of safeguards, and if I understand it makes a
requirement that tunnel ingress MUST start in compatibility mode if it
can not negotiate. How do tunnels find out this information? (see earlier).
- I am not sure how the tunnels we be configured outside of IPsec, so
could you help me understand how this negotiation will take place?
----------
5) Informative status of section 4.3

Section 4.3 is stated as informative
- Can you remind me why this section is informative?
- It seems that there  are strong messages here on the use of the
method. /should/ and /should  not/ are used many times in a
non-normative way. I'd like to explore whether the WG would like to make
these guidelines normative.
---
6) Relation of section 6 with Updating IPsec

Section 6:
- I do not understand this section. I'd have expected a specific section
on how this document updates IPsec - if it does, but I was not sure
whether this section was intended to be the update to IPsec, or whether
the changes relate to all tunnel end points (if so, how
- The discussion here seems to assume IPsec and IKEv2, but I do not
understand the context, either more is needed or much less is needed.
---
7) Alarm raised when ECT(1) encapsulates CE.

Section 6, bullet 3 / Figure 4:
- This says an alarm is generated, Is this really a problem?
- I understand that ECT(0) is allowed in some cases to be re-mapped to
ECT(1). This then makes me wonder why a packet that was remarked from
ECT(0) to ECT(1) then raises an alarm when the inner packet was CE
marked. Have I understood this correctly?
/outer ECT(1) with inner CE/
- To me, this also seems compatible with RFC 4301.
---
8) "Danger" of not forwarding congestion indications?

Section 8:
/  In fact, ensuring congestion markings are not
    lost is itself another aspect of security, because if we allowed
    congestion notification to be lost, any attempt to enforce a response
    to congestion would be much harder./
- I accept that loss of congestion marking can impede congestion
control. I do no agree that this is accepted as a factual security
threat to the Internet.
---
9) Judgement on ECN-N?

Section 8:
This last statement on ECN-N adoption is not required or neccessary for
this document. I would rather not see statements such as /and there has
been no evidence that anyone has implemented it beyond the author's
prototype./ introduced as a side item:

    4.  The ECN nonce [RFC3540] currently has experimental status and
        there has been no evidence that anyone has implemented it beyond
        the author's prototype.
---
10) Size of Appendices.

My review ran out of steam as I read the pages of appendices and I am
not currently persauded that most of the text in the appendices is
needed to publish the updated specification.

Section A.2:

There are many places where the English could be improved. Examples from
the final para include:
/ingress confuses a proposed.../
/It ends up removing excessive amounts of traffic uncessarilly.../

Section B seems to be related to the rationale for PCN, rather than the
use of ECN over tunnels. Is this really required in this specific document?

B.1 seems to be a background to ECN
B.2 again reads like a paper, but the language is rather imprecise

Appendix C seems OK, but is it needed?

Appendix D seems to justify the work, but since this is now adopted, is
the text neccessary?
Section D.1 could be removed to improve the document.

The appendices currently seem to read more like a technical paper than
an IETF PS. If these appendices really are required, then some editorial
work is required to make this a standards quality contribution, and
clarify what actually needs to be said. After this, someone will need to
review the statements about the discussed IETF protocols carefully -
perhaps by referral to the appropriate WGs.
---
11) Relevance to GRE, IP-in-IP, L2VPN, etc, etc.

- If this change is intended to be appropriate to a range of tunnel
behaviours, how do we make sure implementors clearly understand this?
- Perhaps it would be helpful to list a set of example encapsulations at
the front of the introduction in para 1.

----------------------------------------------------------------------
* NiTs
---
Consider changing all:
/doesn't/
- to say /does not/
---
Abstract:
/in order that these combinations may be usefully/
- could we say /to allow these combination to be usefully/
---
Introduction, para 1:
/Three main change/
                  ^
  - please insert 's'
---
para after table 1,
/it must follow rules to ensure marking is propagated.../
    ^^^^^
  - could say 'needs' to avoid conflict with RFC2119 keywords?
---
/The newly specified behaviours/
  ^^^^^^^^^^^^^^^^^^^
- Please say /The new behaviours specified in this document.../
---
/   The rules for constructing the ECN field to be forwarded after tunnel
    decapsulation ensure this happens, but they are not wholly/
- That's the rules in the documents that this document updates?
- Some references would be helpful here.
---
Para starting /as a result,/
The following text, while true, will read oddly once published. I think
this sentence could be usefully rephrased to be more objective:
/As a result, an unfortunate sequence of standards actions has left us
    with nearly the worst of all possible combinations of outcomes,
    despite the best endeavours of everyone concerned./
- later in the para /still/ will likely be changed by publishing this
document and /now is/ was true at the time it was written, but not for
evermore.
---
1.1 Scope, para 2:
- should this refer to RFC 2983 for example?
---
1.2 bullet 1:
/current tunneling behaviours/
- legacy methods? - It would be clearer to explicitly reference the
specs. here.
---
section 3, para 1:
/It merely recaps/
    ^^^^^^^ - could we delete this word?
---
Figure 1
- final line has a spurious 'e' character.
---
3 paras after figure 1:
/But.../ is used twice at the start of a sentence. Consider deleting the
firs case, and replacing the second with /However,/
---
Page 11, and following:
- The covert channel appears several times. I think it is good to
document this and explain the implications, but it seems to be repeated
several times. It also appears again at the end of section 9.
---
End of section 3, first bullet, para 1:
/Firstly/
- Consider using /First,/
---
Section 3.1, end:
/ To ensure copying rather than resetting CE on ingress will not cause
    unintended side-effects, Appendix A assesses whether either harm any
    security, control or management functions. /
/It finds that resetting
    CE makes life difficult in a number of directions/
- I think I understand this, but it was not an easy read.
---
End of section 3, first bullet, para 2:
/dangerously discarding/
- I agree that this results in discard of end-to-end congestion signals,
and that from a network stability perspective this is undesirable, but I
think the word "dangerous" needs more explanation.
---
After Fig 3:
/as the ingress end of RFC4301 IPsec/
- Could this be written better, as something like:
/as the tunnel ingress processing of IPsec in RFC4301/
---
/  Not only will this streamline PCN
       standardisation, but it could also streamline other future uses of
       these codepoints./
- What exactly does this mean?
---
End of 4.2:
/not so often that the illegal combinations would amplify into a flood
of alarm messages/
- I agree that these need to be controlled. Can you say "rate-limited" -
is there some more helpful bound we can cite here for guidance?
---
Section 4.3:
/S.5/
  ^ - Section?
--
Section 4.3, bullet 1
/should not set the ECN field/
             ^^^
- Do you mean set this to CE? or do you mean re-mark? Please be more
specific.
---
Section 5:
/Note: in/
  ^^^^^^^
- Would it be OK to say "In"?
---
Section 5, para 1:
/doesn't need/
     ^^^ - could we say /does not need/
---
Section 5, para 1:
/to know what mode the ingress is in./
     ^^^^^                      ^^^^^
- Could this be /need to determine the mode of the tunnel ingress/.
---
Section 5.1, para 2:
/whichever mode the tunnel was in/
                            ^^^^^^
- could you improve the English of this line.
---
Section 5.1, para 3:
/as its behaviour/
  ^^^^^^
/since the behaviour/
---
Section 5.1, final para:
/doesn't/ and /don't/
- could you say /does not/ and /do not/
---
Section 4.3, title:
/Upgrading/
  ^^^^^^^^
- Is this upgrading or updating, I'd prefer the latter if you think this
is applicable.
---
Section 5.3, para 1:
/dangerously discarding/
- I agree that this results in discard of end-to-end congestion signals,
and that from a network stability perspective this is undesirable, but I
think the word "dangerous" needs more explanation.
---
Section 5.3, para 1:
/ratchet up/ and /ratchet down/
- I agree, but this could be written more clearly.
---
Section 5.3, para 4:
/if the egress says/
                ^^^
- advertises? - can you select a better word?
/doesn't understand the question/
- could you rephrase this please in terms of the protocol or set of
actions that need to take place?
---
Section 6, para 1:
/is a change to the ingress/
     ^^^^^^^^
- is it better to say /updates the ingress/?
---
References:
draft-ietf-pcn-architecture has now been published as RFC 5559.
---




From rbriscoe@jungle.bt.co.uk  Fri Jun 26 06:28:58 2009
Return-Path: <rbriscoe@jungle.bt.co.uk>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C4BA43A6A9A for <tsvwg@core3.amsl.com>; Fri, 26 Jun 2009 06:28:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.117
X-Spam-Level: 
X-Spam-Status: No, score=-2.117 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, 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 8vBXJS1u1WAX for <tsvwg@core3.amsl.com>; Fri, 26 Jun 2009 06:28:52 -0700 (PDT)
Received: from smtp2.smtp.bt.com (smtp2.smtp.bt.com [217.32.164.150]) by core3.amsl.com (Postfix) with ESMTP id 411FB3A6AD8 for <tsvwg@ietf.org>; Fri, 26 Jun 2009 06:28:45 -0700 (PDT)
Received: from i2kc06-ukbr.domain1.systemhost.net ([193.113.197.70]) by smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 26 Jun 2009 14:29:03 +0100
Received: from cbibipnt05.iuser.iroot.adidom.com ([147.149.196.177]) by i2kc06-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 26 Jun 2009 14:29:03 +0100
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by cbibipnt05.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a P0803.399); id 1246022942728; Fri, 26 Jun 2009 14:29:02 +0100
Received: from mut.jungle.bt.co.uk ([10.73.61.69]) by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id n5QDSuiM007908; Fri, 26 Jun 2009 14:28:57 +0100
Message-Id: <200906261328.n5QDSuiM007908@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 26 Jun 2009 14:28:54 +0100
To: gorry@erg.abdn.ac.uk
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
In-Reply-To: <4A43D532.6040906@erg.abdn.ac.uk>
References: <4A43D532.6040906@erg.abdn.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 26 Jun 2009 13:29:03.0467 (UTC) FILETIME=[12847BB0:01C9F662]
Cc: tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] Some comments on draft-ietf-tsvwg-ecn-tunnel-02]]
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jun 2009 13:28:58 -0000

Gorry,

Tx for such a thoro review. It seems nearly all the comments are 
about poor description, rather than any protocol disagreements. Is this fair?

The only substantive disagreement seems to be over whether ECT(1) 
encapsulating  CE should raise an alarm at the egress.

Inline...

At 20:51 25/06/2009, Gorry Fairhurst wrote:
>Bob,
>
>I've just read draft-ietf-tsvwg-ecn-tunnel-02, and have some comments.
>Thanks for preparing this new version, which is certainly easier to read
>(and seems a little shorter) than the previous one, I think as I 
>said at the IETF, the general approach in this draft seems good to me.
>
>I've separated my comments into two parts. The first parts are comments
>which I'd hope you may be able to respond to. The second parts I 
>think may be editorial comments (but do ask questions, if you do not 
>agree/understand).
>
>Best wishes,
>
>Gorry
>
>
>---
>1) Updates RFC4301?
>
>I do not understand whether the document updates RFC 4301, or is an
>update that aligns with the changes made in RFC 4301. At some points,
>the document says the former, whereas at other points I interpret it as
>the latter. This needs to be very clear in the abstract and the document
>text.

I thought I'd made this clear, but obviously not. I included the 
section below which is a hint to the RFC editor to make this clear in 
the headers and in the RFC index.
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
Additional changes to the RFC Index (to be removed by the RFC Editor):
In the RFC index, RFC3168 should be identified as an update to 
RFC2003. RFC4301 should be identified as an update to RFC3168.
This specification updates RFC3168 and RFC4301.
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\

Updating 4301 isn't as bad as it sounds tho:
* The tunnel ingress behaviour is in line with 4301.
* The tunnel egress behaviour adds to 4301, but doesn't change any 
4301 behaviours that currently exist. So compliance with this spec 
has no backward compat issues.
Therefore compliance can be called for only as it is needed (e.g. for PCN).

>---
>2) Abstract
>
>I'd be happier if the abstract could call-out that this updates the 
>behaviour of tunnel end points and middleboxes. That is say 
>something so that people using and configuring these devices know to 
>read this document.

I can say it updates the behaviour of *some* types of tunnel 
end-point. But it would be too complicated for an abstract to say 
exactly which ones.


>I'd also like the abstract to be clear that there is more than one mode
>and say something of this topic - I'm not sure what, because I still
>have questions in this space (see below).

The mode stuff is not needed in most cases, and the actions in this 
RFC make modes less likely to be needed. It's only for some cases 
that are trying to be completely generic and dynamic. And even then, 
it's only carrying through detailed stuff that was already in 
RFC3168. As it's not the new thing, I'd say it's not appropriate for 
the abstract.


>The abstract should say the set of RFCs that are updated by the 
>document (but not cite these as references), e.g.  This 
>specification updates RFC3168 {and RFC4301 --- if it does}.

I'd rather get the RFC Editor to put "updates RFC3168 and RFC4301" in 
the status header, than crowd the abstract.  (that's why I added the 
note for the RFC Editor in S.6 "Changes from Earlier RFCs")

>---
>3) Current status of PCN work
>
>Section 3 includes:
>/  A  number of wasteful or convoluted work-rounds to this problem are
>       being considered for standardisation by the PCN working group (see
>       Appendix D), but by far the simplest approach is just to remove
>       the covert channel blockages from tunnelling behaviour, that are
>       now deemed unnecessary anyway./
>- Is this still the case? If this document removes this constraint, can
>we just say so?

It's still the case, because the PCN work can't assume this spec will 
get through yet - last calls can raise probs even tho I've been 
careful to ensure there are no back-compat issues for the security area.

>---
>4) Recommended default and tunnel negotiation method for non-IPsec case?
>
>- The following set of points are all very much related, and I would 
>like some more detail on what you envisage:
>---
>Section 4.1
>- The current section seems to step-back from actually recommending what
>the mode that SHOULD be used when there is no tunnel negotiation. This
>leaves me with some questions about  what a tunnel endpoint needs to do
>by default.
>- What do you think the document should say?

OK, I thought I'd made it clear, but obviously not.
4.1 refers forward to 5. on this issue (so as not to crowd the main 
point with details that aren't usually necessary).
5.1 says "...the new normal ingress behaviour introduces no backward 
compatibility isses with IKEv2 [RFC4306] IPsec [RFC4301] tunnels, and 
no need for any new modes, options or configuration. "

I think I see the problem. I tend to start by describing the logic 
for all cases, then say what this implies for each. Instead I should 
assert what should be done in each case, then say why. I'll do the 
latter in the next rev.
It's a good point. Implementers just want to find the bits they need 
to read and ignore the rest.

>---
>Section 5:
>   /Before switching to normal mode, a compliant tunnel ingress that does
>    not know the egress ECN capability MUST negotiate with the tunnel
>    egress./
>-It is not clear to me *HOW* this tunnel negotiation would normally be
>performed. Can you clarify?

Again, I've obviously made it hard-reading by giving the general 
logic for all cases, rather than listing each common case. How about 
text something like this to start off with:

"Both endpoints of an RFC4301 tunnel can be sure that the other end 
is 4301-compatible, because the tunnel is only formed after key 
management has been completed, at which point both ends will be 
RFC4301-compliant by definition. Therefore, an IPsec tunnel ingress 
compliant with RFC4301 does not need to implement compatibility mode 
for legacy ECN tunnels.

Similarly, the implementer of any (non-RFC4301) tunnel ingress that 
is designed to be deployed at the same time as its corresponding 
tunnel egress, will not need to implement compatibility mode for 
legacy ECN tunnels.

However, an implementer might want to create a general-purpose tunnel 
ingress that includes some form of tunnel endpoint discovery to 
dynamically create and destroy tunnels to different tunnel egresses, 
driven by the varying needs of arriving packets. If the tunnel 
discovery process is arranged to only ever find tunnel egresses 
compliant with normal mode of RFC3168 or a later ECN tunnelling 
specification, then the ingress would not need to implement 
compatibility mode. But if earlier tunnel egresses might be 
discovered, the ingress would need to implement compatibility mode as 
well as normal mode, and also implement appropriate negotiation as 
defined in RFC3168."

Would this text be OK?

>I found this paragraph in Section 5.3
>/   Therefore, a compliant tunnel ingress MUST at least implement `normal
>    mode' and, if it might be used with arbitrary tunnel egress nodes, it
>    MUST also implement `compatibility mode'./

Is this text a problem? Or are you saying it solves the above issues? 
Or you want it said earlier?

>---
>Section 5.3, para 2:
>Section 5.3, para 4:
>- Para 2 and later talks of safeguards, and if I understand it makes a
>requirement that tunnel ingress MUST start in compatibility mode if it
>can not negotiate.

It doesn't say "if it cannot negotiate". It says if it "does not know 
the egress ECN capability ".

>How do tunnels find out this information? (see earlier).

It's easy if both ends of the tunnel are statically config'd (ie the 
info is part of the config, and it's up to the sysadmin to get it right).

I'm trying to get rid of modes, but I have to allow for the same 
problem RFC3168 had to allow for. So I have to allow the same 
negotiation as RFC3168. I don't know if anyone does this, or how 
exactly they do it. I've been told negotiation is frowned on. But I'm 
not adding anything beyond what RFC3168 said.

I'll say "...negotiation as in RFC3168" if that helps.

In S.6 I have clarified that RFC4301 IPsec implies the negotiation 
machinery of RFC3168 isn't needed for an IPsec tunnel any more:

"The optional ECN Tunnel field in the IPsec security association 
database (SAD) and the optional ECN Tunnel Security Association 
Attribute defined in RFC3168 are no longer needed. The security 
association (SA) has no policy on ECN usage, because all RFC4301 
tunnels now support ECN without any policy choice. "

>- I am not sure how the tunnels we be configured outside of IPsec, so
>could you help me understand how this negotiation will take place?
>----------
>5) Informative status of section 4.3
>
>Section 4.3 is stated as informative
>- Can you remind me why this section is informative?
>- It seems that there  are strong messages here on the use of the
>method. /should/ and /should  not/ are used many times in a
>non-normative way. I'd like to explore whether the WG would like to make
>these guidelines normative.

Maybe I don't understand customary procedure, but I imagine that 
guidelines for future protocol design are generally informative, and 
normative is only needed when a standards track doc is written that 
uses the guidelines. As this doc is intended for standards track, I 
wanted to make the boundary clear, where it had shifted into 
"informational land".

I don't believe guidelines for future protocol design mean anything 
more than "you'll need to give good reasons, if you break these". 
Perhaps my philosophy for encouraging evolvability doesn't match the 
mentality of the typical IETFer these days tho, so discussion is welcome.

>---
>6) Relation of section 6 with Updating IPsec
>
>Section 6:
>- I do not understand this section. I'd have expected a specific section
>on how this document updates IPsec - if it does, but I was not sure
>whether this section was intended to be the update to IPsec, or whether
>the changes relate to all tunnel end points (if so, how

This section is meant to summarise how the changes introduced in 
prior sections update previous RFCs.

But the section is not organised by previous RFCs. It's organised by function:
- ingress
- egress
- negotation between the two (if present).

For each function, it says which aspects of previous RFCs are updated.

This was designed to help implementers, who would be working on each 
function, having to pull together the relevant RFCs for that function.

>- The discussion here seems to assume IPsec and IKEv2, but I do not
>understand the context, either more is needed or much less is needed.

It doesn't assume IPSec. It just says what has changed if you're doing IPSec.

IKEv2 key negotiation is integral to RFC4301. But David Black told me 
there could be corner cases that use manual keying instead.

I could remove the stuff on the manual keying corner case. I'd like 
to take David Black's advice on that. He implied if I put it in it 
will get unnecessarily complicated given no-one does this in 
practice, altho RFC4301 allows them to. But if I leave it out, 
someone could point out that we haven't thought about it.

Does this help?

>---
>7) Alarm raised when ECT(1) encapsulates CE.
>
>Section 6, bullet 3 / Figure 4:
>- This says an alarm is generated, Is this really a problem?

In practice, implementers tend to drop unexpected combinations, on 
the spurious pretext that there might be a security risk.

The idea behind recommending alarms is to give implementers a 
legitimate way to not drop combinations just because are unexpected 
today, given they might be used in the future. While still allowing 
operators to monitor for possible attacks.

Then, if there's a sudden rise in alarms of this type, the operator 
can engage brain and say either
- "Ah, that's because RFC7024 is starting to be implemented, we can 
turn off those alarms" or
- "Hmmm, there's not even an experimental standard that would cause 
this strange combination, could this be a novel attack?"

>- I understand that ECT(0) is allowed in some cases to be re-mapped to
>ECT(1).

If you know of these cases, then fine, I'll remove the need for an 
alarm. But I wasn't aware of any. Any specifics?

>This then makes me wonder why a packet that was remarked from
>ECT(0) to ECT(1) then raises an alarm when the inner packet was CE
>marked. Have I understood this correctly?
>/outer ECT(1) with inner CE/
>- To me, this also seems compatible with RFC 4301.

RFC4301 & RFC3168 define the same output (CE) as I do for this 
combination. The issue is over whether the combination of inputs 
would ever be *expected* to arise, given none of the other ECN RFCs 
could lead to this happening.

I'm not aware of a valid ECN protocol transition that would produce 
this combination, so I've suggested it should raise an alarm. RFC3168 
had some cases that raised alarms, but I just think it missed this 
one. If I'm wrong, I'll happily retract.

>---
>8) "Danger" of not forwarding congestion indications?
>
>Section 8:
>/  In fact, ensuring congestion markings are not
>    lost is itself another aspect of security, because if we allowed
>    congestion notification to be lost, any attempt to enforce a response
>    to congestion would be much harder./
>- I accept that loss of congestion marking can impede congestion
>control. I do no agree that this is accepted as a factual security
>threat to the Internet.

Flooding attacks classify as a security threat (not information 
security, but still security). Enforcing congestion control is a 
valid approach for handling flooding attacks. If we allow explicit 
congestion information to be thrown away, it makes both responding to 
it and enforcing a response to it harder. That's all I'm saying. 
Surely that's non-controversial?

I appreciate that a large part of the security community focuses on 
using information security rather than congestion control enforcement 
to solve flooding, but that doesn't mean they are right. And others 
disagree with them.


>---
>9) Judgement on ECN-N?
>
>Section 8:
>This last statement on ECN-N adoption is not required or neccessary for
>this document. I would rather not see statements such as /and there has
>been no evidence that anyone has implemented it beyond the author's
>prototype./ introduced as a side item:
>
>    4.  The ECN nonce [RFC3540] currently has experimental status and
>        there has been no evidence that anyone has implemented it beyond
>        the author's prototype.

An RFC changes as it moves from draft to RFC. To start with it has to 
justify what it's doing. As people accept the arguments, a lot of 
justification text becomes removeable. I'd be happy to remove 
justifications eventually (as text like this can get dated), but I'd 
rather not until the arguments have got past the security area.

We have two conflicting choices to reconcile. This is one of the 
reasons for the choice made. If we don't mention it, it weakens the case.


>---
>10) Size of Appendices.
>
>My review ran out of steam as I read the pages of appendices and I am
>not currently persauded that most of the text in the appendices is
>needed to publish the updated specification.

I'm also running out of steam here, as I'm meant to be going on 
holiday for a week now. As my wife is politely suggesting a cup of 
water might end up being spilled over my keyboard, I'll also be brief...


>Section A.2:
>
>There are many places where the English could be improved. Examples from
>the final para include:
>/ingress confuses a proposed.../
>/It ends up removing excessive amounts of traffic uncessarilly.../
>
>Section B seems to be related to the rationale for PCN, rather than the
>use of ECN over tunnels. Is this really required in this specific document?
>
>B.1 seems to be a background to ECN
>B.2 again reads like a paper, but the language is rather imprecise
>
>Appendix C seems OK, but is it needed?
>
>Appendix D seems to justify the work, but since this is now adopted, is
>the text neccessary?
>Section D.1 could be removed to improve the document.
>
>The appendices currently seem to read more like a technical paper than
>an IETF PS. If these appendices really are required, then some editorial
>work is required to make this a standards quality contribution, and
>clarify what actually needs to be said. After this, someone will need to
>review the statements about the discussed IETF protocols carefully -
>perhaps by referral to the appropriate WGs.

There's a balance needed between recording why things were done and 
not making the thing flowery and unweildy. Point taken. I'll give 
this some attention in the next draft.

>---
>11) Relevance to GRE, IP-in-IP, L2VPN, etc, etc.
>
>- If this change is intended to be appropriate to a range of tunnel
>behaviours, how do we make sure implementors clearly understand this?
>- Perhaps it would be helpful to list a set of example encapsulations at
>the front of the introduction in para 1.

In the rev between -01 & -02 I took out all the stuff on non-IP-in-IP 
tunnels. It will probably re-appear in some future draft, but not this one.

If I've left any text in here that implies this is relevant beyond 
IP-in-IP, pls point me at it. I thought I had taken it all out.

Tx for the nits below. I'll handle them.


Bob


>----------------------------------------------------------------------
>* NiTs
>---
>Consider changing all:
>/doesn't/
>- to say /does not/
>---
>Abstract:
>/in order that these combinations may be usefully/
>- could we say /to allow these combination to be usefully/
>---
>Introduction, para 1:
>/Three main change/
>                  ^
>  - please insert 's'
>---
>para after table 1,
>/it must follow rules to ensure marking is propagated.../
>    ^^^^^
>  - could say 'needs' to avoid conflict with RFC2119 keywords?
>---
>/The newly specified behaviours/
>  ^^^^^^^^^^^^^^^^^^^
>- Please say /The new behaviours specified in this document.../
>---
>/   The rules for constructing the ECN field to be forwarded after tunnel
>    decapsulation ensure this happens, but they are not wholly/
>- That's the rules in the documents that this document updates?
>- Some references would be helpful here.
>---
>Para starting /as a result,/
>The following text, while true, will read oddly once published. I think
>this sentence could be usefully rephrased to be more objective:
>/As a result, an unfortunate sequence of standards actions has left us
>    with nearly the worst of all possible combinations of outcomes,
>    despite the best endeavours of everyone concerned./
>- later in the para /still/ will likely be changed by publishing this
>document and /now is/ was true at the time it was written, but not for
>evermore.
>---
>1.1 Scope, para 2:
>- should this refer to RFC 2983 for example?
>---
>1.2 bullet 1:
>/current tunneling behaviours/
>- legacy methods? - It would be clearer to explicitly reference the
>specs. here.
>---
>section 3, para 1:
>/It merely recaps/
>    ^^^^^^^ - could we delete this word?
>---
>Figure 1
>- final line has a spurious 'e' character.
>---
>3 paras after figure 1:
>/But.../ is used twice at the start of a sentence. Consider deleting the
>firs case, and replacing the second with /However,/
>---
>Page 11, and following:
>- The covert channel appears several times. I think it is good to
>document this and explain the implications, but it seems to be repeated
>several times. It also appears again at the end of section 9.
>---
>End of section 3, first bullet, para 1:
>/Firstly/
>- Consider using /First,/
>---
>Section 3.1, end:
>/ To ensure copying rather than resetting CE on ingress will not cause
>    unintended side-effects, Appendix A assesses whether either harm any
>    security, control or management functions. /
>/It finds that resetting
>    CE makes life difficult in a number of directions/
>- I think I understand this, but it was not an easy read.
>---
>End of section 3, first bullet, para 2:
>/dangerously discarding/
>- I agree that this results in discard of end-to-end congestion signals,
>and that from a network stability perspective this is undesirable, but I
>think the word "dangerous" needs more explanation.
>---
>After Fig 3:
>/as the ingress end of RFC4301 IPsec/
>- Could this be written better, as something like:
>/as the tunnel ingress processing of IPsec in RFC4301/
>---
>/  Not only will this streamline PCN
>       standardisation, but it could also streamline other future uses of
>       these codepoints./
>- What exactly does this mean?
>---
>End of 4.2:
>/not so often that the illegal combinations would amplify into a flood
>of alarm messages/
>- I agree that these need to be controlled. Can you say "rate-limited" -
>is there some more helpful bound we can cite here for guidance?
>---
>Section 4.3:
>/S.5/
>  ^ - Section?
>--
>Section 4.3, bullet 1
>/should not set the ECN field/
>             ^^^
>- Do you mean set this to CE? or do you mean re-mark? Please be more
>specific.
>---
>Section 5:
>/Note: in/
>  ^^^^^^^
>- Would it be OK to say "In"?
>---
>Section 5, para 1:
>/doesn't need/
>     ^^^ - could we say /does not need/
>---
>Section 5, para 1:
>/to know what mode the ingress is in./
>     ^^^^^                      ^^^^^
>- Could this be /need to determine the mode of the tunnel ingress/.
>---
>Section 5.1, para 2:
>/whichever mode the tunnel was in/
>                            ^^^^^^
>- could you improve the English of this line.
>---
>Section 5.1, para 3:
>/as its behaviour/
>  ^^^^^^
>/since the behaviour/
>---
>Section 5.1, final para:
>/doesn't/ and /don't/
>- could you say /does not/ and /do not/
>---
>Section 4.3, title:
>/Upgrading/
>  ^^^^^^^^
>- Is this upgrading or updating, I'd prefer the latter if you think this
>is applicable.
>---
>Section 5.3, para 1:
>/dangerously discarding/
>- I agree that this results in discard of end-to-end congestion signals,
>and that from a network stability perspective this is undesirable, but I
>think the word "dangerous" needs more explanation.
>---
>Section 5.3, para 1:
>/ratchet up/ and /ratchet down/
>- I agree, but this could be written more clearly.
>---
>Section 5.3, para 4:
>/if the egress says/
>                ^^^
>- advertises? - can you select a better word?
>/doesn't understand the question/
>- could you rephrase this please in terms of the protocol or set of
>actions that need to take place?
>---
>Section 6, para 1:
>/is a change to the ingress/
>     ^^^^^^^^
>- is it better to say /updates the ingress/?
>---
>References:
>draft-ietf-pcn-architecture has now been published as RFC 5559.
>---
>

________________________________________________________________
Bob Briscoe,               Networks Research Centre, BT Research 


From rbriscoe@jungle.bt.co.uk  Fri Jun 26 08:50:07 2009
Return-Path: <rbriscoe@jungle.bt.co.uk>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B2A5A3A6B6C for <tsvwg@core3.amsl.com>; Fri, 26 Jun 2009 08:50:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.682
X-Spam-Level: 
X-Spam-Status: No, score=-1.682 tagged_above=-999 required=5 tests=[AWL=-0.435, BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, RCVD_IN_DNSWL_LOW=-1, SARE_MLH_Stock1=0.87]
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 jnmsDCYxH+bT for <tsvwg@core3.amsl.com>; Fri, 26 Jun 2009 08:50:00 -0700 (PDT)
Received: from smtp2.smtp.bt.com (smtp2.smtp.bt.com [217.32.164.150]) by core3.amsl.com (Postfix) with ESMTP id DA3BA3A6922 for <tsvwg@ietf.org>; Fri, 26 Jun 2009 08:49:59 -0700 (PDT)
Received: from i2kc08-ukbr.domain1.systemhost.net ([193.113.197.71]) by smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 26 Jun 2009 16:49:56 +0100
Received: from cbibipnt08.iuser.iroot.adidom.com ([147.149.100.81]) by i2kc08-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 26 Jun 2009 16:49:47 +0100
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by cbibipnt08.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a P0803.399); id 1246031386412; Fri, 26 Jun 2009 16:49:46 +0100
Received: from mut.jungle.bt.co.uk ([10.73.61.69]) by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id n5QFngXb011576; Fri, 26 Jun 2009 16:49:43 +0100
Message-Id: <200906261549.n5QFngXb011576@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 26 Jun 2009 16:49:28 +0100
To: "James M. Polk" <jmpolk@cisco.com>
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
In-Reply-To: <XFE-SJC-2111tIzmQVu000008ad@xfe-sjc-211.amer.cisco.com>
References: <DD0238A0AAE9B74A8F70A91BDF497C2F057C1364@xmb-ams-335.emea.cisco.com> <XFE-SJC-2111tIzmQVu000008ad@xfe-sjc-211.amer.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 26 Jun 2009 15:49:47.0864 (UTC) FILETIME=[BBC53580:01C9F675]
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, tsvwg IETF list <tsvwg@ietf.org>
Subject: Re: [tsvwg] Meeting in Stockholm?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jun 2009 15:50:07 -0000

James,

1/ Could you put me down for a tentative slot for
draft-ietf-tsvwg-byte-pkt-congest ?

2/ And could I have a 10min slot for
draft-ietf-tsvwg-ecn-tunnel ?

I'm planning to rev ecn-tunnel-02; I've just reminded all those who 
volunteered to review it (and Gorry beat me to it), so there will be 
some changes for the better (I hope).

I'm also planning to present ecn-tunnel in the security area, as I 
think the stds actions have reached / are reaching consensus now, it 
just needs much better wordsmithing.

I will re-activitate byte-pkt (it's expired) but I may not get time 
to do a substantive rev, in which case I'll relinquish the slot.


Bob

At 19:16 16/06/2009, James M. Polk wrote:
>TSVWG
>
>Yes - we are meeting in Stockholm.
>
>I am planning on asking the WG if anyone would like a presentation 
>slot (in Stockholm) in a few days, provided there is a new ID to 
>present.  Your message beat me to this request.

________________________________________________________________
Bob Briscoe,               Networks Research Centre, BT Research 


From ingemar.s.johansson@ericsson.com  Mon Jun 29 12:40:27 2009
Return-Path: <ingemar.s.johansson@ericsson.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 88DF53A69C0 for <tsvwg@core3.amsl.com>; Mon, 29 Jun 2009 12:40:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.099
X-Spam-Level: 
X-Spam-Status: No, score=-6.099 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 0IdRyaX5JQ2b for <tsvwg@core3.amsl.com>; Mon, 29 Jun 2009 12:40:26 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 6E05D3A67B1 for <tsvwg@ietf.org>; Mon, 29 Jun 2009 12:40:26 -0700 (PDT)
X-AuditID: c1b4fb3e-b7be1ae000004757-db-4a4918bbcdd8
Received: from esealmw126.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw4.ericsson.se (Symantec Mail Security) with SMTP id 16.4E.18263.BB8194A4; Mon, 29 Jun 2009 21:40:43 +0200 (CEST)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 29 Jun 2009 21:40:42 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 29 Jun 2009 21:40:40 +0200
Message-ID: <130EBB38279E9847BAAAE0B8F9905F8C0174F1E7@esealmw109.eemea.ericsson.se>
In-Reply-To: <mailman.11454.1246022939.4936.tsvwg@ietf.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on draft-ietf-tsvwg-ecn-tunnel-02
Thread-Index: Acn2Yj0/negY+3ITRjqsJGu+5EMj/ACh0ogA
References: <mailman.11454.1246022939.4936.tsvwg@ietf.org>
From: "Ingemar Johansson S" <ingemar.s.johansson@ericsson.com>
To: <tsvwg@ietf.org>
X-OriginalArrivalTime: 29 Jun 2009 19:40:42.0820 (UTC) FILETIME=[7D34F840:01C9F8F1]
X-Brightmail-Tracker: AAAAAA==
Cc: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
Subject: [tsvwg] Comments on draft-ietf-tsvwg-ecn-tunnel-02
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jun 2009 19:40:27 -0000

Hi

I have read draft-ietf-tsvwg-ecn-tunnel-02 and below some comments. =20

Figure 4:=20
 I wonder what will happen if we have a TCP stack that implements =
ECN-nonce. Wouldn't the rules in figure 4 lead to a faulty nonce-sum =
with negative consequences for the TCP throughput. Or is this out of =
scope?. =20

Page 19: "sfaeguards" -> "safeguards"

Page 22 bullet 4. (ECN nonce) "..no evidence that anyone has implemented =
it beyond the author's prototype". This one made me curios... In general =
one get the feeling that it is not good or recommended to use ECT(1) e.g =
as a light congetsion indication (I believe it is written in similar =
words in RFC3168), the main reason is guess the ECN-nonce, this bullet =
says "don't care about the ECN-nonce". Is there any reference to a =
deeper discussion on around this?

Page 29: "DIffserv" -> "Diffserv"


Regards
Ingemar
*******************************************=20
Ingemar Johansson=20
Senior Research Engineer, IETF "nethead"=20
EAB/TVK - Multimedia Technologies=20
Ericsson Research Ericsson AB=20
Box 920 S-971 28 Lule=E5, Sweden=20
Tel: +46 (0)10 7143042=20
ECN: 852-43042=20
ECC: 852-19042
Mobile: +46 (0)730 783289=20
Visit http://labs.ericsson.com !
*******************************************=20
