Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)



>>>>> "Robert" == Robert Sayre <sayrer at gmail.com> writes:

    Robert> It's not obvious to me why we would to change the concrete
    Robert> definition of interoperability in RFC2026 to an

I don't think anyone is proposing changing the definition: For the
purposes of this section, "interoperable" means to be functionally
equivalent or interchangeable components of the system or process in i
which they are used.


I think we are discussing consequences of that definition that are
non-obvious.  RFC 2026 requires that two interoperable implementations
exist.  However I believe that there is a strong IETF consensus that
our specs need to support universal interoperability.


_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf




Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.