On Wed, Nov 11, 2020 at 06:02:28PM +0100, Carsten Bormann wrote:
> On 2020-11-11, at 17:33, Toerless Eckert <t...@cs.fau.de> wrote:
> >
> > Correct me if i am wrong, but i don't think that this would include at
> > least in recent
> > decades standards track documents, or does it ?
>
> There could be an agreement to hand over change control, which could then
> lead to a standards-track document.
RFC8017 was exactly such an example that explicitly states "hand over change
control",
but it is informational. Alas i can't figure out quickly if/what extensions or
follow-on stds. track work there may be, so we could steal that process if it
would fit.
> None of this changes that pcapng exists and there is little point creating an
> incompatible IETF version, so this would constrain the deviation we would
> want to create with our newly gained change control.
Agreed. but this is in contradiction to what others here on the thread claimed
would be in scope of changes toward RFC, such as "anything", so everybody seems
to chime in wih liking pcapng without first trying to have a clear understanding
what it is the WG should and should not do.
One problem here is that the intro text does not state the context correctly.
With words like "proposes", and "should/must" requirements it reads as if
this is up to WG work to do this. The fact that this is a 2010 protocol
specification adopted 10 years later by IETF really needs to be made clear.
> (As much as I???d like them to switch to CBOR???)
Nah. Much easier to sneak in CBOR into an existing protocol by mandating it for
future extensions of an already widely adopted protocol predating it ;-)
Kidding aside: Maybe the relevant discuss for the fdt mailing list would be
if we should have/select a formal language to describe the arbitrary binary
TLV format that we may just inherit and can not be replaced by any of the
non-arbitrary encoding options (such as CBOR). Ideally, the formal
description could automatically generate ASCII art renderings too for human
enjoyment.
Cheers
Toerless
> Grüße, Carsten
_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
