Re: [IPsec] WG Last Call: draft-ietf-ipsecme-traffic-visibility-05

"QIU Ying" <qiuying@i2r.a-star.edu.sg> Tue, 14 July 2009 07:39 UTC

Return-Path: <qiuying@i2r.a-star.edu.sg>
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 D0E1D3A6A33 for <ipsec@core3.amsl.com>; Tue, 14 Jul 2009 00:39:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[AWL=1.320, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5vH4mLsaIo5m for <ipsec@core3.amsl.com>; Tue, 14 Jul 2009 00:39:13 -0700 (PDT)
Received: from gw1.scei.a-star.edu.sg (gw1.scei.a-star.edu.sg [192.122.140.10]) by core3.amsl.com (Postfix) with ESMTP id B28B63A6E06 for <ipsec@ietf.org>; Tue, 14 Jul 2009 00:38:58 -0700 (PDT)
Received: from mailfe01.teak.local.net ([10.217.253.173]) by gw1.scei.a-star.edu.sg (8.14.1/8.14.1) with ESMTP id n6E7Wqf0005857; Tue, 14 Jul 2009 15:32:53 +0800
Received: from t3400 ([10.217.141.123]) by mailfe01.teak.local.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 14 Jul 2009 15:34:28 +0800
Message-ID: <DF4B170548E644539355FC9A7B3D7143@t3400>
From: QIU Ying <qiuying@i2r.a-star.edu.sg>
To: Yaron Sheffer <yaronf@checkpoint.com>, ipsec@ietf.org
References: <7F9A6D26EB51614FBF9F81C0DA4CFEC8E8ABD594E4@il-ex01.ad.checkpoint.com>
Date: Tue, 14 Jul 2009 15:30:27 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_017B_01CA0498.03D12A20"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-OriginalArrivalTime: 14 Jul 2009 07:34:28.0179 (UTC) FILETIME=[84E4AA30:01CA0455]
X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5, 1.2.40, 4.0.166 definitions=2009-07-14_02:2009-07-03, 2009-07-14, 2009-07-13 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-0811170000 definitions=main-0907140005
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: Tue, 14 Jul 2009 07:39:14 -0000

Regarding the Next Header in section 2, what will be happened if the value of Next Header is zero (i.e. IPv6 Hop-by-Hop option) and the packet is not encrypted?

Regards
Qiu Ying

  ----- Original Message ----- 
  From: Yaron Sheffer 
  To: ipsec@ietf.org 
  Sent: Sunday, July 05, 2009 3:48 AM
  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



------------------------------------------------------------------------------


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

Institute for Infocomm Research disclaimer:  "This email is confidential and may be privileged. If you are not the intended recipient, please delete it and notify us immediately. Please do not copy or use it for any purpose, or disclose its contents to any other person. Thank you."