Re: [Crisp] Questions re adoption and future of IRIS protocol and IRIS dependent services
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Crisp] Questions re adoption and future of IRIS protocol and IRIS dependent services
Carl,
> COMMERCIAL IMPLEMENTATIONS: Marcos Sanz reports that DENIC will make
> available
For the records this will be no "commercial" implementation. You can call
it "closed" implementation, if you want.
> 3) Marcos and Sven-Holger, could you please make more explicit the
complete
> list of IRIS related RFC standards that your companies will be
supporting
> with products or services?
As I said, this is a DCHK implementation (RFC number not known yet) over
LWZ transport (RFC 4993).
> This inquiry regards solely the status of RFC 3982 and the fact that the
> formal XML syntax for dreg1 does not validate. Specifically, XML
validation
> checkers return errors that map to lines beginning with the element
> 'dreg:endsWith'.
RFC errata is to be reported as follows:
http://www.rfc-editor.org/how_to_report.html
Andy or I will gladly verify any errors in the schemata.
> (1) For active members of the CRISP WG, what is the current
recommendation
> for use of a corrected revision for dreg?
Implement RFC 3982 plus verified errata.
Best regards,
Marcos
_______________________________________________
Crisp mailing list
Crisp at ietf.org
https://www1.ietf.org/mailman/listinfo/crisp
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.