Re: D116 Design draft, misc. comments

hi tero, 
 
> -----Ursprüngliche Nachricht-----
> Von: Tero Kivinen [mailto:[email protected]] 
> Gesendet: Donnerstag, 5. Januar 2006 12:13
> An: Tschofenig, Hannes
> Cc: [email protected]; [email protected]
> Betreff: Re: [Mobike] D116 Design draft, misc. comments
> 
> Tschofenig, Hannes writes:
> > > > - Section 5.2.1, a couple of informative references might be 
> > > >   in order (UNSAF, MIDCOM, NSIS NATFW)
> > > 
> > > Sure, give RFC / Internet-draft names, I will add them. 
> > 
> > here are the references: 
> > 
> >    [UNSAF]  Daigle, L. and IAB, "IAB Considerations for UNilateral
> >          Self-Address Fixing (UNSAF) Across Network Address
> >          Translation", RFC 3424, November 2002.
> > 
> > 
> > for midcom we could reference:
> > 
> > [RFC3303]   Srisuresh, P., Kuthan, J., Rosenberg, J., 
> Molitor, A. and A.
> >             Rayhan, "Middlebox communication architecture and
> >             framework", RFC 3303, August 2002.
> 
> Added those. 
> 
> > [MIDCOM-MIB]  Quittek, J., Stiemerling, M. and P. 
> Srisuresh, "Definitions of Managed Objects for Middlebox 
> Communication", draft-ietf-midcom-mib-05.txt (work in 
> progress), March 2005.
> 
> Is the mib here really relevant for the mobike design? I think the
> architecture and framework should be enough. I didn't add this one
> yet. 

it is ok for me to reference just the framework. i guess that everyone then already understands what is meant. 

ciao
hannes

> 
> > here is the nsis reference: 
> > 
> > [NSISNATFW]   Stiemerling, M., Tschofenig, H. and C. Aoun, 
> "A NAT/Firewall NSIS Signaling Layer Protocol (NSLP)", 
> Internet-Draft draft-ietf-nsis-nslp-natfw-08, October  2005.
> 
> Added that. 
> -- 
> [email protected]
>