[Pce] Note on encryption for PCE Discovery

JP Vasseur <jvasseur@cisco.com> Thu, 12 July 2007 22:53 UTC

Return-path: <pce-bounces@lists.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I97X7-0008Vx-BW; Thu, 12 Jul 2007 18:53:13 -0400
Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1I97X6-0008Vq-Ik for pce-confirm+ok@megatron.ietf.org; Thu, 12 Jul 2007 18:53:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I97X6-0008Vi-95 for pce@ietf.org; Thu, 12 Jul 2007 18:53:12 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I97X2-0000Ie-0N for pce@ietf.org; Thu, 12 Jul 2007 18:53:12 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 12 Jul 2007 18:53:07 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAOdNlkZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,534,1175486400"; d="scan'208"; a="65056198:sNHT25442746"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l6CMr7kF025620; Thu, 12 Jul 2007 18:53:07 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l6CMr7s0019306; Thu, 12 Jul 2007 22:53:07 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 12 Jul 2007 18:53:07 -0400
Received: from [10.86.104.182] ([10.86.104.182]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 12 Jul 2007 18:53:07 -0400
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <7A2C4E9D-B9D2-44D2-8081-4B8B5B263CBF@cisco.com>
Content-Transfer-Encoding: 7bit
From: JP Vasseur <jvasseur@cisco.com>
Date: Thu, 12 Jul 2007 18:52:33 -0400
To: pce@ietf.org
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 12 Jul 2007 22:53:07.0403 (UTC) FILETIME=[69B809B0:01C7C4D7]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=746; t=1184280787; x=1185144787; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jvasseur@cisco.com; z=From:=20JP=20Vasseur=20<jvasseur@cisco.com> |Subject:=20Note=20on=20encryption=20for=20PCE=20Discovery |Sender:=20 |To:=20pce@ietf.org; bh=JJAHD0CieO/jxORms0RLUEsh+IoFUwCu9nnvTw3SEXs=; b=X0qF9yG6rtD9/YQj9h6U7j3gLeYh6/AIvgWBgbTNb4FY/21CorbuOa3Wi2J4LjCm5iqR3dQz xIEwdfr9At97JMYdocT+egHkajFYsWYib9PLxIad25+igSszGjyec1o8;
Authentication-Results: rtp-dkim-1; header.From=jvasseur@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc:
Subject: [Pce] Note on encryption for PCE Discovery
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Path Computation Element <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@lists.ietf.org?subject=subscribe>
Errors-To: pce-bounces@lists.ietf.org

Dear WG,

draft-ietf-pce-disco-proto-ospf-06.txt and draft-ietf-pce-disco-proto- 
isis-06.txt both passed WG LC and we're now working on addressing the  
DISCUSS raised during IESG review. On the particular topic of  
encryption, RFC 4674 states the following in section 4.6. "- There  
MUST be a mechanism to encrypt discovery information."

draft-ietf-pce-disco-proto-ospf-06.txt clearly states that this  
requirement is not met: "OSPF provides no encryption mechanism for  
protecting the privacy of LSAs, and in particular the privacy of the  
PCE discovery information.", which is perfectly acceptable as long as  
this is documented.

If any of you has an issue with this, let us know by July 19, noon ET.

Thanks.

JP.


_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce