Re: [v6ops] new draft: draft-taylor-v6ops-fragdrop

[Andrew Yourtchenko <[e-mail]>]

On Wed, 24 Oct 2012, Merike Kaeo wrote:

>
> On Oct 23, 2012, at 1:39 AM, Lorenzo Colitti wrote:
>
>> On Mon, Oct 22, 2012 at 8:44 PM, Nick Hilliard <[e-mail]> wrote:
>> So, what do we do?  Do we:
>>
>> - ignore the problem
>> - issue generic advice
>> - name and shame
>> - other
>>
>> Other. Document that some networks drop fragments, the reasons why they do so, and the impact on applications, but provide no advice.
>
> +1
>
>> It's unlikely that this group, let alone the IETF, would agree on what advice to give (at least this decade), but I think it is the responsibility of an operations group to document real operational issues, so the rest of the community, including application developers and protocol developers, can be made aware of it.
>
> +1 on documenting known issues to make others aware

+1 on documenting, maybe worth adding to the section 2.2 a few more 
protocol case studies:

http://www.ietf.org/mail-archive/web/ipsec/current/msg07749.html
http://www.ietf.org/proceedings/71/slides/radext-4.pdf
http://support.microsoft.com/kb/244474

Alongside with that, also probably something like 
http://tools.ietf.org/html/rfc4347#section-4.2.3 could be also referenced 
as an example of application protocol's approach to fragmentation, 
alongside with 
http://tools.ietf.org/html/draft-smyslov-ipsecme-ikev2-fragmentation-00, 
http://tools.ietf.org/html/draft-perez-radext-radius-fragmentation-03,

This might help future app protocol writers' design choices, even if the 
document does not give the explicit advice (the fact on which I do not 
have an explicit opinion).

--a


>
> - merike
> _______________________________________________
> v6ops mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/v6ops
>