CARD issue 7: separate appendix from the CARD protocol speciifcation

With regard to the protocol extension for dynamic maintenance
of reverse address translation info in CAR tables, as described
in the current draft's appendix, what about shortening the two
proposals for an optional backend protocol solution and to just
describe the basics in the appendix, e.g. what's added from
protocol point of view. Discussion on related security
associations, etc. could be in a separate document,
which provides more details.

Advantage of keeping an overview of the extensions in 
the core document is to get an idea about possible solutions for
backend protocol operation. Maybe this is feasible in particular
since the CARD protocol will be experimental.

In case the appendix will go into a separate document, what
about the "application scenarios" ? I think this is reasonable to
have them in the core spec. Comments?

marco 


 

-----------
was: [CARD editorial issue]: Excessive appendix size

The appendix in the CARD draft is almost as large as the draft itself. How
about performing an appendectomy :-) and separating the appendix out into a
separate draft? I think it would be easier for readers, and especially the
IESG, to process.

            jak