-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/30/2011 11:56 AM, Bruce Lowekamp wrote:
> Marc,
> 
> How about:
> 
> Each
> fragment MUST contain a full copy of the via list, destination list,
> and ForwardingOptions and
> MUST contain at least 256 bytes of the message body. If these elements
> cannot fit within the MTU of the underlying datagram protocol, RELOAD
> fragmentation is not performed and IP-layer fragmentation is allowed
> to occur.
> 
> ?

Your text is unambiguous, so it's fine for me.

> 
> Bruce
> 
> 
> On Mon, Sep 19, 2011 at 4:58 PM, Marc Petit-Huguenin <[email protected]> wrote:
> In section 5.7:
> 
> "Each fragment MUST contain a full copy of the via and
>  destination list and MUST contain at least 256 bytes of the message
>  body.  If the via and destination list are so large that this is not
>  possible, RELOAD fragmentation is not performed and IP-layer
>  fragmentation is allowed to occur."
> 
> I think that the text should say this instead:
> 
> "Each fragment MUST contain a full copy of the via list,
>  destination list and options and MUST contain at least 256 bytes of
>  the message body.  If the via list, destination list and options are
>  so large that this is not possible, RELOAD fragmentation is not
>  performed and IP-layer fragmentation is allowed to occur."
> 

- -- 
Marc Petit-Huguenin
Personal email: [email protected]
Professional email: [email protected]
Blog: http://blog.marc.petit-huguenin.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk6tdaIACgkQ9RoMZyVa61f3AACcCmIT3UXc7y6Pm0aAky+Z33kB
IPQAnAleHO39flwU4GQoSVWHJ0Eta/C6
=cHmt
-----END PGP SIGNATURE-----
_______________________________________________
P2PSIP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/p2psip

Reply via email to