Hi - > From: "Simon Josefsson" <simon@xxxxxxxxxxxxx> > To: "Joel M. Halpern" <joel@xxxxxxxxxxxxxxxx> > Cc: <steven.legg@xxxxxxxxxxx>; <ietf@xxxxxxxx> > Sent: Saturday, January 13, 2007 12:38 PM > Subject: Re: Last Call: draft-legg-xed-asd (Abstract Syntax Notation X(ASN.X)) to Proposed Standard ... > > Firstly, it is clear that you (and every other implementor using this > > document) needs the ability to extract and use the ASN.1 include in > > the document. That is already provided for in BCP 78. The text he > > included is exactly the text that BCP 78 tells him to include to do > > that. So there is no problem there. > > I explained in my note that BCP 78 does _not_ provide for that. If > you disagree with that, I think you need to show where BCP 78 gives > third parties the right to extract and use the ASN.1 module. ... Section 5.2 of RFC 3978 addresses the issue, giving the necessary incantation and using MIBs and PIBs as an example. There's nothing about an ASN.1 module in this regard that's any different from PIBs and MIBs. Randy _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf