Carsten Bormann <c...@tzi.org> wrote:
>> I don't think you should hide the example in the appendix.
>>
>> Rather, I think that you should make it the core of the document,
>> explaining each bit of arcana.
> That sounds like a great project for long winter evenings at the
> fireside. (Macintosh file type code(s)? Fragment identifier
> considerations?)
Yeah.
(I was cooling down in my unheated my pool last week, wondering why I can't
edit code while floating. firesides would be other nice places)
>> If it's worth publishing this as a new RFC, then it's worth obsoleting
>> RFC6838.
> It has no normative intent (*) (and it doesn’t cover a tenth of 6838).
okay, then Updates/Amends-6838, and replaces the template part then.
>> Otherwise, I suggest some nice HTML, maybe in the new-fangled
>> single-hop-over-building wiki. ("Go big, or go home")
> I think my parser is failing here.
I'm saying that if we aren't going to publish, then it goes into the new wiki.
--
Michael Richardson <mcr+i...@sandelman.ca>, Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
