RE: : Re: authors 48 hours: RFC 4005 <draft-ietf-aaa-dia meter-nasreq-17.txt>

W.r.t.
> > Informative References (section 13.2, page 79) <Add after
> > [DiamMIP]>
> > 
> > [VSAdraft] D. Mitton "Diameter/RADIUS Vendor Specific AVP
> > Translation", draft-mitton-diameter-radius-vsas-00.txt, "Work in
> > Progress", April 2005  
> 
> I'm not sure how moving this to an external draft helps anything --
> it's my understanding that an RFC cannot reference an I-D, even
> informatively.  Is that incorrect?
> 

An informative reference CAN BE to a I-D (draft) and the doc will not
be held up by that. The question is if it indeed IS informative. That
is: can an implementer understand/implement with out reading the 
VSADraft? I think an implementer indeed can implement, so it seems
that Informative is fine.

Hope this helps,
Bert