Re: [IPsec] WG Last Call: draft-ietf-ipsecme-traffic-visibility-05
gabriel montenegro <g_e_montenegro@yahoo.com> Mon, 13 July 2009 18:22 UTC
Return-Path: <g_e_montenegro@yahoo.com>
X-Original-To: ipsec@core3.amsl.com
Delivered-To: ipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 82BDF28C352 for <ipsec@core3.amsl.com>; Mon, 13 Jul 2009 11:22:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.288
X-Spam-Level:
X-Spam-Status: No, score=-2.288 tagged_above=-999 required=5 tests=[AWL=-0.309, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_SORBS_WEB=0.619]
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 9WgHQz50lfiL for <ipsec@core3.amsl.com>; Mon, 13 Jul 2009 11:22:05 -0700 (PDT)
Received: from web82608.mail.mud.yahoo.com (web82608.mail.mud.yahoo.com [68.142.201.125]) by core3.amsl.com (Postfix) with SMTP id 4839E28C663 for <ipsec@ietf.org>; Mon, 13 Jul 2009 11:21:00 -0700 (PDT)
Received: (qmail 42760 invoked by uid 60001); 13 Jul 2009 18:21:28 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1247509288; bh=6XpBBUYwngIZgkyOQcAq9LWFymXYAcQhXraxDmy7ZzQ=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=jdtQgQ9aJbWcXmlM50z6NFKBSKKq/bqkyoh5qUKlrMALWODnWM9z1ddgqlH62dIaQbfUQXobs2F5r2UHJVPPpfYFM6kv0EJCkXUuKfJbJqc6hcPH6+tq8Yk5wlSES+82yILd6c6PjtJUARfipbtGxH5Cf5eqnvO8yWZqW8dIAf8=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=gUZQoTYkOFClZyiPpOihK2SfDGhtQVsRDGsOAacgFtyiLw5Lv6Hpj1J5mbeMnch/sTO+ixl3da08DJFHmLNWAUXuqfG9nW5UL1TP+hRo2Z3sVEVZN7aniQUKoSAtSwAc5ZGz3VZF4QX/gNz9i6IbnE4PkyO2WGbIcHJo5e3L0gA=;
Message-ID: <380869.42304.qm@web82608.mail.mud.yahoo.com>
X-YMail-OSG: jh6XBLIVM1lhKdnStJDJ9HTg4XfF9HUvCw9b.BK2GG.w0erIJYbi4BxBN570l0vEaOIZyUUx9.Hn__UnL0Zxom95IXYKekSV5ESQOwb8ELZN2.8CU5IyDsagTYWc02yLXSIHOQOlnhLlynpspuP3H5qKTm00hQue5lyF1lMuYXRUQ1ysPEgzncIcVvXHDd7IO8tn0GWavOc7nRjYHMery2eVI.OLDahFV_9XGhvctsAGIjvcuxWf8Il6obBCIO_HM3jJaA8E7olfo1yYEQGh0Pg7sEAHwvUVfES4DEke.19_3VHx7Mn8rFI_ogH3g2Rh2QpMd.c4hU8pQQEkVYN8DH1qYWP2
Received: from [12.197.88.101] by web82608.mail.mud.yahoo.com via HTTP; Mon, 13 Jul 2009 11:21:28 PDT
X-Mailer: YahooMailRC/1357.22 YahooMailWebService/0.7.289.10
References: <7F9A6D26EB51614FBF9F81C0DA4CFEC8E8ABD594E4@il-ex01.ad.checkpoint.com> <006FEB08D9C6444AB014105C9AEB133F433538CE3E@il-ex01.ad.checkpoint.com> <372852.53939.qm@web82605.mail.mud.yahoo.com>
Date: Mon, 13 Jul 2009 11:21:28 -0700
From: gabriel montenegro <g_e_montenegro@yahoo.com>
To: Yoav Nir <ynir@checkpoint.com>, Yaron Sheffer <yaronf@checkpoint.com>, "ipsec@ietf.org" <ipsec@ietf.org>
In-Reply-To: <372852.53939.qm@web82605.mail.mud.yahoo.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-317283926-1247509288=:42304"
Subject: Re: [IPsec] WG Last Call: draft-ietf-ipsecme-traffic-visibility-05
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipsec>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jul 2009 18:22:06 -0000
Brian Swander notes that we should be explicit about the IV which may be present. It may be clear that this is the intention, but I agree that it is best to be explicit. This is what we suggest in light of this: NEW: HdrLen, 8 bits: Offset from the beginning of the WESP header to the beginning of the Rest of Payload Data (i.e., past the IV, if present) within the encapsulated ESP header, inoctets. Gabriel > >From: gabriel montenegro <g_e_montenegro@yahoo.com> >To: Yoav Nir <ynir@checkpoint.com>; Yaron Sheffer <yaronf@checkpoint.com>; "ipsec@ietf.org" <ipsec@ietf.org> >Sent: Monday, July 13, 2009 9:05:23 AM >Subject: Re: [IPsec] WG Last Call: draft-ietf-ipsecme-traffic-visibility-05 > > >Hi Yoav, > >Good catch, we say offset *to* what, but we don’t say *from* where. > >Among the co-authors, we'd like to suggest this as a simple text change to address this: > >OLD: > HdrLen, 8 bits: Offset to the beginning of the Payload Data in > octets. > >NEW: > HdrLen, 8 bits: Offset from the beginning of the WESP header to > the beginning of the Payload Data within the encapsulated ESP header, in > octets. > > >Does this sound ok? > >BTW, in the case of TrailerLen we do say both *from* as well as *to*. > >Gabriel > >> >>From: Yoav Nir <ynir@checkpoint.com> >>To: Yaron Sheffer <yaronf@checkpoint.com>; "ipsec@ietf.org" <ipsec@ietf.org> >>Sent: Tuesday, July 7, 2009 4:35:19 AM >>Subject: Re: [IPsec] WG Last Call: draft-ietf-ipsecme-traffic-visibility-05 >> >> >>I’ve read it again, and it seems fine. One minor issue, though. >> >>Section 2 describes the WESP header format. It has the following: >> HdrLen, 8 bits: Offset to the beginning of the Payload Data in >> octets. The receiver MUST ensure that this field matches with >> the header offset computed from using the negotiated SA and MUST >> drop the packet in case it doesn't match. >> >>I think I know what they mean, but it’s entirely not clear what this field is supposed to hold. Is it the size of the existing ESP header? Is it that + 4? How about “the combined length of all the ESP fields that precede the “Payload Data” field” in ESP” ? >> >> >> >> ________________________________ >>From:ipsec-bounces@ietf.org [mailto:ipsec-bounces@ietf.org] On Behalf Of Yaron Sheffer >>Sent: Saturday, July 04, 2009 10:48 PM >>To: ipsec@ietf.org >>Subject: [IPsec] WG Last Call: draft-ietf-ipsecme-traffic-visibility-05 >> >>This is the beginning of a two-week WG Last Call, which will end July 18. The target status for this document is Proposed Standard. The current document is at http://tools.ietf.org/html/draft-ietf-ipsecme-traffic-visibility-05. >> >>If you have not read the document before now, please do so. Having fresh eyes on the document often brings up important issues. If you HAVE read it before, please note that there have been several revisions since San Francisco , so you might want to read it again (plus it’s a short document). Send any comments to the list, even if they are as simple as "I read it and it seems fine". >> >>Please clearly indicate the position of any issue in the Internet Draft, and if possible provide alternative text. Please also indicate the nature or severity of the error or correction, e.g. major technical, minor technical, nit, so that we can quickly judge the extent of problems with the document. >> >>Thanks, >> Yaron >> >>Email secured by Check Point >> >>
- [IPsec] WG Last Call: draft-ietf-ipsecme-traffic-… Yaron Sheffer
- Re: [IPsec] WG Last Call: draft-ietf-ipsecme-traf… Jack Kohn
- Re: [IPsec] WG Last Call: draft-ietf-ipsecme-traf… Yoav Nir
- Re: [IPsec] WG Last Call: draft-ietf-ipsecme-traf… QIU Ying
- Re: [IPsec] WG Last Call: draft-ietf-ipsecme-traf… gabriel montenegro
- Re: [IPsec] WG Last Call: draft-ietf-ipsecme-traf… gabriel montenegro
- Re: [IPsec] WG Last Call: draft-ietf-ipsecme-traf… Yoav Nir
- Re: [IPsec] WG Last Call: draft-ietf-ipsecme-traf… QIU Ying
- Re: [IPsec] WG Last Call: draft-ietf-ipsecme-traf… Grewal, Ken
- Re: [IPsec] WG Last Call: draft-ietf-ipsecme-traf… QIU Ying
- Re: [IPsec] WG Last Call: draft-ietf-ipsecme-traf… Grewal, Ken
- Re: [IPsec] WG Last Call: draft-ietf-ipsecme-traf… Bhatia, Manav (Manav)
- Re: [IPsec] WG Last Call: draft-ietf-ipsecme-traf… QIU Ying
- Re: [IPsec] WG Last Call: draft-ietf-ipsecme-traf… QIU Ying
- Re: [IPsec] WG Last Call: draft-ietf-ipsecme-traf… Bhatia, Manav (Manav)
- Re: [IPsec] WG Last Call: draft-ietf-ipsecme-traf… Yaron Sheffer
- Re: [IPsec] WG Last Call: draft-ietf-ipsecme-traf… Bhatia, Manav (Manav)
- Re: [IPsec] WG Last Call: draft-ietf-ipsecme-traf… Grewal, Ken
- [IPsec] WG Last Call: draft-ietf-ipsecme-roadmap-… Yaron Sheffer
- Re: [IPsec] WG Last Call: draft-ietf-ipsecme-road… Paul Hoffman
- Re: [IPsec] WG Last Call: draft-ietf-ipsecme-road… Laganier, Julien
- Re: [IPsec] WG Last Call: draft-ietf-ipsecme-road… Greg Daley
- Re: [IPsec] WG Last Call: draft-ietf-ipsecme-road… Scott C Moonen
- Re: [IPsec] WG Last Call: draft-ietf-ipsecme-road… Yoav Nir
- [IPsec] Comments on draft-ietf-ipsecme-roadmap-03 Suresh Krishnan