Re: [apps-discuss] process and editing questions: RFC errata
Erik Wilde <dret@berkeley.edu> Sat, 23 February 2013 16:24 UTC
Return-Path: <dret@berkeley.edu>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1EA421F8FAE for <apps-discuss@ietfa.amsl.com>; Sat, 23 Feb 2013 08:24:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.262
X-Spam-Level:
X-Spam-Status: No, score=-6.262 tagged_above=-999 required=5 tests=[AWL=-0.263, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4]
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 3iORwDbNA8e0 for <apps-discuss@ietfa.amsl.com>; Sat, 23 Feb 2013 08:24:10 -0800 (PST)
Received: from cm03fe.IST.Berkeley.EDU (cm03fe.IST.Berkeley.EDU [169.229.218.144]) by ietfa.amsl.com (Postfix) with ESMTP id 0C64921F8FCF for <apps-discuss@ietf.org>; Sat, 23 Feb 2013 08:24:10 -0800 (PST)
Received: from 46-126-158-51.dynamic.hispeed.ch ([46.126.158.51] helo=dretpro.local) by cm03fe.ist.berkeley.edu with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (auth plain:dret@berkeley.edu) (envelope-from <dret@berkeley.edu>) id 1U9HtL-0005qo-C8; Sat, 23 Feb 2013 08:24:09 -0800
Message-ID: <5128ED20.6030502@berkeley.edu>
Date: Sat, 23 Feb 2013 17:24:00 +0100
From: Erik Wilde <dret@berkeley.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "t.petch" <ietfc@btconnect.com>
References: <5124D91C.1000703@berkeley.edu> <000901ce1023$3c4b7140$4001a8c0@gateway.2wire.net> <51263634.7040906@berkeley.edu> <015e01ce1052$3098b540$4001a8c0@gateway.2wire.net>
In-Reply-To: <015e01ce1052$3098b540$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: REST Discuss <rest-discuss@yahoogroups.com>, apps-discuss@ietf.org
Subject: Re: [apps-discuss] process and editing questions: RFC errata
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Feb 2013 16:24:10 -0000
hello tom. On 2013-02-21 17:40 , t.petch wrote: > In passing, some lines of formal definition exceed the permitted length > for an RFC line so a little reorganising will be needed, probably best > sooner rather than later as they will need validating before the I-D can > advance and reorganising can introduce syntax errors. thanks for noting, https://raw.github.com/dret/I-D/master/xml-patch/draft-wilde-xml-patch-05.txt should look better (not yet submitted). > I may have missed the errata but I cannot recall a reference to them on > the apps-discuss list. If they are modified and then approved, which > usually happens, then your I-D should follow suit so the sooner they are > processed the better. Which might mean you requesting the AD to set the > wheels in motion, explaining why timeliness matters. the errata are still just in the "reported" state, http://www.rfc-editor.org/errata_search.php?rfc=5261 lists the 4 i have submitted. 3 of those now are actually part of the updates to RFC 5261 in the draft, so i am wondering whether these errata are needed anymore? ideally, my draft would update RFC 5261, and then the errata would be redundant, right? > And, out of curiosity, do you expect people to use XPath 1.0 or 2.0? I > ask because in Netconf, I was keen to specify 2.0 and not 1.0, the > handling of namespaces in 2.0 seemed superior, but was told we could not > because there were no implementations for people to use, that 2.0 was a > great idea that had not happened (mmm IPv6?). The Normative reference > for Yang remains the 1999 version. 2.0 is a vast improvement over 1.0, but it also is much more complex to implement. when 1.0 was released, XML was all the rage and there were a lot of people implementing specs. when 2.0 was released, the XML hyper curve already trended downward, plus it's just harder to implement. as a result it's true that it's surprisingly hard to find implementations of 2.0. so while personally, i always use 2.0 because you can write better code, it's true that in specs, if you can get away with 1.0, it may be a good idea to stick to it. cheers, dret. -- erik wilde | mailto:dret@berkeley.edu - tel:+1-510-2061079 | | UC Berkeley - School of Information (ISchool) | | http://dret.net/netdret http://twitter.com/dret |
- [apps-discuss] process and editing questions: RFC… Erik Wilde
- Re: [apps-discuss] process and editing questions:… t.petch
- Re: [apps-discuss] process and editing questions:… Erik Wilde
- Re: [apps-discuss] process and editing questions:… t.petch
- Re: [apps-discuss] process and editing questions:… Erik Wilde
- Re: [apps-discuss] process and editing questions:… t.petch
- [apps-discuss] draft-wilde-xml-patch and updates … Erik Wilde
- Re: [apps-discuss] draft-wilde-xml-patch and upda… t.petch
- Re: [apps-discuss] draft-wilde-xml-patch and upda… Barry Leiba
- Re: [apps-discuss] draft-wilde-xml-patch and upda… Robert Sparks