IETF Logo Mail Archive

[rfc-i] draft-xml2rfc-21 error in rnc

jhildebr at cisco.com (Joe Hildebrand (jhildebr)) Wed, 02 September 2015 19:58 UTC

From: "jhildebr at cisco.com"
Date: Wed, 02 Sep 2015 19:58:56 +0000
Subject: [rfc-i] draft-xml2rfc-21 error in rnc
In-Reply-To: <55E60764.7050605@gmail.com>
References: <20150831103117.GA11731@miek.nl> <FB9DAEB0-A385-49D0-AE96-30F16B6AF52D@vpnc.org> <55E4DEAD.7040306@tzi.org> <EDB64F32-55E6-461C-B820-D71E7C88B5CE@vpnc.org> <20150901195532.GB21684@miek.nl> <55E60764.7050605@gmail.com>
Message-ID: <4B855FED-0693-4118-A357-58E6B65BB235@cisco.com>

On 9/1/15, 2:15 PM, "rfc-interest on behalf of Brian E Carpenter" <rfc-interest-bounces at rfc-editor.org on behalf of brian.e.carpenter at gmail.com> wrote:

>>Well... to be blunt: don't do that. Why is <svg> so special?
>
>Er, have you looked at draft-brownlee-svg-rfc-11 recently?

I've just re-read that draft, and commented in a separate thread.  Once draft-brownlee-svg-rfc includes RNC, I'm fine with including that RNC *by value* in draft-hoffman-xml2rfc.  Yes, that will make synchronization more difficult, and I'm sorry.

-- 
Joe Hildebrand

v2.23.0 | Report a Bug | By Email