RE: [Fwd: New Version Notification for draft-gont-6man-flowlabel-security-00]

"George, Wes E [NTK]" <Wesley.E.George@sprint.com> Tue, 17 August 2010 14:05 UTC

Return-Path: <Wesley.E.George@sprint.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 959DB3A6A6F for <ipv6@core3.amsl.com>; Tue, 17 Aug 2010 07:05:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.432
X-Spam-Level:
X-Spam-Status: No, score=-3.432 tagged_above=-999 required=5 tests=[AWL=0.167, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IfHSkn--xbDO for <ipv6@core3.amsl.com>; Tue, 17 Aug 2010 07:05:52 -0700 (PDT)
Received: from VA3EHSOBE003.bigfish.com (va3ehsobe003.messaging.microsoft.com [216.32.180.13]) by core3.amsl.com (Postfix) with ESMTP id 74FC83A6A6A for <ipv6@ietf.org>; Tue, 17 Aug 2010 07:05:52 -0700 (PDT)
Received: from mail51-va3-R.bigfish.com (10.7.14.250) by VA3EHSOBE003.bigfish.com (10.7.40.23) with Microsoft SMTP Server id 8.1.340.0; Tue, 17 Aug 2010 14:06:26 +0000
Received: from mail51-va3 (localhost.localdomain [127.0.0.1]) by mail51-va3-R.bigfish.com (Postfix) with ESMTP id E8AFBD4017D; Tue, 17 Aug 2010 14:06:26 +0000 (UTC)
X-SpamScore: -54
X-BigFish: VS-54(zf7Iz936eK1be0L542N1370I4015L62a3L9371P103dKzz1202hzz8275dh1033ILz2fh87h2a8h61h)
X-Spam-TCS-SCL: 0:0
X-FB-DOMAIN-IP-MATCH: fail
Received: from mail51-va3 (localhost.localdomain [127.0.0.1]) by mail51-va3 (MessageSwitch) id 1282053985932512_32628; Tue, 17 Aug 2010 14:06:25 +0000 (UTC)
Received: from VA3EHSMHS025.bigfish.com (unknown [10.7.14.238]) by mail51-va3.bigfish.com (Postfix) with ESMTP id D6619A10046; Tue, 17 Aug 2010 14:06:25 +0000 (UTC)
Received: from pdaasdm2.corp.sprint.com (144.229.32.57) by VA3EHSMHS025.bigfish.com (10.7.99.35) with Microsoft SMTP Server (TLS) id 14.0.482.44; Tue, 17 Aug 2010 14:06:22 +0000
Received: from plswh04a.ad.sprint.com (plswh04a.corp.sprint.com [144.226.251.24]) by pdaasdm2.corp.sprint.com (Sentrion-MTA-4.0.3/Sentrion-MTA-4.0.3) with ESMTP id o7HE26gX007280 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 17 Aug 2010 09:02:06 -0500
Received: from PLSWM01C.ad.sprint.com ([144.226.242.77]) by plswh04a.ad.sprint.com ([2002:90e2:fb18::90e2:fb18]) with mapi; Tue, 17 Aug 2010 09:06:25 -0500
From: "George, Wes E [NTK]" <Wesley.E.George@sprint.com>
To: Fernando Gont <fernando@gont.com.ar>, "ipv6@ietf.org" <ipv6@ietf.org>
Date: Tue, 17 Aug 2010 09:06:23 -0500
Subject: RE: [Fwd: New Version Notification for draft-gont-6man-flowlabel-security-00]
Thread-Topic: [Fwd: New Version Notification for draft-gont-6man-flowlabel-security-00]
Thread-Index: Acs6gN8StsryN4+pT+emZVXg8eOp7gDkUq7Q
Message-ID: <F7EB0A7C707E39409A73CD0353242551A8BF8239C9@PLSWM01C.ad.sprint.com>
References: <4C649599.2000404@gont.com.ar>
In-Reply-To: <4C649599.2000404@gont.com.ar>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Reverse-DNS: smtpda2.sprint.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Aug 2010 14:05:53 -0000

draft-blake-ipv6-flow-label-nonce-02 is expired and I haven't heard much effort to push it forward again. IMO it would be more helpful to consider security implications and evaluate your solution with draft-carpenter-6man-flow-update-03, draft-donley-6man-flowlabel-transport-sig-00, etc in mind. I believe that it should integrate well, but I'd rather see a draft revision that takes this explicitly into consideration.

Thanks,
Wes George

-----Original Message-----
From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of Fernando Gont
Sent: Thursday, August 12, 2010 8:45 PM
To: ipv6@ietf.org
Subject: [Fwd: New Version Notification for draft-gont-6man-flowlabel-security-00]

Folks,

I have just published an Internet-Draft entitled "Security Assessment of
the IPv6 Flow Label" that analyzes the security implications of the Flow
Label header field, and proposes a scheme to set the Flow Label that is
compliant with RFC 3697, and compatible with
draft-blake-ipv6-flow-label-nonce-02.

The I-D is available at:
http://tools.ietf.org/id/draft-gont-6man-flowlabel-security-00.txt

Thanks!

Kind regards,
Fernando




-------- Original Message --------
Subject: New Version Notification for
draft-gont-6man-flowlabel-security-00
Date: Thu, 12 Aug 2010 15:07:50 -0700 (PDT)
From: IETF I-D Submission Tool <idsubmission@ietf.org>
To: fernando@gont.com.ar


A new version of I-D, draft-gont-6man-flowlabel-security-00.txt has been
successfully submitted by Fernando Gont and posted to the IETF repository.

Filename:        draft-gont-6man-flowlabel-security
Revision:        00
Title:           Security Assessment of the IPv6 Flow Label
Creation_date:   2010-08-12
WG ID:           Independent Submission
Number_of_pages: 20

Abstract:
This document discusses the security implications of the IPv6 "Flow
Label" header field, and analyzes possible schemes for selecting the
Flow Label value of IPv6 packets.




The IETF Secretariat.




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




--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------


This e-mail may contain Sprint Nextel proprietary information intended for the sole use of the recipient(s). Any use by others is prohibited. If you are not the intended recipient, please contact the sender and delete all copies of the message.