Re: [calsify] Alvaro Retana's Block on charter-ietf-calext-01-00: (with BLOCK and COMMENT)

[Bron Gondwana <[e-mail]>]

On Thu, Jan 20, 2022, at 03:38, Alvaro Retana wrote:
> On January 18, 2022 at 7:01:39 PM, Bron Gondwana wrote:
> 
> 
> Bron:
> 
> Hi!
> 
> ...
> > > ----------------------------------------------------------------------
> > > BLOCK:
> > > ----------------------------------------------------------------------
> > >
> > > - publish informative documents describing existing vendor extensions
> > > which did not come through the IETF consensus process, but are
> > > nonetheless in common usage and likely to be encountered in the wild.
> > >
> > > I understand the intent, but all IETF documents require consensus
> > > (rfc8789).  Publishing a vendor extension without consensus should be
> > > done through the ISE.
> >
> > The idea is to publish as informative - with consensus that this matches
> > what IETF members have seen in the wild. Even if they wound up published
> > via ISE, the working group would work with them, since we have to work
> > around them because that's what's actually out there.
> 
> I understand.
> 
> I don't think is correct to hint at publishing IETF stream documents
> without consensus -- even if that is not the intent.  Perhaps the
> bullet could be updated to something like this:
> 
>    - publish documents describing existing vendor extensions that are
>      in common usage...
> 
> 
> Does that work?

Yes, I'm happy with that.  I'll update the text at https://notes.ietf.org/calext-proposed-charter-2021

Cheers,

Bron.

--
  Bron Gondwana, CEO, Fastmail Pty Ltd
  [e-mail]