[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ipng
Subject:    Re: IPV6_USEMTU socket option
From:       Tim Hartrick <tim () mentat ! com>
Date:       2000-11-27 18:42:46
[Download RAW message or body]



Erik,

> 
> What would you like to see instead?
> uint32_t? uint16_t?
>

uint32_t is probably best.

> 
> >    This cmsghdr will be passed to every socket that sets the
> >    IPV6_RECVPATHMTU socket option, even if the socket is
> >    non-connected. Note that this also means an application that sets
> >    the option may get the ancillary data upon a too big message sent
> >    from other applications to the same destination. An implementation
> >    may skip to deliver the data to sockets that connect a different
> >    foreign address from the destination address of the corresponding
> >    ip6_mtuinfo strucutre.
> 
> I'll add the above. THanks for the text.
> 
> > This is based on the behavior of our implementation, but I don't stick
> > to minor details (e.g. the last sentence).
> > 
> > >    XXX What about more complex paths e.g. when using a routing header?
> > 
> > How about the following text?
> > 
> >   When an application sends packet with a routing header, the final
> >   destination stored in the ip6m_addr member does not necessarily
> >   contain complete information of the entire path. Thus, an
> >   implementation may append an additional data structure after
> >   ip6_mtuinfo to tell the application precise information of the
> >   entire path. This definition of the additinaol structure is beyond
> >   the scope of this document.
> 
> I can add this unless somebody has any concerns about essentially making
> this implementation specific.
> 

I do, since I am having a difficult time understanding how an application
would make use of such information.  If it can be used by an application
then it should be documented in full or not referenced at all in the
document.

Note that I am not saying that someone can't implement anything they like.
What I am saying is that the specification is intended to document specific
features that application writers can depend on being available on all
platforms.




tim
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page:                      http://playground.sun.com/ipng
FTP archive:                      ftp://playground.sun.com/pub/ipng
Direct all administrative requests to majordomo@sunroof.eng.sun.com
--------------------------------------------------------------------

[prev in list] [next in list] [prev in thread] [next in thread]