Re: [radext] Update RFC 6929 in draft-ietf-radext-radius-fragmentation
Alejandro Perez Mendez <alex@um.es> Tue, 25 March 2014 08:29 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 562F11A0369 for <radext@ietfa.amsl.com>; Tue, 25 Mar 2014 01:29:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level:
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 aQ9CFO0-TWUt for <radext@ietfa.amsl.com>; Tue, 25 Mar 2014 01:29:44 -0700 (PDT)
Received: from xenon21.um.es (xenon21.um.es [155.54.212.161]) by ietfa.amsl.com (Postfix) with ESMTP id B09681A013B for <radext@ietf.org>; Tue, 25 Mar 2014 01:29:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by xenon21.um.es (Postfix) with ESMTP id A52B43FAB6 for <radext@ietf.org>; Tue, 25 Mar 2014 09:29:41 +0100 (CET)
X-Virus-Scanned: by antispam in UMU at xenon21.um.es
Received: from xenon21.um.es ([127.0.0.1]) by localhost (xenon21.um.es [127.0.0.1]) (amavisd-new, port 10024) with LMTP id imUGlFjwy8to for <radext@ietf.org>; Tue, 25 Mar 2014 09:29:41 +0100 (CET)
Received: from [10.42.0.18] (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 xenon21.um.es (Postfix) with ESMTPSA id 5FA363F84B for <radext@ietf.org>; Tue, 25 Mar 2014 09:29:40 +0100 (CET)
Message-ID: <53313E73.4030502@um.es>
Date: Tue, 25 Mar 2014 09:29:39 +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> <53303FB2.8090002@restena.lu>
In-Reply-To: <53303FB2.8090002@restena.lu>
X-Enigmail-Version: 1.6
Content-Type: multipart/alternative; boundary="------------040604070403080604030700"
Archived-At: http://mailarchive.ietf.org/arch/msg/radext/8gtbVo1pdvdbtt9NjCsw8H5Ln-k
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: Tue, 25 Mar 2014 08:29:47 -0000
El 24/03/14 15:22, Stefan Winter escribió: > Hello, > > with my shiny new chair hat on: > >>> 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 it's a bad idea to rely on collective memory or a mailing list > archive. > > So, regardless of what the consensus will be: try an "Updates" or not; > create an IANA registry or not - the fact that a loosely-knit > relationship to RFC6929 exists, and where the pitfalls are, should be > reflected inside the draft itself. > > As for where - I think it helps to keep in mind that that there will be > numerous rounds of reviewing going on after the document has cleared WGLC. > > In particular, the Operations Area will conduct an ops-dir review as > part of the IETF LC. There are very specific questions in the ops-dir > review template, one of which is: > > "Are there any coexistence issues?" > > The probability that an ops-dir reviewer will pick up the T-Bit > allocation coexistence issue during his reading are very high > (especially if the proto write-up mentions this as one of the > contentious points :-) ); so if that issue is not explicitly documented, > it will probably surface at that point, and we'll need to deal with it. > > We can of course wait for that to happen, but I'd rather preempt such a > useless extra round and fix the issue in the draft right now. > > Another question in the ops-dir review is > > "Is an operational considerations and/or manageability section part of > the document?" > > I believe the best way forward is to add such a section to the draft (it > could be a sub-section of Introduction, or be a section of its own). The > section would document what was argued on the mailing list, where the > pitfalls are, and that an "Updates" would be a reasonable possiblity to > avoid them if allowed by process. > > With that text in the document, the WG can then try to use Updates or > not - and the reason for doing so can then be found in the document > itself. If the actual Updates relationship later doesn't fly, the text > highlighting the issue will at least still be in there - and not in > someone's brain or deep down in the ML archives. I realise that the text > then wouldn't necessarily be found by someone implementing a follow-up > spec to RFC6929 due to lack of an Updated-By, but chances are at least > way better. > > (And as an individual: if we have an Operations/Manageability section > anyway at that point - wouldn't it be a good idea to move the "formal > violation of RFC2865" into that section as well? ) I think it is a good idea to have such a section, specially is you think it will be requested by ops-dir reviewers if not present. I would place it as section 10, right before "Security considerations" section, instead of in the Introduction section, to avoid basing the explanations on something that has not been described yet. I also think that the "formal violation..." discussion should be moved here. We could also include the "proxying based on User-Name" restriction too. Regards, Alejandro > > Greetings, > > Stefan Winter > >>> I believe that this update relationship needs to be retained. >> It may be useful, but IETF process may forbid it. >> >> Alan DeKok. >> >> _______________________________________________ >> radext mailing list >> radext@ietf.org >> https://www.ietf.org/mailman/listinfo/radext >> > > > > _______________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext
- [radext] Update RFC 6929 in draft-ietf-radext-rad… Benoit Claise
- Re: [radext] Update RFC 6929 in draft-ietf-radext… Alan DeKok
- Re: [radext] Update RFC 6929 in draft-ietf-radext… Benoit Claise
- Re: [radext] Update RFC 6929 in draft-ietf-radext… lionel.morand
- Re: [radext] Update RFC 6929 in draft-ietf-radext… Jim Schaad
- Re: [radext] Update RFC 6929 in draft-ietf-radext… Alan DeKok
- Re: [radext] Update RFC 6929 in draft-ietf-radext… Alejandro Perez Mendez
- Re: [radext] Update RFC 6929 in draft-ietf-radext… Michael Richardson
- Re: [radext] Update RFC 6929 in draft-ietf-radext… Alan DeKok
- Re: [radext] Update RFC 6929 in draft-ietf-radext… Sam Hartman
- Re: [radext] Update RFC 6929 in draft-ietf-radext… Michael Richardson
- Re: [radext] Update RFC 6929 in draft-ietf-radext… Alan DeKok
- Re: [radext] Update RFC 6929 in draft-ietf-radext… Stefan Winter
- Re: [radext] Update RFC 6929 in draft-ietf-radext… Alejandro Perez Mendez
- Re: [radext] Update RFC 6929 in draft-ietf-radext… Stefan Winter
- Re: [radext] Update RFC 6929 in draft-ietf-radext… Alan DeKok
- Re: [radext] Update RFC 6929 in draft-ietf-radext… Jim Schaad