[rfc-i] [IAB] draft-iab-xml2rfc-03, "2.19 <displayreference> "

tony at att.com (HANSEN, TONY L) Wed, 02 March 2016 17:00 UTC

From: tony at att.com (HANSEN, TONY L)
Date: Wed, 2 Mar 2016 17:00:33 +0000
Subject: [rfc-i] [IAB] draft-iab-xml2rfc-03, "2.19 <displayreference> "
In-Reply-To: <56D71133.2070104@gmx.de>
References: <56D607FC.4070903@gmx.de> <40F98072-B8FE-48D7-A506-946558ACB9D6@cisco.com> <56D688F7.5060508@gmx.de> <7F5B319D-106C-4928-8B48-88F9D3A3CF99@cisco.com> <EED7D730-19DD-4A4B-BAAA-B43C9706CB0B@vpnc.org> <56D71133.2070104@gmx.de>
Message-ID: <4AA4D342-0DDE-4E28-8B72-D9C910F5FCCA@att.com>

On 3/2/16, 11:13 AM, "rfc-interest on behalf of Julian Reschke" <rfc-interest-bounces at rfc-editor.org on behalf of julian.reschke at gmx.de> wrote:


>On 2016-03-02 17:05, Paul Hoffman wrote:
>>
>> I'm fine with the idea that the prep tool will remove <displayreference>
>> from the prepped XML if we can do so.
>
>How is it supposed to do that when to="3GBLA"?

Perhaps Paul meant "when possible". Names that do not match the syntax of an identifier (e.g. 3GBLA or 3GPP) are obvious times when it's not possible.

And 3GPP, which is an existing problem.

	Tony