Esko Dijk <[email protected]> wrote:
    > Thanks for the feedback. It looks like the draft is struggling between the
    > viewpoints of "cBRSKI is a new protocol based on BRSKI" vs "cBRSKI equals
    > BRSKI and is a variant on it".

In general, I have used and pushed others to use the
draft-kuehlewind-rswg-updates-tag stuff, even though a few had small problems
with it that kept it stagnating.
RFC9914 got through with amends/extends, although there were some bumps.

    > cBRSKI is an extension of BRSKI (without impacting existing 
implementations),
    > however the document also does provide some normative updates to 
BRSKI/8995
    > which might impact existing implementations in case they weren't doing 
these
    > things right.

    > The namings "BRSKI-EST" and "BRSKI-MASA" are used to divide all protocol
    > interactions into 2 groups. This way of dividing would conceptually hold 
for
    > cBRSKI, but also for existing BRSKI (8995).

    > An alternate way to summarize this very shortly would be like this:

    > cBRSKI = cBRSKI-EST + cBRSKI-MASA

    > BRSKI = BRSKI-EST + BRSKI-MASA

    > This is probably confusing as well, because it uses another definition for
    > these terms. The key thing I think is that "BRSKI-EST" as used now in the
    > draft is a way to say "The Pledge-to-Registrar interactions of any BRSKI 
type
    > protocol (including 8995 and cBRSKI and possible others)".

Yes.
The BRSKI-MASA side of things is being extended.
I'd have to look again if there was anything on that side that gets amended.

cBRSKI-EST is clearly extending RFC9148 by adding the new resources.
I think we are also **amending** it with draft-ietf-core-uri-path-abbrev.

    > Maybe we should call it "Pledge-to-Registrar Scope" or 
"Pledge-to-Registrar
    > Leg" or so instead of BRSKI-EST.

More words do not always help.
I think that this is pretty niche.
Search engines and LLMs seem to know what BRSKI-EST, so leave it alone.

--
Michael Richardson <[email protected]>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

**       My working hours and your working hours may be different.         **
** Please do not feel obligated to reply outside your normal working hours **

Attachment: signature.asc
Description: PGP signature

_______________________________________________
Anima mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to