Re: [Int-area] RSVP for IPv6 implementors: your use of RAO value 3

"Vishwas Manral" <vishwas.ietf@gmail.com> Thu, 15 May 2008 06:28 UTC

Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1FE053A697C; Wed, 14 May 2008 23:28:38 -0700 (PDT)
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0E1FB3A6905 for <ipv6@core3.amsl.com>; Wed, 14 May 2008 23:28:31 -0700 (PDT)
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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iEbl+Lvw605b for <ipv6@core3.amsl.com>; Wed, 14 May 2008 23:28:29 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.174]) by core3.amsl.com (Postfix) with ESMTP id D8FE13A67D6 for <ipv6@ietf.org>; Wed, 14 May 2008 23:28:29 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 27so301083wfd.31 for <ipv6@ietf.org>; Wed, 14 May 2008 23:26:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=eIqgPTj5PQOu4oTgbg9qjrX3go1JqqKdpgWd6nmmda0=; b=Iml7DJZs4rmnmthvbAR65jlrLYDcHD48iJjUAOnO4X6k2fSNM7vLCVcD/GMQyErhILhteT7sDhu4netfipzkrF9vORh46bw0FisQF6H2skRB9GHMGId9BAyNNMmQfx7mGtbPRqx3te45lbv2Wsj1otPxFgOpUAjqbdCa66yjGVw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=cyaxHFmgrtiQTjd9NJDGpGehNlQ7gSm17ZRboX8Y9OlsrZdfKhpi/Mhtu1XXuVC4JpB1OFGnbBwkmoJ6uqNCMv2IePnPZC9rXFnGW8DrJNSaZQBS76oOOtE77UZ7iNxQIYxA9cOPpWyOLIrFpEZTz2/wnts4VQUMSme98kz0oDA=
Received: by 10.142.125.5 with SMTP id x5mr798598wfc.191.1210832792601; Wed, 14 May 2008 23:26:32 -0700 (PDT)
Received: by 10.143.164.14 with HTTP; Wed, 14 May 2008 23:26:32 -0700 (PDT)
Message-ID: <77ead0ec0805142326n77ce1692vaf57d35378f5fe27@mail.gmail.com>
Date: Thu, 15 May 2008 11:56:32 +0530
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: bob.hinden@nokia.com, jmanner@cs.Helsinki.FI
Subject: Re: [Int-area] RSVP for IPv6 implementors: your use of RAO value 3
In-Reply-To: <913678E6-D723-419B-B19D-7430D9DF4641@nokia.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <Pine.LNX.4.64.0805141642001.28722@sbz-31.cs.Helsinki.FI> <913678E6-D723-419B-B19D-7430D9DF4641@nokia.com>
Cc: IPv6 Operations <v6ops@ops.ietf.org>, IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

Hi Bob/ Jukka,

We at IPInfusion support RSVP for IPv6. Our implementation will
however not be affected by the fix mentioned below.

Thanks,
Vishwas

On Wed, May 14, 2008 at 9:24 PM, Bob Hinden <bob.hinden@nokia.com> wrote:
> FYI
>
> Begin forwarded message:
>
>> From: "Jukka MJ Manner" <jmanner@cs.Helsinki.FI>
>> Date: May 14, 2008 3:51:08 PM GMT+02:00
>> To: Transport Area WG <tsvwg@ietf.org>, Internet Area <int-area@ietf.org
>> >
>> Subject: [Int-area] RSVP for IPv6 implementors: your use of RAO
>> value 3
>>
>>
>> Hi,
>>
>> We are in the middle of fixing the IP Router Alert Option registry and
>> allocations, and one issue affects the current RSVP implementations.
>>
>> There are two values that indicate end-to-end RSVP:
>> "1" Datagram contains RSVP message    [RFC2711]
>> "3" RSVP Aggregation Level 0          [RFC3175]
>>
>> We are currently proposing that value "3" should be removed from
>> use, and
>> reserved (not to be allocated to any protocol). Thus, value "1"
>> should be
>> used to indicate end-to-end RSVP.
>>
>> The question is: who have RSVP implementations for IPv6, and would
>> this
>> change break something?
>>
>> Regards,
>> Jukka
>> _______________________________________________
>> Int-area mailing list
>> Int-area@ietf.org
>> https://www.ietf.org/mailman/listinfo/int-area
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------