[Rift] What is being standardized in the base spec? (draft-ietf-rift-rift)

[Alvaro Retana <[e-mail]>]

Dear WG:

I have started my review of the (very long) base spec [1] [2].  Thank
you to everyone involved!


As I read through the document and ask questions, many are answered
"in the schema."  Using the schema is ok; we had already talked about
it being Normative.  However, it makes me wonder, what are we
standardizing?  Bear with me as I explain.

(a) The WG can standardize the schema itself, just like the IETF works
on, for example, YANG modules:  the module *is* the standard and the
rest of the text in the RFC represents a high-level overview and other
general things (IANA and Security Considerations, for example).  If we
go this route, we're assuming that people will extract the schema from
the document and use it (again, similar to YANG modules) -- and we're
taking advantage of thrift-specific facilities and assumptions (that
don't have to be explicitly specified).

(b) The WG can standardize a protocol specification
(rfc2328/rfc4271/ISO10589 are all examples of that).  In this case,
the body contains the specification of the protocol's expected
behavior, and the schema can aid in that definition.  For example,
instead of traditional packet formats, the schema can be used to
define the fields and some of the behavior -- it can also be used as a
"reference implementation."  If we go this route, we're
assuming/expecting that people will write non-thrift implementations
of the protocol without explicit knowledge of any thrift-specific
facilities (any such assumption would have to be explicitly
specified).


The question to the WG, for which I would like the Chairs to guide the
discussion, is: What are we standardizing?  When the WG reviewed the
document, what were the assumptions?


FWIW, I have been assuming/expecting (b).  If the WG intends (a), that
is ok -- I can change my expectations.   We need to be in alignment.

Thanks!

Alvaro.


[1] https://mailarchive.ietf.org/arch/msg/rift/yTujeIBGVuYcQMgnpTvVN_qPW9Y/

[2] https://mailarchive.ietf.org/arch/msg/rift/r_YVHdNgrwtt_0wPotml1FBHmyI/