[CCAMP] FW: Last Call: <draft-ietf-tsvwg-rsvp-security-groupkeying-10.txt> (Applicability of Keying Methods for RSVP Security) to Informational RFC

"Adrian Farrel" <adrian@olddog.co.uk> Tue, 19 July 2011 20:12 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 642BC21F8AB9; Tue, 19 Jul 2011 13:12:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level:
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[AWL=0.063, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dNlJW4EXTtsU; Tue, 19 Jul 2011 13:12:52 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 7584B21F89CC; Tue, 19 Jul 2011 13:12:52 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id p6JK9GSk007746; Tue, 19 Jul 2011 21:09:17 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id p6JK9Ewr007724 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 19 Jul 2011 21:09:16 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: mpls@ietf.org, 'CCAMP' <ccamp@ietf.org>
Date: Tue, 19 Jul 2011 21:12:48 +0100
Message-ID: <00fa01cc4650$3c1997e0$b44cc7a0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AcxGT+Xet643lgRjQNalrlcZ/HFG5A==
Content-Language: en-gb
Subject: [CCAMP] FW: Last Call: <draft-ietf-tsvwg-rsvp-security-groupkeying-10.txt> (Applicability of Keying Methods for RSVP Security) to Informational RFC
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jul 2011 20:12:53 -0000

MPLS and CCAMP working groups.

Please be aware of and participate in this IETF last call.

Thanks,
Adrian

> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of
> The IESG
> Sent: 18 July 2011 14:29
> To: IETF-Announce
> Cc: tsvwg@ietf.org
> Subject: Last Call: <draft-ietf-tsvwg-rsvp-security-groupkeying-10.txt>
> (Applicability of Keying Methods for RSVP Security) to Informational RFC
> 
> 
> The IESG has received a request from the Transport Area Working Group
> (tsvwg) to consider the following document:
> - 'Applicability of Keying Methods for RSVP Security'
>   <draft-ietf-tsvwg-rsvp-security-groupkeying-10.txt> as an Informational
> RFC
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2011-08-01. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    The Resource reSerVation Protocol (RSVP) allows hop-by-hop integrity
>    protection of RSVP neighbors.  This requires messages to be
>    cryptographically protected 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 document also discusses
>    applicability of encrypting RSVP messages.
> 
> The Responsible AD notes that the IPR declaration terms seem to apply to
> standards-track documents, but not necessarily to an Informational document.
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-rsvp-security-groupkeying/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-rsvp-security-groupkeying/
> 
> 
> The following IPR Declarations may be related to this I-D:
> 
>    http://datatracker.ietf.org/ipr/988/
>