IETF Logo Mail Archive

Re: [v6ops] RFC6459 "IPv6 in 3GPP" - TE/MS split mode?

<mohamed.boucadair@orange.com> Thu, 13 July 2017 11:33 UTC

Return-Path: <mohamed.boucadair@orange.com>
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 1B6B2126D73 for <v6ops@ietfa.amsl.com>; Thu, 13 Jul 2017 04:33:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.619
X-Spam-Level:
X-Spam-Status: No, score=-1.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MKUTKzL5sO0Z for <v6ops@ietfa.amsl.com>; Thu, 13 Jul 2017 04:33:01 -0700 (PDT)
Received: from relais-inet.orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3960F12ECCB for <v6ops@ietf.org>; Thu, 13 Jul 2017 04:32:59 -0700 (PDT)
Received: from opfednr03.francetelecom.fr (unknown [xx.xx.xx.67]) by opfednr27.francetelecom.fr (ESMTP service) with ESMTP id C9DECA04B6; Thu, 13 Jul 2017 13:32:57 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.43]) by opfednr03.francetelecom.fr (ESMTP service) with ESMTP id 9FE071A008F; Thu, 13 Jul 2017 13:32:57 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM5F.corporate.adroot.infra.ftgroup ([fe80::e172:f13e:8be6:71cc%18]) with mapi id 14.03.0352.000; Thu, 13 Jul 2017 13:32:57 +0200
From: mohamed.boucadair@orange.com
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, 神明達哉 <jinmei@wide.ad.jp>
CC: "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] RFC6459 "IPv6 in 3GPP" - TE/MS split mode?
Thread-Index: AQHS+7x70awen34woU+GrnWOaIskkaJRn2aQ
Date: Thu, 13 Jul 2017 11:32:56 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93300A006E6D@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <937f22f6-e4b7-b398-9df9-79c36ea2d7ee@gmail.com> <787AE7BB302AE849A7480A190F8B93300A002E21@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <a67eb7d0-be6a-f158-b05c-fda0f38e09d6@gmail.com> <787AE7BB302AE849A7480A190F8B93300A002EF9@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <1be23f5b-f449-9924-8322-f21c4ccbd09e@gmail.com> <787AE7BB302AE849A7480A190F8B93300A002F95@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <2c325097-651e-501c-747a-e7a322c3d844@gmail.com> <787AE7BB302AE849A7480A190F8B93300A0032B6@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <6c43cf08-0bd6-daf4-ea9d-d52c34db2a8c@gmail.com> <CAJE_bqem6dKVcANbVgQLbny2ks5jvVNELRqwPECM_TiJtOtxcg@mail.gmail.com> <00d03635-4b5d-f4df-d3c2-1e7d69653bc9@gmail.com> <CAJE_bqf7wSQ5ZLtPR-XTALStnFcu7wnHmfSXGQ1PL=q=vpYtpg@mail.gmail.com> <787AE7BB302AE849A7480A190F8B93300A0044C9@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <7efc2597-ad20-d15b-ccc1-b7fd0d97b68b@gmail.com>
In-Reply-To: <7efc2597-ad20-d15b-ccc1-b7fd0d97b68b@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.5]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/mQ9XkpUkGc8uBtgUPG17dY0b7A8>
Subject: Re: [v6ops] RFC6459 "IPv6 in 3GPP" - TE/MS split mode?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 13 Jul 2017 11:33:02 -0000

Re-,

I meant TE/MT. 

I can direct you to 3GPP specs, but the key point is nicely summarized here: 
https://tools.ietf.org/html/rfc7066#section-2.4 

Cheers,
Med

> -----Message d'origine-----
> De : Alexandre Petrescu [mailto:alexandre.petrescu@gmail.com]
> Envoyé : jeudi 13 juillet 2017 11:43
> À : BOUCADAIR Mohamed IMT/OLN; 神明達哉
> Cc : v6ops@ietf.org
> Objet : Re: [v6ops] RFC6459 "IPv6 in 3GPP" - TE/MS split mode?
> 
> What is a TE/MS split mode?
> 
> Alex
> 
> Le 13/07/2017 à 07:17, mohamed.boucadair@orange.com a écrit :
> > Dear Jinmei,
> >
> > I fully agree that there is no point to discuss a broken implementation.
> >
> > Alex seems to use a TE/MS split mode. So the addresses he is seeing are
> not coming from the network.
> >
> > Cheers,
> > Med
> >
> >> -----Message d'origine-----
> >> De : v6ops [mailto:v6ops-bounces@ietf.org] De la part de ????
> >> Envoyé : mercredi 12 juillet 2017 18:54
> >> À : Alexandre Petrescu
> >> Cc : v6ops@ietf.org
> >> Objet : Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in the LL address
> and
> >> GUA
> >>
> >> At Wed, 12 Jul 2017 17:15:52 +0200,
> >> Alexandre Petrescu <alexandre.petrescu@gmail.com> wrote:
> >>
> >>>> If you really see an RA with a non-LL source address, a textual
> >>>> snippet of the packet dump will certainly be interesting.
> >>>
> >>> A textual snippet may include addresses that are considered private.
> >>> But I will send you privately the snippet.
> >>
> >> You could mask the sensitive part of it, but, anyway, I actually see
> >> RAs sent from a global address.  I don't know why it behaves that way,
> >> but it's no secret that there are broken implementations so it's not
> >> surprising.  Since the implementation is this broken I don't see any
> >> point in discussing this particular case here - that is, no one here
> >> will be able to answer why a broken implementation is broken or why an
> >> operator uses that broken implementation.  You'll just need to talk to
> >> that operator.
> >>
> >> --
> >> JINMEI, Tatuya
> >>
> >> _______________________________________________
> >> v6ops mailing list
> >> v6ops@ietf.org
> >> https://www.ietf.org/mailman/listinfo/v6ops

v2.23.0 | Report a Bug | By Email