Re: [radext] Update RFC 6929 in draft-ietf-radext-radius-fragmentation

Alejandro Perez Mendez <alex@um.es> Wed, 19 March 2014 10:15 UTC

Return-Path: <alex@um.es>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A92D81A06C3 for <radext@ietfa.amsl.com>; Wed, 19 Mar 2014 03:15:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.748
X-Spam-Level:
X-Spam-Status: No, score=-4.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c8cigIFmgZ8N for <radext@ietfa.amsl.com>; Wed, 19 Mar 2014 03:15:46 -0700 (PDT)
Received: from xenon23.um.es (xenon23.um.es [155.54.212.163]) by ietfa.amsl.com (Postfix) with ESMTP id 2E7101A06C8 for <radext@ietf.org>; Wed, 19 Mar 2014 03:15:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by xenon23.um.es (Postfix) with ESMTP id 258B744EC for <radext@ietf.org>; Wed, 19 Mar 2014 11:15:37 +0100 (CET)
X-Virus-Scanned: by antispam in UMU at xenon23.um.es
Received: from xenon23.um.es ([127.0.0.1]) by localhost (xenon23.um.es [127.0.0.1]) (amavisd-new, port 10024) with LMTP id eSSm-a-R9up4 for <radext@ietf.org>; Wed, 19 Mar 2014 11:15:37 +0100 (CET)
Received: from [10.42.0.19] (84.124.131.72.dyn.user.ono.com [84.124.131.72]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: alex) by xenon23.um.es (Postfix) with ESMTPSA id E663B44C9 for <radext@ietf.org>; Wed, 19 Mar 2014 11:15:36 +0100 (CET)
Message-ID: <53296E47.4060802@um.es>
Date: Wed, 19 Mar 2014 11:15:35 +0100
From: Alejandro Perez Mendez <alex@um.es>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: radext@ietf.org
References: <53285DE2.9040802@cisco.com> <035801cf42d2$99464b80$cbd2e280$@augustcellars.com> <5328C172.5080305@deployingradius.com>
In-Reply-To: <5328C172.5080305@deployingradius.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/radext/G8fm5_DD1k7J91D5vpeIFMIRIbE
Subject: Re: [radext] Update RFC 6929 in draft-ietf-radext-radius-fragmentation
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/radext>, <mailto:radext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/radext/>
List-Post: <mailto:radext@ietf.org>
List-Help: <mailto:radext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radext>, <mailto:radext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Mar 2014 10:15:50 -0000

El 18/03/14 22:58, Alan DeKok escribió:
> Jim Schaad wrote:
>> While it is true that an implementer of 6929 does not need to see this
>> document, it is also true that this document is effectively allocating a
>> bit from a structure that is in that document.  If this document does
>> not update 6929, then it is possible that the next document to update
>> that structure will fail to notice this and allocate the same bit for a
>> different purpose.
>   I hope we're all smart enough to remember that the bit is allocated.
> If we're not... the WG should be shut down.
>
>> I believe that this update relationship needs to be retained.
>   It may be useful, but IETF process may forbid it.

In my opinion, this draft does update 6929, as it updates 2865, since
6929 specifies the reserved field MUST be set to 0, and SHOULD be
ignored by recipients, and we change that.

However, following the same reasoning than with 2865, probably it should
not be actually specified until the fragmentation document is re-issued
as a standards track document (if it does).

Regards

>
>   Alan DeKok.
>
> _______________________________________________
> radext mailing list
> radext@ietf.org
> https://www.ietf.org/mailman/listinfo/radext