[CCAMP] FW: New Version Notification for draft-balls-ccamp-relax-loop-check-02.txt

Steve Balls <Steve.Balls@metaswitch.com> Tue, 20 November 2012 23:08 UTC

Return-Path: <Steve.Balls@metaswitch.com>
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 3060C21F87FD for <ccamp@ietfa.amsl.com>; Tue, 20 Nov 2012 15:08:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 BMjxuj-33TPn for <ccamp@ietfa.amsl.com>; Tue, 20 Nov 2012 15:08:02 -0800 (PST)
Received: from SFPETS2.metaswitch.com (sfpets2.metaswitch.com [198.147.226.9]) by ietfa.amsl.com (Postfix) with ESMTP id A56E621F87F4 for <ccamp@ietf.org>; Tue, 20 Nov 2012 15:08:02 -0800 (PST)
Received: from SFPCAS1.datcon.co.uk (172.24.4.3) by SFPETS2.metaswitch.com (172.24.4.12) with Microsoft SMTP Server (TLS) id 14.2.318.4; Tue, 20 Nov 2012 15:07:23 -0800
Received: from SFPMBX1.datcon.co.uk ([fe80::8471:982f:7fd5:35ef]) by SFPCAS1.datcon.co.uk ([fe80::1924:e6dd:b536:8f10%12]) with mapi id 14.02.0318.004; Tue, 20 Nov 2012 15:08:01 -0800
From: Steve Balls <Steve.Balls@metaswitch.com>
To: "ccamp@ietf.org" <ccamp@ietf.org>
Thread-Topic: New Version Notification for draft-balls-ccamp-relax-loop-check-02.txt
Thread-Index: AQHNxoAAK4pcx6S4aUOgu5ieaIH1opfxc6gw
Date: Tue, 20 Nov 2012 23:06:00 +0000
Deferred-Delivery: Tue, 20 Nov 2012 23:06:00 +0000
Message-ID: <1508F62A2F511042B45D315CFF74E229D265B9E1@SFPMBX1.datcon.co.uk>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.24.112.28]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: [CCAMP] FW: New Version Notification for draft-balls-ccamp-relax-loop-check-02.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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, 20 Nov 2012 23:08:03 -0000

Hi CCAMP,

We have updated draft-balls-ccamp-relax-loop-check with some further examples demonstrating why we believe an update to RSVP is required, and modified the language to clarify the proposed solution does not introduce loops.

We would like to discuss this on the list.  Specifically, do you agree that the use cases described in the draft are valid and that modifications to RSVP are required to support them?

Thanks,

Steve, Jon and Cyril.
(Authors)


-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Monday, November 19, 2012 10:02 AM
To: Steve Balls
Cc: Jonathan Hardwick; NSN - Cyril Margaria
Subject: New Version Notification for draft-balls-ccamp-relax-loop-check-02.txt


A new version of I-D, draft-balls-ccamp-relax-loop-check-02.txt
has been successfully submitted by Steve Balls and posted to the IETF repository.

Filename:	 draft-balls-ccamp-relax-loop-check
Revision:	 02
Title:		 Relaxing RSVP Loop Checking
Creation date:	 2012-11-19
WG ID:		 Individual Submission
Number of pages: 10
URL:             http://www.ietf.org/internet-drafts/draft-balls-ccamp-relax-loop-check-02.txt
Status:          http://datatracker.ietf.org/doc/draft-balls-ccamp-relax-loop-check
Htmlized:        http://tools.ietf.org/html/draft-balls-ccamp-relax-loop-check-02
Diff:            http://www.ietf.org/rfcdiff?url2=draft-balls-ccamp-relax-loop-check-02

Abstract:
   This specification relaxes the rules governing loop checking within
   RSVP.  These were originally defined in RFC3209 and are too strict
   for the requirements of today's data planes.

                                                                                  


The IETF Secretariat