Re: D116 Design draft, misc. comments

Tero Kivinen <[email protected]> Thu, 5 Jan 2006 13:12:57 +0200
Newsgroups gmane.ietf.mobike
Message-ID <[email protected]>
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. 

> 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]