Re: [v6ops] new draft: draft-ietf-v6ops-6204bis

Tassos Chatzithomaoglou <achatz@forthnetgroup.gr> Wed, 19 October 2011 08:53 UTC

Return-Path: <achatz@forthnetgroup.gr>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3ADA21F8BA6 for <v6ops@ietfa.amsl.com>; Wed, 19 Oct 2011 01:53:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.342
X-Spam-Level:
X-Spam-Status: No, score=-2.342 tagged_above=-999 required=5 tests=[AWL=0.257, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rYIP9rmjN+Z5 for <v6ops@ietfa.amsl.com>; Wed, 19 Oct 2011 01:53:36 -0700 (PDT)
Received: from mx-out.forthnet.gr (mx-out.forthnet.gr [193.92.150.115]) by ietfa.amsl.com (Postfix) with ESMTP id A3CA421F8BA0 for <v6ops@ietf.org>; Wed, 19 Oct 2011 01:53:35 -0700 (PDT)
Received: from mx-av-03.forthnet.gr (mx-av.forthnet.gr [193.92.150.27]) by mx-out-01.forthnet.gr (8.14.4/8.14.4) with ESMTP id p9J8rXRK027743; Wed, 19 Oct 2011 11:53:33 +0300
Received: from MX-IN-02.forthnet.gr (mx-in-02.forthnet.gr [193.92.150.185]) by mx-av-03.forthnet.gr (8.14.3/8.14.3) with ESMTP id p9J8rXJn030933; Wed, 19 Oct 2011 11:53:33 +0300
Received: from [192.168.1.2] (194.219.107.119.dsl.dyn.forthnet.gr [194.219.107.119]) (authenticated bits=0) by MX-IN-02.forthnet.gr (8.14.4/8.14.4) with ESMTP id p9J8rLNP001680; Wed, 19 Oct 2011 11:53:22 +0300
Authentication-Results: MX-IN-02.forthnet.gr smtp.mail=achatz@forthnetgroup.gr; auth=pass (PLAIN)
Message-ID: <4E9E8FFF.4070703@forthnetgroup.gr>
Date: Wed, 19 Oct 2011 11:53:19 +0300
From: Tassos Chatzithomaoglou <achatz@forthnetgroup.gr>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110928 Firefox/7.0.1 SeaMonkey/2.4.1
MIME-Version: 1.0
To: Ole Troan <ot@cisco.com>
References: <4E974F1A.2030008@forthnetgroup.gr><5B6B2B64C9FE2A489045EEEADDAFF2C3030A4156@XMB-RCD-109.cisco.com><5B6B2B64C9FE2A489045EEEADDAFF2C303130390@XMB-RCD-109.cisco.com><4E98CCB2.2050100@forthnetgroup.gr><5B6B2B64C9FE2A489045EEEADDAFF2C3031303D8@XMB-RCD-109.cisco.com><4E994515.6020204@forthnetgroup.gr> <5B6B2B64C9FE2A489045EEEADDAFF2C303130B54@XMB-RCD-109.cisco.com> <5B6B2B64C9FE2A489045EEEADDAFF2C303130C12@XMB-RCD-109.cisco.com> <4E9E8706.6050006@forthnetgroup.gr> <900AA617-6DE5-4792-A706-5D62EFC4CEF8@cisco.com>
In-Reply-To: <900AA617-6DE5-4792-A706-5D62EFC4CEF8@cisco.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: v6ops@ietf.org, draft-ietf-v6ops-6204bis@tools.ietf.org
Subject: Re: [v6ops] new draft: draft-ietf-v6ops-6204bis
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2011 08:53:36 -0000

Ole,

Ole Troan wrote on 19/10/2011 11:19:
> Tassos,
>
>> Do you think it would be possible to add something about the MTU under "4.3.  LAN-Side Configuration"?
>>
>> L-15: The IPv6 CE router SHOULD by default include the LAN MTU into its Router Advertisements.
>>       The activation of this behavior MAY be user-configurable. The LAN MTU SHOULD also be user-configurable.
>>
>> There had been a similar talk 1 month ago, but i would like to see a recommended approach included.
> should the MTU be different than the default LAN link MTU and if so why?
It could be, in order to avoid PTB (packet too big) messages from the CE to the hosts for 
WAN communication (1500=>PTB=>1492=>ok).

> should internal to the home communication also be restricted in MTU?
That might by already restricted by the default LAN MTU.
I don't want that to be restricted, that's why the LAN MTU should be user-configurable.
> if the MTU is set e.g. equal to the WAN MTU, what do you do in the case of a routed home? how do you propagate the MTU inside the network?
> what if there are conflicts?
Although, a routed home might not be a typical subscriber's home, i would expect to have 
routed components handle this by their own.
I'm not asking for LAN MTU to be equal to WAN MTU specifically. I'm asking of advertising 
a MTU to the hosts, in order to avoid PTB messages, in case of WAN communication.
I'm also asking to be able to able to disable this, in order to have the hosts decide by 
their own.
> unless you have good answers to these questions, I suggest we don't.
>
> cheers,
> Ole
Generally, i would like to have available as many options as possible, in order to cover 
most scenarios.
If you want to have 1492 everywhere in order to lower the fragmentation possibilities, 
then you should have this option.
If you want to have 1500 or 9000, knowing that you might need to do fragmentation, then 
you should also have these options.

I don't know how many IPv6 CPEs support (or will support) >1500 MTU on their LAN 
interfaces, but judging from the ones i have tried, none of them did (maybe it's because 
of their FE interfaces). In that case, i don't believe using a 1492 MTU vs a 1500 one will 
make a big difference for internal home communication.


Regards,
Tassos