Re: [v6ops] draft-binet-v6ops-cellular-host-requirements-00.txt

<> Mon, 19 November 2012 10:30 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C0E5621F8564 for <>; Mon, 19 Nov 2012 02:30:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.822
X-Spam-Status: No, score=-1.822 tagged_above=-999 required=5 tests=[AWL=0.425, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, UNPARSEABLE_RELAY=0.001]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id q8rVh6OeWKM5 for <>; Mon, 19 Nov 2012 02:30:50 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 6757821F849E for <>; Mon, 19 Nov 2012 02:30:49 -0800 (PST)
Received: from (unknown [xx.xx.xx.1]) by (ESMTP service) with ESMTP id 1F9C018C3F4; Mon, 19 Nov 2012 11:30:49 +0100 (CET)
Received: from (unknown []) by (ESMTP service) with ESMTP id D9BDD35C058; Mon, 19 Nov 2012 11:30:48 +0100 (CET)
Received: from ([]) by ([]) with mapi; Mon, 19 Nov 2012 11:30:46 +0100
From: <>
To: Lorenzo Colitti <>
Date: Mon, 19 Nov 2012 11:30:45 +0100
Thread-Topic: [v6ops] draft-binet-v6ops-cellular-host-requirements-00.txt
Thread-Index: Ac3GPSYjHiUrcAQjTxuv+kW78tjtGgAArGOA
Message-ID: <>
References: <> <> <> <>
In-Reply-To: <>
Accept-Language: fr-FR
Content-Language: fr-FR
acceptlanguage: fr-FR
Content-Type: multipart/alternative; boundary="_000_1B2E7539FECD9048B261B791B1B24A7C3EF5B56FF4PUEXCB1Anante_"
MIME-Version: 1.0
X-PMX-Version:, Antispam-Engine:, Antispam-Data: 2012.11.19.100316
Cc: IPv6 Ops WG <>
Subject: Re: [v6ops] draft-binet-v6ops-cellular-host-requirements-00.txt
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 19 Nov 2012 10:30:51 -0000

De : Lorenzo Colitti []
Envoyé : lundi 19 novembre 2012 11:03
Objet : Re: [v6ops] draft-binet-v6ops-cellular-host-requirements-00.txt

On Mon, Nov 19, 2012 at 6:57 PM, <<>> wrote:
And I do not understand the comment about the need to remove some requirements and to provide a link to RFC3316bis document. I do not understand why a RFCbis draft was proposed if the specifications were already present in draft-binet-* document.
Because that draft properly updates RFC3316. This document does not update RFC3316, it's something completely different.
[[david]] You are right. It is different and the goal is to get a document where we can have all IPv6 specifications.
Besides, I do not have the feeling that there was some demand for a RFC3316 update whereas there was some support for a document providing an IPv6 profile, as proposed in draft-binet-.
Second, most of this document attempts to standardize feature sets, not protocols or interoperability. I'm not sure this is is in scope for the IETF, and even more so for an operations group inside the IETF.
[[david]] It is your opinion but as operator, it is something which is very important and there is a lack in standardisation documents where some IPv6 profile is defined. We receive a lot of support about such specifications.
Does the IETF define an IPv4 profile? If not, why not?
[[david]] As an operator, I would say such document would not be required if we had IPv6 terminals. But it is not the case and we need to get such reference even if it is not our only action to get such devices.
Does the IETF define an IPv6 profile for CPE ? Yes. Now, there is RFC6204.


Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
Thank you.