From nobody Thu May 1 04:24:52 2014 Return-Path: X-Original-To: its@ietfa.amsl.com Delivered-To: its@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD6FE1A88E8 for ; Thu, 1 May 2014 04:24:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.717 X-Spam-Level: X-Spam-Status: No, score=0.717 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, GB_I_LETTER=-2, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=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 7Csz4BPvu8wO for ; Thu, 1 May 2014 04:24:12 -0700 (PDT) Received: from smtp4-g21.free.fr (smtp4-g21.free.fr [212.27.42.4]) by ietfa.amsl.com (Postfix) with ESMTP id BC4DA1A88F9 for ; Thu, 1 May 2014 04:24:10 -0700 (PDT) Received: from [127.0.0.1] (unknown [82.239.213.32]) by smtp4-g21.free.fr (Postfix) with ESMTP id 2004E4C809F; Thu, 1 May 2014 13:23:28 +0200 (CEST) Message-ID: <53622ED2.7080605@gmail.com> Date: Thu, 01 May 2014 13:24:02 +0200 From: Alexandru Petrescu User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "its@ietf.org" References: <2ED1D3801ACAAB459FDB4EAC9EAD090C0FFFE9E2@xmb-aln-x03.cisco.com> <51064E08.9020401@gmail.com> <5106619F.7020002@inria.fr> <51067D07.9020409@gmail.com> <5108E3AB.8080205@inria.fr> <5108EA48.90003@gmail.com> <5108EDAA.90700@gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA07A4E4@AZ-FFEXMB04.global.avaya.com> <5267EAFC.9090607@gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA1291358F@AZ-FFEXMB04.global.avaya.com> In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA1291358F@AZ-FFEXMB04.global.avaya.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Antivirus: avast! (VPS 140430-2, 30/04/2014), Outbound message X-Antivirus-Status: Clean Archived-At: http://mailarchive.ietf.org/arch/msg/its/GdP7m_fFA2qB7ur4qZOxvZVj3Z4 Cc: "Romascanu, Dan \(Dan\)" Subject: [geonet/its] EtherType for geonet/ITS 0x8947 reflected at IANA (was: What do we need to make ITS WG go forward? - EtherType for ITS) X-BeenThere: its@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "GeoNet BoF discussion list." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2014 11:24:15 -0000 Hello geonetters, I would like to inform you that, following our discussions about EtherType for geonet, and per my request, and per designated reviewer for this entry - IANA has added an entry in the table of EtherTypes for 0x8947 for GeoNetworking, as to reflect the IEEE allocation of same EtherType. http://www.iana.org/assignments/ieee-802-numbers This is a good allocation which should help software designers in writing interoperable implementations of geonetworking code over link layers of type Ethernet, and in some cases, links dedicated to ITS vehicular communications. Yours, Alex On 23/10/2013 17:41, Romascanu, Dan (Dan) wrote: > Hi Alexandru, > > The authority for allocation is with the IEEE, and the list to be > referenced and used in specifications is the one at IEEE. > > The IANA list is informational and includes as specified on the page > 'contributed unverified information from various sources'. It would > be good I think to have the new ethertype mentioned on the IANA page > as well, because some IETF-ers may go first to that list. I suggest > that you just send an email to IANA asking for the change (additional > row in the table) be made according to the IEEE allocation. We can > talk about this with the IANA folks in Vancouver if this is not > solved until then. > > I am not sure who needs to be asked about the linux kernel patches, I > can guess that a query to the apps-discuss@ietf.org may result on > useful information from people involved with that layer. > > I hope this helps. > > Regards, > > Dan > > > >> -----Original Message----- From: Alexandru Petrescu >> [mailto:alexandru.petrescu@gmail.com] Sent: Wednesday, October 23, >> 2013 6:28 PM To: Romascanu, Dan (Dan); its@ietf.org Subject: Re: >> [its] What do we need to make ITS WG go forward? - EtherType for >> ITS >> >> Hi Dan, >> >> Let me bring back this topic. >> >> Since our last discussion the EtherType for ETSI GeoNetworking >> 0x8947 has been set at IEEE: >> http://standards.ieee.org/develop/regauth/ethertype/eth.txt >> >> However, it is absent at the IANA website: >> http://www.iana.org/assignments/ieee-802-numbers/ieee-802-numbers.xml >> >> >> Where should we ask at IANA about this type? >> >> Also, this ethertype 0x8947 seems absent from the linux kernel >> sources. >> >> Where should we ask a patch? >> >> Alex >> >> >> Le 30/01/2013 11:00, Romascanu, Dan (Dan) a écrit : >>> Hi, >>> >>> If the PDF letter is dated 1/29 (yesterday) than we may see the >>> IEEE RA list updated soon. >>> >>> There is no need for IANA to make an allocation (if we are >>> discussing EtherTypes). The responsibility for EtherTypes >>> assignment is with the IEEE RA and the file at IANA is only >>> informational. See the note at >>> http://www.iana.org/assignments/ieee-802-numbers/ieee-802-numbers.xml. >>> >>> >>> >> >>> Regards, >>> >>> Dan >>> >>> >>> >>> >>>> -----Original Message----- From: its-bounces@ietf.org >>>> [mailto:its-bounces@ietf.org] On Behalf Of Alexandru Petrescu >>>> Sent: Wednesday, January 30, 2013 11:54 AM To: its@ietf.org >>>> Subject: Re: [its] What do we need to make ITS WG go forward? >>>> - EtherType for ITS >>>> >>>> In private I got hold of a pdf letter from IEEE to ETSI dated >>>> January 29th, 2013, which says that the EtherType is #8947. >>>> (not sure hexa or decimal). >>>> >>>> See that letter attached to this email. >>>> >>>> One would say that things unfold as we speak. >>>> >>>> I still think that IANA should also allocate it as well. (maybe >>>> I'll get another pdf in private telling me it's already >>>> done...) >>>> >>>> Alex >>>> >>>> Le 30/01/2013 10:39, Alexandru Petrescu a écrit : >>>>> Le 30/01/2013 10:11, Thierry Ernst a écrit : >>>>>> >>>>>> Alex, >>>>>> >>>>>> IEEE have assigned Ethernet Type Field number #8947 for ITS >>>>>> use (ETSI TC ITS's GeoNetworking). Check the following >>>>>> document available on the ETSI server: >>>>>> >>>>>> ITS(13)000020 >>>>>> >>>>> >>>>>> 00 >>>>>> >>>>>> >>>>>> >> 20_Ethernet_Type_Field_number_for_GeoNetworking.pdf> >>>>>> >>>>>> >>>>>> Ethernet Type Field number for GeoNetworking >>>>>> http://docbox.etsi.org/ITS/ITS/05-CONTRIBUTIONS/2013/ITS(13)000020_ >>>>>> >>>>>> Et >>>>>> >>>>>> >>>>>> >> hernet_Type_Field_number_for_GeoNetworking.pdf >>>>>> >>>>>> >>>>> >>>>> Thierry, >>>>> >>>>> I >>>>>> >>>>> may be wrong, but here are my thoughts. >>>>> >>>>> I am trying to access these URLs you provide above but they >>>>> are password protected. What is the username and password? >>>>> >>>>> The URL indicates ETSI, not IEEE. >>>>> >>>>> The IEEE URL for EtherTypes is the following, I believe: >>>>> http://standards.ieee.org/develop/regauth/ethertype/eth.txt >>>>> >>>>> That eth.txt file does not contain 0707 nor 8947. But it >>>>> does contain, for example 86DD which is 'IPv6'. >>>>> >>>>> The 0x0707 EtherType is present in an implementation which >>>>> is supposed compliant with ETSI ITS (plugtests). Wireshark >>>>> dump available upon request. >>>>> >>>>> Besides, if this is to be about IPv6, I think it should be >>>>> reserved at IANA as well, in addition to reserving it at >>>>> IEEE. The IANA URL for IEEE 802 Numbers is at: >>>>> http://www.iana.org/assignments/ieee-802-numbers/ieee-802-numbers.xm >>>>> >>>>> l >>>>> >>>>> >>>>> >>>>> >> (the #8947 that you mention above does not seem to figure in this >>>>> IANA URL). >>>>> >>>>> This is why I believe this number should be reserved both as >>>>> an EtherType at IEEE and at IANA. >>>>> >>>>> Yours, >>>>> >>>>> Alex >>>>> >>>>>> >>>>>> Regards, Thierry. >>>>>> >>>>>> >>>>>> On 28/01/13 14:28, Alexandru Petrescu wrote: >>>>>>> Le 28/01/2013 14:16, Joe Klein a écrit : >>>>>>>> I really dislike the fact that ISO is charging for the >>>>>>>> ISO 21217 - Architecture & ISO 21210 - IPv6 >>>>>>>> Networking. >>>>>>>> >>>>>>>> Does this make it any better? Safer? Should ISO now >>>>>>>> have cybersecurity and safety liability if the >>>>>>>> specification leads to deaths and damage to property? >>>>>>> >>>>>>> Does it make any better interoperable as well? >>>>>>> >>>>>>> EtherType 0x0707 described in ITS documents, implemented, >>>>>>> but not specified by IEEE nor reserved at IANA - does not >>>>>>> make it interoperable. >>>>>>> >>>>>>> One wouldn't think that this 0x0707 ethertype be reserved >>>>>>> by somebody who is not IANA nor IEEE? >>>>>>> >>>>>>> (see a good example of interoperability: IPv6 0x86dd >>>>>>> ethertype is reserved at IEEE and at IANA >>>>>>> http://www.iana.org/assignments/ieee-802-numbers/ieee-802-numbers. >>>>>>> >>>>>>> xm >>>>>>> >>>>>>> >>>>>>> >> l) >>>>>>> >>>>>>> >>>>>>> >>>>> >>>>>>> >>>> Alex >>>>>>> >>>>>>> Or should these standards remain in >>>>>>>> the public domain, for researches to review and >>>>>>>> validate? >>>>>>>> >>>>>>>> Just my 2 cents. >>>>>>>> >>>>>>>> Joe >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Jan 28, 2013 at 6:31 AM, Thierry Ernst >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> Dear all, >>>>>>>>> >>>>>>>>> At this stage, I don't think a new working group is >>>>>>>>> needed. First, it would need a charter, and support >>>>>>>>> from the industry. But more importantly, IETF WGs are >>>>>>>>> not usually sector-driven, so it means the different >>>>>>>>> issues pertaining to ITS should be brought to VARIOUS >>>>>>>>> existing WGs, and a WG should only be created if >>>>>>>>> there is an important issue for which there is no >>>>>>>>> existing WG that could work on it. >>>>>>>>> >>>>>>>>> This said, as mentioned earlier, ITS is not only >>>>>>>>> about vehicular communications, though the issues >>>>>>>>> listed by Alexandru below mostly consider vehicular >>>>>>>>> communications. >>>>>>>>> >>>>>>>>> What ITS really needs is the definition of a common >>>>>>>>> communication architecture and the definition of what >>>>>>>>> features should be comprised for an IPv6 networking >>>>>>>>> stack deployed for ITS use cases. This cannot be done >>>>>>>>> at IETF, and actually already exists at ISO: - ISO >>>>>>>>> 21217 - Architecture - ISO 21210 - IPv6 Networking >>>>>>>>> >>>>>>>>> As an input to the discussion, please consider >>>>>>>>> reading documents D2.1 and D2.2 available on the >>>>>>>>> ITSSv6 project web page: >>>>>>>>> http://www.itssv6.eu/documentation/ D2.2 provides an >>>>>>>>> analysis of the currently published version of ISO >>>>>>>>> 21210, but new work items have been launched since >>>>>>>>> then to address remaining issues. >>>>>>>>> >>>>>>>>> Regards, Thierry. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On 28/01/13 11:08, Alexandru Petrescu wrote: >>>>>>>>>> >>>>>>>>>> Le 28/01/2013 05:02, Stan Ratliff (sratliff) a >>>>>>>>>> écrit : >>>>>>>>>>> >>>>>>>>>>> All, >>>>>>>>>>> >>>>>>>>>>> This is just one opinion, but I'd like to >>>>>>>>>>> understand why ITS would need its own IETF group. >>>>>>>>>>> The work here is the same (IMO) as what is taking >>>>>>>>>>> place in MANET. I would vote that this work be >>>>>>>>>>> taken up in MANET. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Stan, >>>>>>>>>> >>>>>>>>>> Thank you for the offer. I considered this offer >>>>>>>>>> since some time. >>>>>>>>>> >>>>>>>>>> I try to understand whether some of these items on >>>>>>>>>> which I have interest could be brought in in MANET >>>>>>>>>> WG: - V2V using prefix exchange - VIN-based IP >>>>>>>>>> addressing scheme - ND Prefix Delegation - >>>>>>>>>> PMIP-based network mobility - IPv6 single-address >>>>>>>>>> connecion 'sharing' with a cellular operator and a >>>>>>>>>> vehicular moving network (type '64share' of >>>>>>>>>> v6ops). - Default Route with DHCPv6. >>>>>>>>>> >>>>>>>>>> Please let me know. >>>>>>>>>> >>>>>>>>>> Yours, >>>>>>>>>> >>>>>>>>>> Alex >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Regards, Stan >>>>>>>>>>> >>>>>>>>>>> On Jan 26, 2013, at 9:34 AM, Abdussalam Baryun >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi Nabil, >>>>>>>>>>>> >>>>>>>>>>>> I think we already done some steps but not sure >>>>>>>>>>>> how far now. We will need to propose the WG and >>>>>>>>>>>> provide the WG charter, as use cases and work >>>>>>>>>>>> to be done in this group. This charter needs to >>>>>>>>>>>> be approved by the IESG. I have not attended >>>>>>>>>>>> the last meeting so not sure about the status >>>>>>>>>>>> now, >>>>>>>>>>>> >>>>>>>>>>>> AB >>>>>>>>>>>> >>>>>>>>>>>> On 1/26/13, Nabil Benamar >>>>>>>>>>>> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> Hi All, >>>>>>>>>>>>> >>>>>>>>>>>>> I'm still interested in this list and want to >>>>>>>>>>>>> join voices previously heard to make it a >>>>>>>>>>>>> working group. So what should we exactly do, >>>>>>>>>>>>> to achieve this goal ? >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> 2013/1/26 Abdussalam Baryun >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>> Hi All, >>>>>>>>>>>>>> >>>>>>>>>>>>>> I was interested in this group but not sure >>>>>>>>>>>>>> where are we so far. Is there progress, or >>>>>>>>>>>>>> is there issues/efforts that need to be >>>>>>>>>>>>>> completed and volunteered. >>>>>>>>>>>>>> >>>>>>>>>>>>>> AB >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >> >>>>>>>>>>>>>> its mailing list its@ietf.org >>>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- * * *تحياتي ، **Cordialement, Regards* * * >>>>>>>>>>>>> * * *نبيل بنعمرو Nabil Benamar* Professor of >>>>>>>>>>>>> computer sciences Simulation and Modelisation >>>>>>>>>>>>> Laboratory Human Sciences Faculty of Meknes >>>>>>>>>>>>> Moulay Ismail* *University* Meknes, Morocco >>>>>>>>>>>>> *GSM: * *+ 212 6 70832236 >>>>>>>>>>>>> http://nabilbenamar.com/ >>>>>>>>>>>>> >>>>>>>>>>>>> * >>>>>>>>>>>>> >>>>>>>>>>>>> ------------------------------------------------------------ >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >> ------------------ >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>> >>>>>>> * >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> >>>>>>>>>>>> its mailing list its@ietf.org >>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> its mailing list its@ietf.org >>>>>>>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> its mailing list its@ietf.org >>>>>>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ its >>>>>>>>> mailing list its@ietf.org >>>>>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>>>>> >>>>>>>> _______________________________________________ its >>>>>>>> mailing list its@ietf.org >>>>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ its >>>>>>> mailing list its@ietf.org >>>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ its >>>>>> mailing list its@ietf.org >>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>> >>>>> >>>>> >>>>> _______________________________________________ its mailing >>>>> list its@ietf.org https://www.ietf.org/mailman/listinfo/its >>> >> > --- Ce courrier électronique ne contient aucun virus ou logiciel malveillant parce que la protection avast! Antivirus est active. http://www.avast.com From nobody Thu May 1 08:25:57 2014 Return-Path: X-Original-To: its@ietfa.amsl.com Delivered-To: its@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DFCF1A6F83 for ; Thu, 1 May 2014 08:25:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.999 X-Spam-Level: X-Spam-Status: No, score=-3.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, GB_I_LETTER=-2, MIME_QP_LONG_LINE=0.001, SPF_PASS=-0.001] autolearn=ham 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 eIXSmFxZJ9qP for ; Thu, 1 May 2014 08:25:51 -0700 (PDT) Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 8BDD41A6F85 for ; Thu, 1 May 2014 08:25:51 -0700 (PDT) Received: by mail-pa0-f46.google.com with SMTP id kx10so1036453pab.33 for ; Thu, 01 May 2014 08:25:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=3tnFJXtDoZn4rr6Pele4D9m15NE5q3w6h9HfbhYpOOM=; b=Cc32Fct0vG1gru2U6LEirUd9jktjybZL7YQCqb+3J8Q7x2K9tYAnSAlNvx+lIRlfHB U6wqSfOH5v0Zue9ps1GX/asdpGKIQzoB+KXzMoOjw7NCCU/IzsH/qMfevGFENJEBYBdc p7LCyYIfsc1bfiglwKaB+GMfoxM7ttRdAWnFrIqff1jPqgBU5D5Pw5x04gKyUxOk512m hsDK4ZO3UK4MXr/M5UhtwgbMLUJfSJnB6v71NhwzZM7Cx0uNIzj418hPi3jATMlJI7rP 3NT88ryxQ1A2G8Ki4BjVIIUYmaa44IQUt4IrTQOQIFgtWDPjRRHBoz1y5TJTGMgEAxYb ut9g== X-Received: by 10.67.13.226 with SMTP id fb2mr22442092pad.146.1398957949648; Thu, 01 May 2014 08:25:49 -0700 (PDT) Received: from [192.168.1.34] (173-8-188-29-SFBA.hfc.comcastbusiness.net. [173.8.188.29]) by mx.google.com with ESMTPSA id xo9sm159611820pab.18.2014.05.01.08.25.48 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 01 May 2014 08:25:48 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) From: Dino Farinacci X-Mailer: iPhone Mail (11D167) In-Reply-To: <53622ED2.7080605@gmail.com> Date: Thu, 1 May 2014 08:25:48 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <2ED1D3801ACAAB459FDB4EAC9EAD090C0FFFE9E2@xmb-aln-x03.cisco.com> <51064E08.9020401@gmail.com> <5106619F.7020002@inria.fr> <51067D07.9020409@gmail.com> <5108E3AB.8080205@inria.fr> <5108EA48.90003@gmail.com> <5108EDAA.90700@gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA07A4E4@AZ-FFEXMB04.global.avaya.com> <5267EAFC.9090607@gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA1291358F@AZ-FFEXMB04.global.avaya.com> <53622ED2.7080605@gmail.com> To: Alexandru Petrescu Archived-At: http://mailarchive.ietf.org/arch/msg/its/CTSqM5FPgjnys5H4WrofY80ey7g Cc: "Romascanu, Dan \(Dan\)" , "its@ietf.org" Subject: Re: [geonet/its] EtherType for geonet/ITS 0x8947 reflected at IANA (was: What do we need to make ITS WG go forward? - EtherType for ITS) X-BeenThere: its@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "GeoNet BoF discussion list." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2014 15:25:54 -0000 This sounds like the cart before the horse.=20 Why does geonet have to run at the link-layer? Now if you have to run any geonet protocol over a layer-3 network, you are r= equired to stretch a subnet and use layer-2 overlays.=20 Can someone justify this request? Dino > On May 1, 2014, at 4:24 AM, Alexandru Petrescu wrote: >=20 > Hello geonetters, >=20 > I would like to inform you that, following our discussions about EtherType= for geonet, and per my request, and per designated reviewer for this entry -= IANA has added an entry in the table of EtherTypes for 0x8947 for GeoNetwor= king, as to reflect the IEEE allocation of same EtherType. >=20 > http://www.iana.org/assignments/ieee-802-numbers >=20 > This is a good allocation which should help software designers in writing i= nteroperable implementations of geonetworking code over link layers of type E= thernet, and in some cases, links dedicated to ITS vehicular communications.= >=20 > Yours, >=20 > Alex >=20 >> On 23/10/2013 17:41, Romascanu, Dan (Dan) wrote: >> Hi Alexandru, >>=20 >> The authority for allocation is with the IEEE, and the list to be >> referenced and used in specifications is the one at IEEE. >>=20 >> The IANA list is informational and includes as specified on the page >> 'contributed unverified information from various sources'. It would >> be good I think to have the new ethertype mentioned on the IANA page >> as well, because some IETF-ers may go first to that list. I suggest >> that you just send an email to IANA asking for the change (additional >> row in the table) be made according to the IEEE allocation. We can >> talk about this with the IANA folks in Vancouver if this is not >> solved until then. >>=20 >> I am not sure who needs to be asked about the linux kernel patches, I >> can guess that a query to the apps-discuss@ietf.org may result on >> useful information from people involved with that layer. >>=20 >> I hope this helps. >>=20 >> Regards, >>=20 >> Dan >>=20 >>=20 >>=20 >>> -----Original Message----- From: Alexandru Petrescu >>> [mailto:alexandru.petrescu@gmail.com] Sent: Wednesday, October 23, >>> 2013 6:28 PM To: Romascanu, Dan (Dan); its@ietf.org Subject: Re: >>> [its] What do we need to make ITS WG go forward? - EtherType for >>> ITS >>>=20 >>> Hi Dan, >>>=20 >>> Let me bring back this topic. >>>=20 >>> Since our last discussion the EtherType for ETSI GeoNetworking >>> 0x8947 has been set at IEEE: >>> http://standards.ieee.org/develop/regauth/ethertype/eth.txt >>>=20 >>> However, it is absent at the IANA website: >>> http://www.iana.org/assignments/ieee-802-numbers/ieee-802-numbers.xml > Where should we ask at IANA about this type? >>>=20 >>> Also, this ethertype 0x8947 seems absent from the linux kernel >>> sources. >>>=20 >>> Where should we ask a patch? >>>=20 >>> Alex >>>=20 >>>=20 >>> Le 30/01/2013 11:00, Romascanu, Dan (Dan) a =C3=A9crit : >>>> Hi, >>>>=20 >>>> If the PDF letter is dated 1/29 (yesterday) than we may see the >>>> IEEE RA list updated soon. >>>>=20 >>>> There is no need for IANA to make an allocation (if we are >>>> discussing EtherTypes). The responsibility for EtherTypes >>>> assignment is with the IEEE RA and the file at IANA is only >>>> informational. See the note at >>>> http://www.iana.org/assignments/ieee-802-numbers/ieee-802-numbers.xml. >>>=20 > Regards, >>>>=20 >>>> Dan >>>>=20 >>>>=20 >>>>=20 >>>>=20 >>>>> -----Original Message----- From: its-bounces@ietf.org >>>>> [mailto:its-bounces@ietf.org] On Behalf Of Alexandru Petrescu >>>>> Sent: Wednesday, January 30, 2013 11:54 AM To: its@ietf.org >>>>> Subject: Re: [its] What do we need to make ITS WG go forward? >>>>> - EtherType for ITS >>>>>=20 >>>>> In private I got hold of a pdf letter from IEEE to ETSI dated >>>>> January 29th, 2013, which says that the EtherType is #8947. >>>>> (not sure hexa or decimal). >>>>>=20 >>>>> See that letter attached to this email. >>>>>=20 >>>>> One would say that things unfold as we speak. >>>>>=20 >>>>> I still think that IANA should also allocate it as well. (maybe >>>>> I'll get another pdf in private telling me it's already >>>>> done...) >>>>>=20 >>>>> Alex >>>>>=20 >>>>> Le 30/01/2013 10:39, Alexandru Petrescu a =C3=A9crit : >>>>>> Le 30/01/2013 10:11, Thierry Ernst a =C3=A9crit : >>>>>>>=20 >>>>>>> Alex, >>>>>>>=20 >>>>>>> IEEE have assigned Ethernet Type Field number #8947 for ITS >>>>>>> use (ETSI TC ITS's GeoNetworking). Check the following >>>>>>> document available on the ETSI server: >>>>>>>=20 >>>>>>> ITS(13)000020 >>>>>>> 00 >>> 20_Ethernet_Type_Field_number_for_GeoNetworking.pdf> >>>>>>>=20 >>>>>>>=20 >>>>>>> Ethernet Type Field number for GeoNetworking >>>>>>> http://docbox.etsi.org/ITS/ITS/05-CONTRIBUTIONS/2013/ITS(13)000020_ > Et >>> hernet_Type_Field_number_for_GeoNetworking.pdf >>>>>>=20 >>>>>> Thierry, >>>>>>=20 >>>>>> I >>>>>> may be wrong, but here are my thoughts. >>>>>>=20 >>>>>> I am trying to access these URLs you provide above but they >>>>>> are password protected. What is the username and password? >>>>>>=20 >>>>>> The URL indicates ETSI, not IEEE. >>>>>>=20 >>>>>> The IEEE URL for EtherTypes is the following, I believe: >>>>>> http://standards.ieee.org/develop/regauth/ethertype/eth.txt >>>>>>=20 >>>>>> That eth.txt file does not contain 0707 nor 8947. But it >>>>>> does contain, for example 86DD which is 'IPv6'. >>>>>>=20 >>>>>> The 0x0707 EtherType is present in an implementation which >>>>>> is supposed compliant with ETSI ITS (plugtests). Wireshark >>>>>> dump available upon request. >>>>>>=20 >>>>>> Besides, if this is to be about IPv6, I think it should be >>>>>> reserved at IANA as well, in addition to reserving it at >>>>>> IEEE. The IANA URL for IEEE 802 Numbers is at: >>>>>> http://www.iana.org/assignments/ieee-802-numbers/ieee-802-numbers.xm > l >>> (the #8947 that you mention above does not seem to figure in this >>>>>> IANA URL). >>>>>>=20 >>>>>> This is why I believe this number should be reserved both as >>>>>> an EtherType at IEEE and at IANA. >>>>>>=20 >>>>>> Yours, >>>>>>=20 >>>>>> Alex >>>>>>=20 >>>>>>>=20 >>>>>>> Regards, Thierry. >>>>>>>=20 >>>>>>>=20 >>>>>>>> On 28/01/13 14:28, Alexandru Petrescu wrote: >>>>>>>> Le 28/01/2013 14:16, Joe Klein a =C3=A9crit : >>>>>>>>> I really dislike the fact that ISO is charging for the >>>>>>>>> ISO 21217 - Architecture & ISO 21210 - IPv6 >>>>>>>>> Networking. >>>>>>>>>=20 >>>>>>>>> Does this make it any better? Safer? Should ISO now >>>>>>>>> have cybersecurity and safety liability if the >>>>>>>>> specification leads to deaths and damage to property? >>>>>>>>=20 >>>>>>>> Does it make any better interoperable as well? >>>>>>>>=20 >>>>>>>> EtherType 0x0707 described in ITS documents, implemented, >>>>>>>> but not specified by IEEE nor reserved at IANA - does not >>>>>>>> make it interoperable. >>>>>>>>=20 >>>>>>>> One wouldn't think that this 0x0707 ethertype be reserved >>>>>>>> by somebody who is not IANA nor IEEE? >>>>>>>>=20 >>>>>>>> (see a good example of interoperability: IPv6 0x86dd >>>>>>>> ethertype is reserved at IEEE and at IANA >>>>>>>> http://www.iana.org/assignments/ieee-802-numbers/ieee-802-numbers. > xm >>> l) >>>>>>=20 >>>>> Alex >>>>>>>>=20 >>>>>>>> Or should these standards remain in >>>>>>>>> the public domain, for researches to review and >>>>>>>>> validate? >>>>>>>>>=20 >>>>>>>>> Just my 2 cents. >>>>>>>>>=20 >>>>>>>>> Joe >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> On Mon, Jan 28, 2013 at 6:31 AM, Thierry Ernst >>>>>>>>> wrote: >>>>>>>>>>=20 >>>>>>>>>> Dear all, >>>>>>>>>>=20 >>>>>>>>>> At this stage, I don't think a new working group is >>>>>>>>>> needed. First, it would need a charter, and support >>>>>>>>>> from the industry. But more importantly, IETF WGs are >>>>>>>>>> not usually sector-driven, so it means the different >>>>>>>>>> issues pertaining to ITS should be brought to VARIOUS >>>>>>>>>> existing WGs, and a WG should only be created if >>>>>>>>>> there is an important issue for which there is no >>>>>>>>>> existing WG that could work on it. >>>>>>>>>>=20 >>>>>>>>>> This said, as mentioned earlier, ITS is not only >>>>>>>>>> about vehicular communications, though the issues >>>>>>>>>> listed by Alexandru below mostly consider vehicular >>>>>>>>>> communications. >>>>>>>>>>=20 >>>>>>>>>> What ITS really needs is the definition of a common >>>>>>>>>> communication architecture and the definition of what >>>>>>>>>> features should be comprised for an IPv6 networking >>>>>>>>>> stack deployed for ITS use cases. This cannot be done >>>>>>>>>> at IETF, and actually already exists at ISO: - ISO >>>>>>>>>> 21217 - Architecture - ISO 21210 - IPv6 Networking >>>>>>>>>>=20 >>>>>>>>>> As an input to the discussion, please consider >>>>>>>>>> reading documents D2.1 and D2.2 available on the >>>>>>>>>> ITSSv6 project web page: >>>>>>>>>> http://www.itssv6.eu/documentation/ D2.2 provides an >>>>>>>>>> analysis of the currently published version of ISO >>>>>>>>>> 21210, but new work items have been launched since >>>>>>>>>> then to address remaining issues. >>>>>>>>>>=20 >>>>>>>>>> Regards, Thierry. >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>>> On 28/01/13 11:08, Alexandru Petrescu wrote: >>>>>>>>>>>=20 >>>>>>>>>>> Le 28/01/2013 05:02, Stan Ratliff (sratliff) a >>>>>>>>>>> =C3=A9crit : >>>>>>>>>>>>=20 >>>>>>>>>>>> All, >>>>>>>>>>>>=20 >>>>>>>>>>>> This is just one opinion, but I'd like to >>>>>>>>>>>> understand why ITS would need its own IETF group. >>>>>>>>>>>> The work here is the same (IMO) as what is taking >>>>>>>>>>>> place in MANET. I would vote that this work be >>>>>>>>>>>> taken up in MANET. >>>>>>>>>>>=20 >>>>>>>>>>>=20 >>>>>>>>>>> Stan, >>>>>>>>>>>=20 >>>>>>>>>>> Thank you for the offer. I considered this offer >>>>>>>>>>> since some time. >>>>>>>>>>>=20 >>>>>>>>>>> I try to understand whether some of these items on >>>>>>>>>>> which I have interest could be brought in in MANET >>>>>>>>>>> WG: - V2V using prefix exchange - VIN-based IP >>>>>>>>>>> addressing scheme - ND Prefix Delegation - >>>>>>>>>>> PMIP-based network mobility - IPv6 single-address >>>>>>>>>>> connecion 'sharing' with a cellular operator and a >>>>>>>>>>> vehicular moving network (type '64share' of >>>>>>>>>>> v6ops). - Default Route with DHCPv6. >>>>>>>>>>>=20 >>>>>>>>>>> Please let me know. >>>>>>>>>>>=20 >>>>>>>>>>> Yours, >>>>>>>>>>>=20 >>>>>>>>>>> Alex >>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>> Regards, Stan >>>>>>>>>>>>=20 >>>>>>>>>>>> On Jan 26, 2013, at 9:34 AM, Abdussalam Baryun >>>>>>>>>>>> wrote: >>>>>>>>>>>>=20 >>>>>>>>>>>>> Hi Nabil, >>>>>>>>>>>>>=20 >>>>>>>>>>>>> I think we already done some steps but not sure >>>>>>>>>>>>> how far now. We will need to propose the WG and >>>>>>>>>>>>> provide the WG charter, as use cases and work >>>>>>>>>>>>> to be done in this group. This charter needs to >>>>>>>>>>>>> be approved by the IESG. I have not attended >>>>>>>>>>>>> the last meeting so not sure about the status >>>>>>>>>>>>> now, >>>>>>>>>>>>>=20 >>>>>>>>>>>>> AB >>>>>>>>>>>>>=20 >>>>>>>>>>>>> On 1/26/13, Nabil Benamar >>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> Hi All, >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> I'm still interested in this list and want to >>>>>>>>>>>>>> join voices previously heard to make it a >>>>>>>>>>>>>> working group. So what should we exactly do, >>>>>>>>>>>>>> to achieve this goal ? >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> 2013/1/26 Abdussalam Baryun >>>>>>>>>>>>>> >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> Hi All, >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> I was interested in this group but not sure >>>>>>>>>>>>>>> where are we so far. Is there progress, or >>>>>>>>>>>>>>> is there issues/efforts that need to be >>>>>>>>>>>>>>> completed and volunteered. >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> AB >>>>>>>>>>>>>>> _______________________________________________ >>>=20 > its mailing list its@ietf.org >>>>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> -- * * *=D8=AA=D8=AD=D9=8A=D8=A7=D8=AA=D9=8A =D8=8C **Cordial= ement, Regards* * * >>>>>>>>>>>>>> * * *=D9=86=D8=A8=D9=8A=D9=84 =D8=A8=D9=86=D8=B9=D9=85=D8=B1=D9= =88 Nabil Benamar* Professor of >>>>>>>>>>>>>> computer sciences Simulation and Modelisation >>>>>>>>>>>>>> Laboratory Human Sciences Faculty of Meknes >>>>>>>>>>>>>> Moulay Ismail* *University* Meknes, Morocco >>>>>>>>>>>>>> *GSM: * *+ 212 6 70832236 >>>>>>>>>>>>>> http://nabilbenamar.com/ >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> * >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> ------------------------------------------------------------ > -- >>> ------------------ >>>>>>>>>>>=20 >>>>>>>> * >>>>>>>>>>>>> _______________________________________________ > its mailing list its@ietf.org >>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> its mailing list its@ietf.org >>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>>>>>>>=20 >>>>>>>>>>>=20 >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> its mailing list its@ietf.org >>>>>>>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>> _______________________________________________ its >>>>>>>>>> mailing list its@ietf.org >>>>>>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>>>>> _______________________________________________ its >>>>>>>>> mailing list its@ietf.org >>>>>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>>>>=20 >>>>>>>>=20 >>>>>>>> _______________________________________________ its >>>>>>>> mailing list its@ietf.org >>>>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>> _______________________________________________ its >>>>>>> mailing list its@ietf.org >>>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>>=20 >>>>>>=20 >>>>>> _______________________________________________ its mailing >>>>>> list its@ietf.org https://www.ietf.org/mailman/listinfo/its >=20 >=20 > --- > Ce courrier =C3=A9lectronique ne contient aucun virus ou logiciel malveill= ant parce que la protection avast! Antivirus est active. > http://www.avast.com >=20 > _______________________________________________ > its mailing list > its@ietf.org > https://www.ietf.org/mailman/listinfo/its From nobody Thu May 1 09:05:40 2014 Return-Path: X-Original-To: its@ietfa.amsl.com Delivered-To: its@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69FC01A6F8F for ; Thu, 1 May 2014 09:05:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.456 X-Spam-Level: X-Spam-Status: No, score=-2.456 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RP_MATCHES_RCVD=-0.651] autolearn=ham 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 BICZ7cVO0pu5 for ; Thu, 1 May 2014 09:05:35 -0700 (PDT) Received: from fromintouta.tno.nl (fromintouta.tno.nl [134.221.1.26]) by ietfa.amsl.com (Postfix) with ESMTP id CBCED1A08F2 for ; Thu, 1 May 2014 09:05:34 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.97,965,1389740400"; d="scan'208";a="25008583" Received: from unknown (HELO mail.tno.nl) ([134.221.225.221]) by mailhost1a.tno.nl with ESMTP; 01 May 2014 18:05:31 +0200 Received: from EXC-MBX03.tsn.tno.nl ([fe80::e969:1300:fb9f:7e12]) by EXC-CASHUB02.tsn.tno.nl ([fe80::8c02:de2a:3094:171%14]) with mapi id 14.03.0174.001; Thu, 1 May 2014 18:05:31 +0200 From: "Velt, R. (Ronald) in 't" To: Dino Farinacci , Alexandru Petrescu Thread-Topic: [geonet/its] EtherType for geonet/ITS 0x8947 reflected at IANA (was: What do we need to make ITS WG go forward? - EtherType for ITS) Thread-Index: AQHPZS/8V0zSQakqOE2tBPZU326n15srt1oAgAAn6nA= Date: Thu, 1 May 2014 16:05:31 +0000 Message-ID: <72FB622921C13746AD6349E70A8D9F307DB5492C@EXC-MBX03.tsn.tno.nl> References: <2ED1D3801ACAAB459FDB4EAC9EAD090C0FFFE9E2@xmb-aln-x03.cisco.com> <51064E08.9020401@gmail.com> <5106619F.7020002@inria.fr> <51067D07.9020409@gmail.com> <5108E3AB.8080205@inria.fr> <5108EA48.90003@gmail.com> <5108EDAA.90700@gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA07A4E4@AZ-FFEXMB04.global.avaya.com> <5267EAFC.9090607@gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA1291358F@AZ-FFEXMB04.global.avaya.com> <53622ED2.7080605@gmail.com> In-Reply-To: Accept-Language: en-US, nl-NL Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [134.221.225.191] Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Archived-At: http://mailarchive.ietf.org/arch/msg/its/BblsQbhwLPoVVurqMjI8Mmcal1A Cc: "Romascanu, Dan \(Dan\)" , "its@ietf.org" Subject: Re: [geonet/its] EtherType for geonet/ITS 0x8947 reflected at IANA (was: What do we need to make ITS WG go forward? - EtherType for ITS) X-BeenThere: its@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "GeoNet BoF discussion list." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2014 16:05:39 -0000 RGlubywNCg0KPi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+RnJvbTogaXRzIFttYWlsdG86 aXRzLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBEaW5vIEZhcmluYWNjaQ0KPlNlbnQ6 IGRvbmRlcmRhZyAxIG1laSAyMDE0IDE3OjI2DQo+VG86IEFsZXhhbmRydSBQZXRyZXNjdQ0KPkNj OiBSb21hc2NhbnUsIERhbiAoRGFuKTsgaXRzQGlldGYub3JnDQo+U3ViamVjdDogUmU6IFtnZW9u ZXQvaXRzXSBFdGhlclR5cGUgZm9yIGdlb25ldC9JVFMgMHg4OTQ3IHJlZmxlY3RlZCBhdCBJQU5B DQo+KHdhczogV2hhdCBkbyB3ZSBuZWVkIHRvIG1ha2UgSVRTIFdHIGdvIGZvcndhcmQ/IC0gRXRo ZXJUeXBlIGZvciBJVFMpDQo+DQo+VGhpcyBzb3VuZHMgbGlrZSB0aGUgY2FydCBiZWZvcmUgdGhl IGhvcnNlLg0KPg0KPldoeSBkb2VzIGdlb25ldCBoYXZlIHRvIHJ1biBhdCB0aGUgbGluay1sYXll cj8NCj4NCj5Ob3cgaWYgeW91IGhhdmUgdG8gcnVuIGFueSBnZW9uZXQgcHJvdG9jb2wgb3ZlciBh IGxheWVyLTMgbmV0d29yaywgeW91IGFyZQ0KPnJlcXVpcmVkIHRvIHN0cmV0Y2ggYSBzdWJuZXQg YW5kIHVzZSBsYXllci0yIG92ZXJsYXlzLg0KPg0KPkNhbiBzb21lb25lIGp1c3RpZnkgdGhpcyBy ZXF1ZXN0Pw0KDQpUaGlzIGlzIHRoZSBFdGhlclR5cGUgdGhhdCB3YXMgcmVxdWVzdGVkIGJ5IEVU U0kgVGVjaG5pY2FsIENvbW1pdHRlZSBJVFMgZm9yIHRoZWlyICpub24tSVAtYmFzZWQqIEdlb05l dHdvcmtpbmcgcHJvdG9jb2wsIHdoaWNoIHJ1bnMgb3ZlciBJRUVFIDgwMi4xMSBPQ0IgbW9kZSAo b3IgIkc1IiBpbiB0aGVpciBwYXJsYW5jZSkuIEl0IGhhcyBub3RoaW5nIHRvIGRvICh5ZXQpIHdp dGggYW55IGV4aXN0aW5nIG9yIHByb3Bvc2VkIElFVEYgcHJvdG9jb2wvYWN0aXZpdHkuDQoNClRo aXMgYWN0aW9uIG1lcmVseSBtZWFucyB0aGF0IElBTkEncyB0YWJsZSBub3cgaG9sZHMgYW4gZW50 cnkgdGhhdCB3YXMgIGFkZGVkIHRvIElFRUUncyBvd24gdGFibGUgZWFybHkgbGFzdCB5ZWFyLg0K DQpCZXN0IHJlZ2FyZHMsDQpSb25hbGQgaW4gJ3QgVmVsdA0KDQo+DQo+RGlubw0KPg0KPj4gT24g TWF5IDEsIDIwMTQsIGF0IDQ6MjQgQU0sIEFsZXhhbmRydSBQZXRyZXNjdQ0KPjxhbGV4YW5kcnUu cGV0cmVzY3VAZ21haWwuY29tPiB3cm90ZToNCj4+DQo+PiBIZWxsbyBnZW9uZXR0ZXJzLA0KPj4N Cj4+IEkgd291bGQgbGlrZSB0byBpbmZvcm0geW91IHRoYXQsIGZvbGxvd2luZyBvdXIgZGlzY3Vz c2lvbnMgYWJvdXQgRXRoZXJUeXBlDQo+Zm9yIGdlb25ldCwgYW5kIHBlciBteSByZXF1ZXN0LCBh bmQgcGVyIGRlc2lnbmF0ZWQgcmV2aWV3ZXIgZm9yIHRoaXMgZW50cnkgLQ0KPklBTkEgaGFzIGFk ZGVkIGFuIGVudHJ5IGluIHRoZSB0YWJsZSBvZiBFdGhlclR5cGVzIGZvciAweDg5NDcgZm9yDQo+ R2VvTmV0d29ya2luZywgYXMgdG8gcmVmbGVjdCB0aGUgSUVFRSBhbGxvY2F0aW9uIG9mIHNhbWUg RXRoZXJUeXBlLg0KPj4NCj4+ICAgICBodHRwOi8vd3d3LmlhbmEub3JnL2Fzc2lnbm1lbnRzL2ll ZWUtODAyLW51bWJlcnMNCj4+DQo+PiBUaGlzIGlzIGEgZ29vZCBhbGxvY2F0aW9uIHdoaWNoIHNo b3VsZCBoZWxwIHNvZnR3YXJlIGRlc2lnbmVycyBpbiB3cml0aW5nDQo+aW50ZXJvcGVyYWJsZSBp bXBsZW1lbnRhdGlvbnMgb2YgZ2VvbmV0d29ya2luZyBjb2RlIG92ZXIgbGluayBsYXllcnMgb2YN Cj50eXBlIEV0aGVybmV0LCBhbmQgaW4gc29tZSBjYXNlcywgbGlua3MgZGVkaWNhdGVkIHRvIElU UyB2ZWhpY3VsYXINCj5jb21tdW5pY2F0aW9ucy4NCj4+DQo+PiBZb3VycywNCj4+DQo+PiBBbGV4 DQo+Pg0KPj4+IE9uIDIzLzEwLzIwMTMgMTc6NDEsIFJvbWFzY2FudSwgRGFuIChEYW4pIHdyb3Rl Og0KPj4+IEhpIEFsZXhhbmRydSwNCj4+Pg0KPj4+IFRoZSBhdXRob3JpdHkgZm9yIGFsbG9jYXRp b24gaXMgd2l0aCB0aGUgSUVFRSwgYW5kIHRoZSBsaXN0IHRvIGJlDQo+Pj4gcmVmZXJlbmNlZCBh bmQgdXNlZCBpbiBzcGVjaWZpY2F0aW9ucyBpcyB0aGUgb25lIGF0IElFRUUuDQo+Pj4NCj4+PiBU aGUgSUFOQSBsaXN0IGlzIGluZm9ybWF0aW9uYWwgYW5kIGluY2x1ZGVzIGFzIHNwZWNpZmllZCBv biB0aGUgcGFnZQ0KPj4+ICdjb250cmlidXRlZCB1bnZlcmlmaWVkIGluZm9ybWF0aW9uIGZyb20g dmFyaW91cyBzb3VyY2VzJy4gSXQgd291bGQNCj4+PiBiZSBnb29kIEkgdGhpbmsgdG8gaGF2ZSB0 aGUgbmV3IGV0aGVydHlwZSBtZW50aW9uZWQgb24gdGhlIElBTkEgcGFnZQ0KPj4+IGFzIHdlbGws IGJlY2F1c2Ugc29tZSBJRVRGLWVycyBtYXkgZ28gZmlyc3QgdG8gdGhhdCBsaXN0LiBJIHN1Z2dl c3QNCj4+PiB0aGF0IHlvdSBqdXN0IHNlbmQgYW4gZW1haWwgdG8gSUFOQSBhc2tpbmcgZm9yIHRo ZSBjaGFuZ2UgKGFkZGl0aW9uYWwNCj4+PiByb3cgaW4gdGhlIHRhYmxlKSBiZSBtYWRlIGFjY29y ZGluZyB0byB0aGUgSUVFRSBhbGxvY2F0aW9uLiBXZSBjYW4NCj4+PiB0YWxrIGFib3V0IHRoaXMg d2l0aCB0aGUgSUFOQSBmb2xrcyBpbiBWYW5jb3V2ZXIgaWYgdGhpcyBpcyBub3QNCj4+PiBzb2x2 ZWQgdW50aWwgdGhlbi4NCj4+Pg0KPj4+IEkgYW0gbm90IHN1cmUgd2hvIG5lZWRzIHRvIGJlIGFz a2VkIGFib3V0IHRoZSBsaW51eCBrZXJuZWwgcGF0Y2hlcywgSQ0KPj4+IGNhbiBndWVzcyB0aGF0 IGEgcXVlcnkgdG8gdGhlIGFwcHMtZGlzY3Vzc0BpZXRmLm9yZyBtYXkgcmVzdWx0IG9uDQo+Pj4g dXNlZnVsIGluZm9ybWF0aW9uIGZyb20gcGVvcGxlIGludm9sdmVkIHdpdGggdGhhdCBsYXllci4N Cj4+Pg0KPj4+IEkgaG9wZSB0aGlzIGhlbHBzLg0KPj4+DQo+Pj4gUmVnYXJkcywNCj4+Pg0KPj4+ IERhbg0KPj4+DQo+Pj4NCj4+Pg0KPj4+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLSBGcm9t OiBBbGV4YW5kcnUgUGV0cmVzY3UNCj4+Pj4gW21haWx0bzphbGV4YW5kcnUucGV0cmVzY3VAZ21h aWwuY29tXSBTZW50OiBXZWRuZXNkYXksIE9jdG9iZXIgMjMsDQo+Pj4+IDIwMTMgNjoyOCBQTSBU bzogUm9tYXNjYW51LCBEYW4gKERhbik7IGl0c0BpZXRmLm9yZyBTdWJqZWN0OiBSZToNCj4+Pj4g W2l0c10gV2hhdCBkbyB3ZSBuZWVkIHRvIG1ha2UgSVRTIFdHIGdvIGZvcndhcmQ/IC0gRXRoZXJU eXBlIGZvciBJVFMNCj4+Pj4NCj4+Pj4gSGkgRGFuLA0KPj4+Pg0KPj4+PiBMZXQgbWUgYnJpbmcg YmFjayB0aGlzIHRvcGljLg0KPj4+Pg0KPj4+PiBTaW5jZSBvdXIgbGFzdCBkaXNjdXNzaW9uIHRo ZSBFdGhlclR5cGUgZm9yIEVUU0kgR2VvTmV0d29ya2luZw0KPj4+PiAweDg5NDcgaGFzIGJlZW4g c2V0IGF0IElFRUU6DQo+Pj4+IGh0dHA6Ly9zdGFuZGFyZHMuaWVlZS5vcmcvZGV2ZWxvcC9yZWdh dXRoL2V0aGVydHlwZS9ldGgudHh0DQo+Pj4+DQo+Pj4+IEhvd2V2ZXIsIGl0IGlzIGFic2VudCBh dCB0aGUgSUFOQSB3ZWJzaXRlOg0KPj4+PiBodHRwOi8vd3d3LmlhbmEub3JnL2Fzc2lnbm1lbnRz L2llZWUtODAyLW51bWJlcnMvaWVlZS04MDItDQo+bnVtYmVycy54bQ0KPj4+PiBsDQo+PiBXaGVy ZSBzaG91bGQgd2UgYXNrIGF0IElBTkEgYWJvdXQgdGhpcyB0eXBlPw0KPj4+Pg0KPj4+PiBBbHNv LCB0aGlzIGV0aGVydHlwZSAweDg5NDcgc2VlbXMgYWJzZW50IGZyb20gdGhlIGxpbnV4IGtlcm5l bA0KPj4+PiBzb3VyY2VzLg0KPj4+Pg0KPj4+PiBXaGVyZSBzaG91bGQgd2UgYXNrIGEgcGF0Y2g/ DQo+Pj4+DQo+Pj4+IEFsZXgNCj4+Pj4NCj4+Pj4NCj4+Pj4gTGUgMzAvMDEvMjAxMyAxMTowMCwg Um9tYXNjYW51LCBEYW4gKERhbikgYSDDqWNyaXQgOg0KPj4+Pj4gSGksDQo+Pj4+Pg0KPj4+Pj4g SWYgdGhlIFBERiBsZXR0ZXIgaXMgZGF0ZWQgMS8yOSAoeWVzdGVyZGF5KSB0aGFuIHdlIG1heSBz ZWUgdGhlDQo+Pj4+PiBJRUVFIFJBIGxpc3QgdXBkYXRlZCBzb29uLg0KPj4+Pj4NCj4+Pj4+IFRo ZXJlIGlzIG5vIG5lZWQgZm9yIElBTkEgdG8gbWFrZSBhbiBhbGxvY2F0aW9uIChpZiB3ZSBhcmUN Cj4+Pj4+IGRpc2N1c3NpbmcgRXRoZXJUeXBlcykuIFRoZSByZXNwb25zaWJpbGl0eSBmb3IgRXRo ZXJUeXBlcw0KPj4+Pj4gYXNzaWdubWVudCBpcyB3aXRoIHRoZSBJRUVFIFJBIGFuZCB0aGUgZmls ZSBhdCBJQU5BIGlzIG9ubHkNCj4+Pj4+IGluZm9ybWF0aW9uYWwuIFNlZSB0aGUgbm90ZSBhdA0K Pj4+Pj4gaHR0cDovL3d3dy5pYW5hLm9yZy9hc3NpZ25tZW50cy9pZWVlLTgwMi1udW1iZXJzL2ll ZWUtODAyLQ0KPm51bWJlcnMueG1sLg0KPj4+Pg0KPj4gUmVnYXJkcywNCj4+Pj4+DQo+Pj4+PiBE YW4NCj4+Pj4+DQo+Pj4+Pg0KPj4+Pj4NCj4+Pj4+DQo+Pj4+Pj4gLS0tLS1PcmlnaW5hbCBNZXNz YWdlLS0tLS0gRnJvbTogaXRzLWJvdW5jZXNAaWV0Zi5vcmcNCj4+Pj4+PiBbbWFpbHRvOml0cy1i b3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgQWxleGFuZHJ1IFBldHJlc2N1DQo+Pj4+Pj4g U2VudDogV2VkbmVzZGF5LCBKYW51YXJ5IDMwLCAyMDEzIDExOjU0IEFNIFRvOiBpdHNAaWV0Zi5v cmcNCj4+Pj4+PiBTdWJqZWN0OiBSZTogW2l0c10gV2hhdCBkbyB3ZSBuZWVkIHRvIG1ha2UgSVRT IFdHIGdvIGZvcndhcmQ/DQo+Pj4+Pj4gLSBFdGhlclR5cGUgZm9yIElUUw0KPj4+Pj4+DQo+Pj4+ Pj4gSW4gcHJpdmF0ZSBJIGdvdCBob2xkIG9mIGEgcGRmIGxldHRlciBmcm9tIElFRUUgdG8gRVRT SSBkYXRlZA0KPj4+Pj4+IEphbnVhcnkgMjl0aCwgMjAxMywgd2hpY2ggc2F5cyB0aGF0IHRoZSBF dGhlclR5cGUgaXMgIzg5NDcuDQo+Pj4+Pj4gKG5vdCBzdXJlIGhleGEgb3IgZGVjaW1hbCkuDQo+ Pj4+Pj4NCj4+Pj4+PiBTZWUgdGhhdCBsZXR0ZXIgYXR0YWNoZWQgdG8gdGhpcyBlbWFpbC4NCj4+ Pj4+Pg0KPj4+Pj4+IE9uZSB3b3VsZCBzYXkgdGhhdCB0aGluZ3MgdW5mb2xkIGFzIHdlIHNwZWFr Lg0KPj4+Pj4+DQo+Pj4+Pj4gSSBzdGlsbCB0aGluayB0aGF0IElBTkEgc2hvdWxkIGFsc28gYWxs b2NhdGUgaXQgYXMgd2VsbC4gKG1heWJlDQo+Pj4+Pj4gSSdsbCBnZXQgYW5vdGhlciBwZGYgaW4g cHJpdmF0ZSB0ZWxsaW5nIG1lIGl0J3MgYWxyZWFkeQ0KPj4+Pj4+IGRvbmUuLi4pDQo+Pj4+Pj4N Cj4+Pj4+PiBBbGV4DQo+Pj4+Pj4NCj4+Pj4+PiBMZSAzMC8wMS8yMDEzIDEwOjM5LCBBbGV4YW5k cnUgUGV0cmVzY3UgYSDDqWNyaXQgOg0KPj4+Pj4+PiBMZSAzMC8wMS8yMDEzIDEwOjExLCBUaGll cnJ5IEVybnN0IGEgw6ljcml0IDoNCj4+Pj4+Pj4+DQo+Pj4+Pj4+PiBBbGV4LA0KPj4+Pj4+Pj4N Cj4+Pj4+Pj4+IElFRUUgaGF2ZSBhc3NpZ25lZCBFdGhlcm5ldCBUeXBlIEZpZWxkIG51bWJlciAj ODk0NyBmb3IgSVRTIHVzZQ0KPj4+Pj4+Pj4gKEVUU0kgVEMgSVRTJ3MgR2VvTmV0d29ya2luZyku IENoZWNrIHRoZSBmb2xsb3dpbmcgZG9jdW1lbnQNCj4+Pj4+Pj4+IGF2YWlsYWJsZSBvbiB0aGUg RVRTSSBzZXJ2ZXI6DQo+Pj4+Pj4+Pg0KPj4+Pj4+Pj4gSVRTKDEzKTAwMDAyMA0KPj4+Pj4+Pj4g PGh0dHA6Ly9kb2Nib3guZXRzaS5vcmcvSVRTL0lUUy8wNS0NCj5DT05UUklCVVRJT05TLzIwMTMv SVRTJTI4MTMlMg0KPj4+Pj4+Pj4gOTAwDQo+PiAwMA0KPj4+PiAyMF9FdGhlcm5ldF9UeXBlX0Zp ZWxkX251bWJlcl9mb3JfR2VvTmV0d29ya2luZy5wZGY+DQo+Pj4+Pj4+Pg0KPj4+Pj4+Pj4NCj4+ Pj4+Pj4+IEV0aGVybmV0IFR5cGUgRmllbGQgbnVtYmVyIGZvciBHZW9OZXR3b3JraW5nDQo+Pj4+ Pj4+PiBodHRwOi8vZG9jYm94LmV0c2kub3JnL0lUUy9JVFMvMDUtDQo+Q09OVFJJQlVUSU9OUy8y MDEzL0lUUygxMykwMDAwDQo+Pj4+Pj4+PiAyMF8NCj4+IEV0DQo+Pj4+IGhlcm5ldF9UeXBlX0Zp ZWxkX251bWJlcl9mb3JfR2VvTmV0d29ya2luZy5wZGYNCj4+Pj4+Pj4NCj4+Pj4+Pj4gVGhpZXJy eSwNCj4+Pj4+Pj4NCj4+Pj4+Pj4gSQ0KPj4+Pj4+PiBtYXkgYmUgd3JvbmcsIGJ1dCBoZXJlIGFy ZSBteSB0aG91Z2h0cy4NCj4+Pj4+Pj4NCj4+Pj4+Pj4gSSBhbSB0cnlpbmcgdG8gYWNjZXNzIHRo ZXNlIFVSTHMgeW91IHByb3ZpZGUgYWJvdmUgYnV0IHRoZXkgYXJlDQo+Pj4+Pj4+IHBhc3N3b3Jk IHByb3RlY3RlZC4gIFdoYXQgaXMgdGhlIHVzZXJuYW1lIGFuZCBwYXNzd29yZD8NCj4+Pj4+Pj4N Cj4+Pj4+Pj4gVGhlIFVSTCBpbmRpY2F0ZXMgRVRTSSwgbm90IElFRUUuDQo+Pj4+Pj4+DQo+Pj4+ Pj4+IFRoZSBJRUVFIFVSTCBmb3IgRXRoZXJUeXBlcyBpcyB0aGUgZm9sbG93aW5nLCBJIGJlbGll dmU6DQo+Pj4+Pj4+IGh0dHA6Ly9zdGFuZGFyZHMuaWVlZS5vcmcvZGV2ZWxvcC9yZWdhdXRoL2V0 aGVydHlwZS9ldGgudHh0DQo+Pj4+Pj4+DQo+Pj4+Pj4+IFRoYXQgZXRoLnR4dCBmaWxlIGRvZXMg bm90IGNvbnRhaW4gMDcwNyBub3IgODk0Ny4gIEJ1dCBpdCBkb2VzDQo+Pj4+Pj4+IGNvbnRhaW4s IGZvciBleGFtcGxlIDg2REQgd2hpY2ggaXMgJ0lQdjYnLg0KPj4+Pj4+Pg0KPj4+Pj4+PiBUaGUg MHgwNzA3IEV0aGVyVHlwZSBpcyBwcmVzZW50IGluIGFuIGltcGxlbWVudGF0aW9uIHdoaWNoIGlz DQo+Pj4+Pj4+IHN1cHBvc2VkIGNvbXBsaWFudCB3aXRoIEVUU0kgSVRTIChwbHVndGVzdHMpLiAg V2lyZXNoYXJrIGR1bXANCj4+Pj4+Pj4gYXZhaWxhYmxlIHVwb24gcmVxdWVzdC4NCj4+Pj4+Pj4N Cj4+Pj4+Pj4gQmVzaWRlcywgaWYgdGhpcyBpcyB0byBiZSBhYm91dCBJUHY2LCBJIHRoaW5rIGl0 IHNob3VsZCBiZQ0KPj4+Pj4+PiByZXNlcnZlZCBhdCBJQU5BIGFzIHdlbGwsIGluIGFkZGl0aW9u IHRvIHJlc2VydmluZyBpdCBhdCBJRUVFLg0KPj4+Pj4+PiBUaGUgSUFOQSBVUkwgZm9yIElFRUUg ODAyIE51bWJlcnMgaXMgYXQ6DQo+Pj4+Pj4+IGh0dHA6Ly93d3cuaWFuYS5vcmcvYXNzaWdubWVu dHMvaWVlZS04MDItbnVtYmVycy9pZWVlLTgwMi0NCj5udW1iZXJzDQo+Pj4+Pj4+IC54bQ0KPj4g bA0KPj4+PiAodGhlICM4OTQ3IHRoYXQgeW91IG1lbnRpb24gYWJvdmUgZG9lcyBub3Qgc2VlbSB0 byBmaWd1cmUgaW4gdGhpcw0KPj4+Pj4+PiBJQU5BIFVSTCkuDQo+Pj4+Pj4+DQo+Pj4+Pj4+IFRo aXMgaXMgd2h5IEkgYmVsaWV2ZSB0aGlzIG51bWJlciBzaG91bGQgYmUgcmVzZXJ2ZWQgYm90aCBh cyBhbg0KPj4+Pj4+PiBFdGhlclR5cGUgYXQgSUVFRSBhbmQgYXQgSUFOQS4NCj4+Pj4+Pj4NCj4+ Pj4+Pj4gWW91cnMsDQo+Pj4+Pj4+DQo+Pj4+Pj4+IEFsZXgNCj4+Pj4+Pj4NCj4+Pj4+Pj4+DQo+ Pj4+Pj4+PiBSZWdhcmRzLCBUaGllcnJ5Lg0KPj4+Pj4+Pj4NCj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4g T24gMjgvMDEvMTMgMTQ6MjgsIEFsZXhhbmRydSBQZXRyZXNjdSB3cm90ZToNCj4+Pj4+Pj4+PiBM ZSAyOC8wMS8yMDEzIDE0OjE2LCBKb2UgS2xlaW4gYSDDqWNyaXQgOg0KPj4+Pj4+Pj4+PiBJIHJl YWxseSBkaXNsaWtlIHRoZSBmYWN0IHRoYXQgSVNPIGlzIGNoYXJnaW5nIGZvciB0aGUgSVNPDQo+ Pj4+Pj4+Pj4+IDIxMjE3IC0gQXJjaGl0ZWN0dXJlICYgSVNPIDIxMjEwIC0gSVB2NiBOZXR3b3Jr aW5nLg0KPj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+PiBEb2VzIHRoaXMgbWFrZSBpdCBhbnkgYmV0dGVy PyBTYWZlcj8gIFNob3VsZCBJU08gbm93IGhhdmUNCj4+Pj4+Pj4+Pj4gY3liZXJzZWN1cml0eSBh bmQgc2FmZXR5IGxpYWJpbGl0eSBpZiB0aGUgc3BlY2lmaWNhdGlvbiBsZWFkcw0KPj4+Pj4+Pj4+ PiB0byBkZWF0aHMgYW5kIGRhbWFnZSB0byBwcm9wZXJ0eT8NCj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+ IERvZXMgaXQgbWFrZSBhbnkgYmV0dGVyIGludGVyb3BlcmFibGUgYXMgd2VsbD8NCj4+Pj4+Pj4+ Pg0KPj4+Pj4+Pj4+IEV0aGVyVHlwZSAweDA3MDcgZGVzY3JpYmVkIGluIElUUyBkb2N1bWVudHMs IGltcGxlbWVudGVkLCBidXQNCj4+Pj4+Pj4+PiBub3Qgc3BlY2lmaWVkIGJ5IElFRUUgbm9yIHJl c2VydmVkIGF0IElBTkEgLSBkb2VzIG5vdCBtYWtlIGl0DQo+Pj4+Pj4+Pj4gaW50ZXJvcGVyYWJs ZS4NCj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+IE9uZSB3b3VsZG4ndCB0aGluayB0aGF0IHRoaXMgMHgw NzA3IGV0aGVydHlwZSBiZSByZXNlcnZlZCBieQ0KPj4+Pj4+Pj4+IHNvbWVib2R5IHdobyBpcyBu b3QgSUFOQSBub3IgSUVFRT8NCj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+IChzZWUgYSBnb29kIGV4YW1w bGUgb2YgaW50ZXJvcGVyYWJpbGl0eTogSVB2NiAweDg2ZGQgZXRoZXJ0eXBlDQo+Pj4+Pj4+Pj4g aXMgcmVzZXJ2ZWQgYXQgSUVFRSBhbmQgYXQgSUFOQQ0KPj4+Pj4+Pj4+IGh0dHA6Ly93d3cuaWFu YS5vcmcvYXNzaWdubWVudHMvaWVlZS04MDItbnVtYmVycy9pZWVlLTgwMi0NCj5udW1iZXJzLg0K Pj4geG0NCj4+Pj4gbCkNCj4+Pj4+Pj4NCj4+Pj4+PiBBbGV4DQo+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+ PiBPciBzaG91bGQgdGhlc2Ugc3RhbmRhcmRzIHJlbWFpbiBpbg0KPj4+Pj4+Pj4+PiB0aGUgcHVi bGljIGRvbWFpbiwgZm9yIHJlc2VhcmNoZXMgdG8gcmV2aWV3IGFuZCB2YWxpZGF0ZT8NCj4+Pj4+ Pj4+Pj4NCj4+Pj4+Pj4+Pj4gSnVzdCBteSAyIGNlbnRzLg0KPj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+ PiBKb2UNCj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4gT24g TW9uLCBKYW4gMjgsIDIwMTMgYXQgNjozMSBBTSwgVGhpZXJyeSBFcm5zdA0KPj4+Pj4+Pj4+PiA8 dGhpZXJyeS5lcm5zdEBpbnJpYS5mcj4gd3JvdGU6DQo+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pj4g RGVhciBhbGwsDQo+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pj4gQXQgdGhpcyBzdGFnZSwgSSBkb24n dCB0aGluayBhIG5ldyB3b3JraW5nIGdyb3VwIGlzIG5lZWRlZC4NCj4+Pj4+Pj4+Pj4+IEZpcnN0 LCBpdCB3b3VsZCBuZWVkIGEgY2hhcnRlciwgYW5kIHN1cHBvcnQgZnJvbSB0aGUNCj4+Pj4+Pj4+ Pj4+IGluZHVzdHJ5LiBCdXQgbW9yZSBpbXBvcnRhbnRseSwgSUVURiBXR3MgYXJlIG5vdCB1c3Vh bGx5DQo+Pj4+Pj4+Pj4+PiBzZWN0b3ItZHJpdmVuLCBzbyBpdCBtZWFucyB0aGUgZGlmZmVyZW50 IGlzc3VlcyBwZXJ0YWluaW5nIHRvDQo+Pj4+Pj4+Pj4+PiBJVFMgc2hvdWxkIGJlIGJyb3VnaHQg dG8gVkFSSU9VUyBleGlzdGluZyBXR3MsIGFuZCBhIFdHDQo+Pj4+Pj4+Pj4+PiBzaG91bGQgb25s eSBiZSBjcmVhdGVkIGlmIHRoZXJlIGlzIGFuIGltcG9ydGFudCBpc3N1ZSBmb3INCj4+Pj4+Pj4+ Pj4+IHdoaWNoIHRoZXJlIGlzIG5vIGV4aXN0aW5nIFdHIHRoYXQgY291bGQgd29yayBvbiBpdC4N Cj4+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+PiBUaGlzIHNhaWQsIGFzIG1lbnRpb25lZCBlYXJsaWVy LCBJVFMgaXMgbm90IG9ubHkgYWJvdXQNCj4+Pj4+Pj4+Pj4+IHZlaGljdWxhciBjb21tdW5pY2F0 aW9ucywgdGhvdWdoIHRoZSBpc3N1ZXMgbGlzdGVkIGJ5DQo+Pj4+Pj4+Pj4+PiBBbGV4YW5kcnUg YmVsb3cgbW9zdGx5IGNvbnNpZGVyIHZlaGljdWxhciBjb21tdW5pY2F0aW9ucy4NCj4+Pj4+Pj4+ Pj4+DQo+Pj4+Pj4+Pj4+PiBXaGF0IElUUyByZWFsbHkgbmVlZHMgaXMgdGhlIGRlZmluaXRpb24g b2YgYSBjb21tb24NCj4+Pj4+Pj4+Pj4+IGNvbW11bmljYXRpb24gYXJjaGl0ZWN0dXJlIGFuZCB0 aGUgZGVmaW5pdGlvbiBvZiB3aGF0DQo+Pj4+Pj4+Pj4+PiBmZWF0dXJlcyBzaG91bGQgYmUgY29t cHJpc2VkIGZvciBhbiBJUHY2IG5ldHdvcmtpbmcgc3RhY2sNCj4+Pj4+Pj4+Pj4+IGRlcGxveWVk IGZvciBJVFMgdXNlIGNhc2VzLiBUaGlzIGNhbm5vdCBiZSBkb25lIGF0IElFVEYsIGFuZA0KPj4+ Pj4+Pj4+Pj4gYWN0dWFsbHkgYWxyZWFkeSBleGlzdHMgYXQgSVNPOiAtIElTTw0KPj4+Pj4+Pj4+ Pj4gMjEyMTcgLSBBcmNoaXRlY3R1cmUgLSBJU08gMjEyMTAgLSBJUHY2IE5ldHdvcmtpbmcNCj4+ Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+PiBBcyBhbiBpbnB1dCB0byB0aGUgZGlzY3Vzc2lvbiwgcGxl YXNlIGNvbnNpZGVyIHJlYWRpbmcNCj4+Pj4+Pj4+Pj4+IGRvY3VtZW50cyBEMi4xIGFuZCBEMi4y IGF2YWlsYWJsZSBvbiB0aGUNCj4+Pj4+Pj4+Pj4+IElUU1N2NiBwcm9qZWN0IHdlYiBwYWdlOg0K Pj4+Pj4+Pj4+Pj4gaHR0cDovL3d3dy5pdHNzdjYuZXUvZG9jdW1lbnRhdGlvbi8gRDIuMiBwcm92 aWRlcyBhbiBhbmFseXNpcw0KPj4+Pj4+Pj4+Pj4gb2YgdGhlIGN1cnJlbnRseSBwdWJsaXNoZWQg dmVyc2lvbiBvZiBJU08gMjEyMTAsIGJ1dCBuZXcgd29yaw0KPj4+Pj4+Pj4+Pj4gaXRlbXMgaGF2 ZSBiZWVuIGxhdW5jaGVkIHNpbmNlIHRoZW4gdG8gYWRkcmVzcyByZW1haW5pbmcNCj4+Pj4+Pj4+ Pj4+IGlzc3Vlcy4NCj4+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+PiBSZWdhcmRzLCBUaGllcnJ5Lg0K Pj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pj4NCj4+Pj4+ Pj4+Pj4+DQo+Pj4+Pj4+Pj4+Pj4gT24gMjgvMDEvMTMgMTE6MDgsIEFsZXhhbmRydSBQZXRyZXNj dSB3cm90ZToNCj4+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pj4+IExlIDI4LzAxLzIwMTMgMDU6MDIs IFN0YW4gUmF0bGlmZiAoc3JhdGxpZmYpIGEgw6ljcml0IDoNCj4+Pj4+Pj4+Pj4+Pj4NCj4+Pj4+ Pj4+Pj4+Pj4gQWxsLA0KPj4+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pj4+PiBUaGlzIGlzIGp1c3Qg b25lIG9waW5pb24sIGJ1dCBJJ2QgbGlrZSB0byB1bmRlcnN0YW5kIHdoeQ0KPj4+Pj4+Pj4+Pj4+ PiBJVFMgd291bGQgbmVlZCBpdHMgb3duIElFVEYgZ3JvdXAuDQo+Pj4+Pj4+Pj4+Pj4+IFRoZSB3 b3JrIGhlcmUgaXMgdGhlIHNhbWUgKElNTykgYXMgd2hhdCBpcyB0YWtpbmcgcGxhY2UgaW4NCj4+ Pj4+Pj4+Pj4+Pj4gTUFORVQuIEkgd291bGQgdm90ZSB0aGF0IHRoaXMgd29yayBiZSB0YWtlbiB1 cCBpbiBNQU5FVC4NCj4+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+Pj4gU3Rh biwNCj4+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pj4+IFRoYW5rIHlvdSBmb3IgdGhlIG9mZmVyLiAg SSBjb25zaWRlcmVkIHRoaXMgb2ZmZXIgc2luY2Ugc29tZQ0KPj4+Pj4+Pj4+Pj4+IHRpbWUuDQo+ Pj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4+PiBJIHRyeSB0byB1bmRlcnN0YW5kIHdoZXRoZXIgc29t ZSBvZiB0aGVzZSBpdGVtcyBvbiB3aGljaCBJDQo+Pj4+Pj4+Pj4+Pj4gaGF2ZSBpbnRlcmVzdCBj b3VsZCBiZSBicm91Z2h0IGluIGluIE1BTkVUDQo+Pj4+Pj4+Pj4+Pj4gV0c6IC0gVjJWIHVzaW5n IHByZWZpeCBleGNoYW5nZSAtIFZJTi1iYXNlZCBJUCBhZGRyZXNzaW5nDQo+Pj4+Pj4+Pj4+Pj4g c2NoZW1lIC0gTkQgUHJlZml4IERlbGVnYXRpb24gLSBQTUlQLWJhc2VkIG5ldHdvcmsgbW9iaWxp dHkNCj4+Pj4+Pj4+Pj4+PiAtIElQdjYgc2luZ2xlLWFkZHJlc3MgY29ubmVjaW9uICdzaGFyaW5n JyB3aXRoIGEgY2VsbHVsYXINCj4+Pj4+Pj4+Pj4+PiBvcGVyYXRvciBhbmQgYSB2ZWhpY3VsYXIg bW92aW5nIG5ldHdvcmsgICh0eXBlICc2NHNoYXJlJyBvZg0KPj4+Pj4+Pj4+Pj4+IHY2b3BzKS4g LSBEZWZhdWx0IFJvdXRlIHdpdGggREhDUHY2Lg0KPj4+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+Pj4g UGxlYXNlIGxldCBtZSBrbm93Lg0KPj4+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+Pj4gWW91cnMsDQo+ Pj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4+PiBBbGV4DQo+Pj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4+ Pj4NCj4+Pj4+Pj4+Pj4+Pj4gUmVnYXJkcywgU3Rhbg0KPj4+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+ Pj4+PiBPbiBKYW4gMjYsIDIwMTMsIGF0IDk6MzQgQU0sIEFiZHVzc2FsYW0gQmFyeXVuDQo+Pj4+ Pj4+Pj4+Pj4+IHdyb3RlOg0KPj4+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pj4+Pj4gSGkgTmFiaWws DQo+Pj4+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pj4+Pj4gSSB0aGluayB3ZSBhbHJlYWR5IGRvbmUg c29tZSBzdGVwcyBidXQgbm90IHN1cmUgaG93IGZhcg0KPj4+Pj4+Pj4+Pj4+Pj4gbm93LiBXZSB3 aWxsIG5lZWQgdG8gcHJvcG9zZSB0aGUgV0cgYW5kIHByb3ZpZGUgdGhlIFdHDQo+Pj4+Pj4+Pj4+ Pj4+PiBjaGFydGVyLCBhcyB1c2UgY2FzZXMgYW5kIHdvcmsgdG8gYmUgZG9uZSBpbiB0aGlzIGdy b3VwLg0KPj4+Pj4+Pj4+Pj4+Pj4gVGhpcyBjaGFydGVyIG5lZWRzIHRvIGJlIGFwcHJvdmVkIGJ5 IHRoZSBJRVNHLiBJIGhhdmUgbm90DQo+Pj4+Pj4+Pj4+Pj4+PiBhdHRlbmRlZCB0aGUgbGFzdCBt ZWV0aW5nIHNvIG5vdCBzdXJlIGFib3V0IHRoZSBzdGF0dXMNCj4+Pj4+Pj4+Pj4+Pj4+IG5vdywN Cj4+Pj4+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+Pj4+PiBBQg0KPj4+Pj4+Pj4+Pj4+Pj4NCj4+Pj4+ Pj4+Pj4+Pj4+IE9uIDEvMjYvMTMsIE5hYmlsIEJlbmFtYXINCj4+Pj4+Pj4+Pj4+Pj4+IDxiZW5h bWFyNzNAZ21haWwuY29tPiB3cm90ZToNCj4+Pj4+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pj4+Pj4+ IEhpIEFsbCwNCj4+Pj4+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pj4+Pj4+IEknbSBzdGlsbCBpbnRl cmVzdGVkIGluIHRoaXMgbGlzdCBhbmQgd2FudCB0byBqb2luIHZvaWNlcw0KPj4+Pj4+Pj4+Pj4+ Pj4+IHByZXZpb3VzbHkgaGVhcmQgdG8gbWFrZSBpdCBhIHdvcmtpbmcgZ3JvdXAuIFNvIHdoYXQN Cj4+Pj4+Pj4+Pj4+Pj4+PiBzaG91bGQgd2UgZXhhY3RseSBkbywgdG8gYWNoaWV2ZSB0aGlzIGdv YWwgPw0KPj4+Pj4+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4+Pj4+PiAy MDEzLzEvMjYgQWJkdXNzYWxhbSBCYXJ5dW4NCj48YWJkdXNzYWxhbWJhcnl1bkBnbWFpbC5jb20+ DQo+Pj4+Pj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4+Pj4+Pj4gSGkgQWxsLA0KPj4+Pj4+Pj4+Pj4+ Pj4+Pg0KPj4+Pj4+Pj4+Pj4+Pj4+PiBJIHdhcyBpbnRlcmVzdGVkIGluIHRoaXMgZ3JvdXAgYnV0 IG5vdCBzdXJlIHdoZXJlIGFyZSB3ZQ0KPj4+Pj4+Pj4+Pj4+Pj4+PiBzbyBmYXIuIElzIHRoZXJl IHByb2dyZXNzLCBvciBpcyB0aGVyZSBpc3N1ZXMvZWZmb3J0cw0KPj4+Pj4+Pj4+Pj4+Pj4+PiB0 aGF0IG5lZWQgdG8gYmUgY29tcGxldGVkIGFuZCB2b2x1bnRlZXJlZC4NCj4+Pj4+Pj4+Pj4+Pj4+ Pj4NCj4+Pj4+Pj4+Pj4+Pj4+Pj4gQUINCj4+Pj4+Pj4+Pj4+Pj4+Pj4NCj5fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4+Pg0KPj4gaXRzIG1haWxpbmcg bGlzdCBpdHNAaWV0Zi5vcmcNCj4+Pj4+Pj4+Pj4+Pj4+Pj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcv bWFpbG1hbi9saXN0aW5mby9pdHMNCj4+Pj4+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pj4+Pj4+DQo+ Pj4+Pj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4+Pj4+PiAtLSAqICogKtiq2K3Zitin2KrZiiDYjCAq KkNvcmRpYWxlbWVudCwgUmVnYXJkcyogKiAqDQo+Pj4+Pj4+Pj4+Pj4+Pj4gKiAqICrZhtio2YrZ hCDYqNmG2LnZhdix2YggTmFiaWwgQmVuYW1hciogUHJvZmVzc29yIG9mIGNvbXB1dGVyDQo+Pj4+ Pj4+Pj4+Pj4+Pj4gc2NpZW5jZXMgU2ltdWxhdGlvbiBhbmQgTW9kZWxpc2F0aW9uIExhYm9yYXRv cnkgSHVtYW4NCj4+Pj4+Pj4+Pj4+Pj4+PiBTY2llbmNlcyBGYWN1bHR5IG9mIE1la25lcyBNb3Vs YXkgSXNtYWlsKiAqVW5pdmVyc2l0eSoNCj4+Pj4+Pj4+Pj4+Pj4+PiBNZWtuZXMsIE1vcm9jY28N Cj4+Pj4+Pj4+Pj4+Pj4+PiAqR1NNOiAqICorIDIxMiA2IDcwODMyMjM2IGh0dHA6Ly9uYWJpbGJl bmFtYXIuY29tLw0KPj4+Pj4+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+Pj4+Pj4gKg0KPj4+Pj4+Pj4+ Pj4+Pj4+DQo+Pj4+Pj4+Pj4+Pj4+Pj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+Pj4+Pj4+Pj4+Pj4+Pj4gLS0tDQo+PiAtLQ0KPj4+ PiAtLS0tLS0tLS0tLS0tLS0tLS0NCj4+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+ICoNCj4+Pj4+Pj4+ Pj4+Pj4+DQo+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N Cj4+IGl0cyBtYWlsaW5nIGxpc3QgaXRzQGlldGYub3JnDQo+Pj4+Pj4+Pj4+Pj4+PiBodHRwczov L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2l0cw0KPj4+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+ Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pj4+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fXw0KPj4+Pj4+Pj4+Pj4+PiBpdHMgbWFpbGluZyBsaXN0IGl0c0BpZXRmLm9y Zw0KPj4+Pj4+Pj4+Pj4+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2l0 cw0KPj4+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4+PiBfX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4+Pj4+Pj4+Pj4+IGl0cyBtYWls aW5nIGxpc3QgaXRzQGlldGYub3JnDQo+Pj4+Pj4+Pj4+Pj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcv bWFpbG1hbi9saXN0aW5mby9pdHMNCj4+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+ Pj4NCj4+Pj4+Pj4+Pj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fIGl0cw0KPm1haWxpbmcNCj4+Pj4+Pj4+Pj4+IGxpc3QgaXRzQGlldGYub3JnIGh0dHBz Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaXRzDQo+Pj4+Pj4+Pj4+IF9fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fIGl0cw0KPm1haWxpbmcNCj4+ Pj4+Pj4+Pj4gbGlzdCBpdHNAaWV0Zi5vcmcgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s aXN0aW5mby9pdHMNCj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4gX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18gaXRzDQo+bWFpbGluZw0KPj4+Pj4+ Pj4+IGxpc3QgaXRzQGlldGYub3JnIGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGlu Zm8vaXRzDQo+Pj4+Pj4+Pg0KPj4+Pj4+Pj4NCj4+Pj4+Pj4+DQo+Pj4+Pj4+PiBfX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXyBpdHMNCj5tYWlsaW5nIGxpc3QN Cj4+Pj4+Pj4+IGl0c0BpZXRmLm9yZyBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3Rp bmZvL2l0cw0KPj4+Pj4+Pg0KPj4+Pj4+Pg0KPj4+Pj4+PiBfX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fXyBpdHMNCj5tYWlsaW5nIGxpc3QNCj4+Pj4+Pj4gaXRz QGlldGYub3JnIGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaXRzDQo+Pg0K Pj4NCj4+IC0tLQ0KPj4gQ2UgY291cnJpZXIgw6lsZWN0cm9uaXF1ZSBuZSBjb250aWVudCBhdWN1 biB2aXJ1cyBvdSBsb2dpY2llbCBtYWx2ZWlsbGFudCBwYXJjZQ0KPnF1ZSBsYSBwcm90ZWN0aW9u IGF2YXN0ISBBbnRpdmlydXMgZXN0IGFjdGl2ZS4NCj4+IGh0dHA6Ly93d3cuYXZhc3QuY29tDQo+ Pg0KPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+ IGl0cyBtYWlsaW5nIGxpc3QNCj4+IGl0c0BpZXRmLm9yZw0KPj4gaHR0cHM6Ly93d3cuaWV0Zi5v cmcvbWFpbG1hbi9saXN0aW5mby9pdHMNCj4NCj5fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fXw0KPml0cyBtYWlsaW5nIGxpc3QNCj5pdHNAaWV0Zi5vcmcNCj5o dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2l0cw0KCgoKRGl0IGJlcmljaHQg a2FuIGluZm9ybWF0aWUgYmV2YXR0ZW4gZGllIG5pZXQgdm9vciB1IGlzIGJlc3RlbWQuIEluZGll biB1IG5pZXQgZGUgZ2VhZHJlc3NlZXJkZSBiZW50IG9mIGRpdCBiZXJpY2h0IGFidXNpZXZlbGlq ayBhYW4gdSBpcyB0b2VnZXpvbmRlbiwgd29yZHQgdSB2ZXJ6b2NodCBkYXQgYWFuIGRlIGFmemVu ZGVyIHRlIG1lbGRlbiBlbiBoZXQgYmVyaWNodCB0ZSB2ZXJ3aWpkZXJlbi4gVE5PIGFhbnZhYXJk dCBnZWVuIGFhbnNwcmFrZWxpamtoZWlkIHZvb3IgZGUgaW5ob3VkIHZhbiBkZXplIGUtbWFpbCwg ZGUgd2lqemUgd2Fhcm9wIHUgZGV6ZSBnZWJydWlrdCBlbiB2b29yIHNjaGFkZSwgdmFuIHdlbGtl IGFhcmQgb29rLCBkaWUgdmVyYmFuZCBob3VkdCBtZXQgcmlzaWNvJ3MgdmVyYm9uZGVuIGFhbiBo ZXQgZWxla3Ryb25pc2NoIHZlcnplbmRlbiB2YW4gYmVyaWNodGVuLgoKIAoKVGhpcyBtZXNzYWdl IG1heSBjb250YWluIGluZm9ybWF0aW9uIHRoYXQgaXMgbm90IGludGVuZGVkIGZvciB5b3UuIElm IHlvdSBhcmUgbm90IHRoZSBhZGRyZXNzZWUgb3IgaWYgdGhpcyBtZXNzYWdlIHdhcyBzZW50IHRv IHlvdSBieSBtaXN0YWtlLCB5b3UgYXJlIHJlcXVlc3RlZCB0byBpbmZvcm0gdGhlIHNlbmRlciBh bmQgZGVsZXRlIHRoZSBtZXNzYWdlLiBUTk8gYWNjZXB0cyBubyBsaWFiaWxpdHkgZm9yIHRoZSBj b250ZW50IG9mIHRoaXMgZS1tYWlsLCBmb3IgdGhlIG1hbm5lciBpbiB3aGljaCB5b3UgdXNlIGl0 IGFuZCBmb3IgZGFtYWdlIG9mIGFueSBraW5kIHJlc3VsdGluZyBmcm9tIHRoZSByaXNrcyBpbmhl cmVudCB0byB0aGUgZWxlY3Ryb25pYyB0cmFuc21pc3Npb24gb2YgbWVzc2FnZXMuCg== From nobody Thu May 1 09:45:56 2014 Return-Path: X-Original-To: its@ietfa.amsl.com Delivered-To: its@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C44061A08F2 for ; Thu, 1 May 2014 09:45:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.4 X-Spam-Level: X-Spam-Status: No, score=-3.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, GB_I_LETTER=-2, J_CHICKENPOX_72=0.6, SPF_PASS=-0.001] autolearn=ham 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 8VW3WDBCiU4o for ; Thu, 1 May 2014 09:45:50 -0700 (PDT) Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id DED341A073F for ; Thu, 1 May 2014 09:45:49 -0700 (PDT) Received: by mail-pd0-f175.google.com with SMTP id fp1so3330404pdb.34 for ; Thu, 01 May 2014 09:45:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=STZlin4UFQ2J3RbAWTnzLWdBS2oPPLr7lncxeIzbtAE=; b=AG0cMPAMRwUPHhWOtS+PTdWSDV200lAqeoUAOj7Swd7/40ViZUyFqe4IwrHg6b4YgQ vP1w5aXHd8bZ7LvgTc1M/SyGnxFC1eQuHJ+5M2AYe391ITngyu7/+rbCjtS+O9WVKRZe vxdQQF1ddTj7WEiKooYljl/A19hNV0NCuEwOet8CYa/L5bXfeKLjLioZqPXkfzpx/3RN BfN3jKEyGHA6iptQhG/s9A47R8V+boPtDXGE9sUzCxBKtAEVChkd3x6oyCuPbsiqs/a9 9EQox9vbh6tKNvxStEcbeUXx+y4TZoFp0oAek2P2lKAMQELzyoRIs6Q0/g/K8C2KJjGl hbmA== X-Received: by 10.66.149.7 with SMTP id tw7mr23205723pab.72.1398962747910; Thu, 01 May 2014 09:45:47 -0700 (PDT) Received: from [10.169.113.83] (71-6-80-11.static-ip.telepacific.net. [71.6.80.11]) by mx.google.com with ESMTPSA id ry8sm161409179pac.29.2014.05.01.09.45.46 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 01 May 2014 09:45:47 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Dino Farinacci In-Reply-To: <72FB622921C13746AD6349E70A8D9F307DB5492C@EXC-MBX03.tsn.tno.nl> Date: Thu, 1 May 2014 09:42:31 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <2DED53A3-5A58-4C0C-BF85-A59E00457A07@gmail.com> References: <2ED1D3801ACAAB459FDB4EAC9EAD090C0FFFE9E2@xmb-aln-x03.cisco.com> <51064E08.9020401@gmail.com> <5106619F.7020002@inria.fr> <51067D07.9020409@gmail.com> <5108E3AB.8080205@inria.fr> <5108EA48.90003@gmail.com> <5108EDAA.90700@gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA07A4E4@AZ-FFEXMB04.global.avaya.com> <5267EAFC.9090607@gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA1291358F@AZ-FFEXMB04.global.avaya.com> <53622ED2.7080605@gmail.com> <72FB622921C13746AD6349E70A8D9F307DB5492C@EXC-MBX03.tsn.tno.nl> To: "Velt, R. (Ronald) in 't" X-Mailer: Apple Mail (2.1874) Archived-At: http://mailarchive.ietf.org/arch/msg/its/2Yy4FInLTauc53Ks510VrUkp9n8 Cc: "Romascanu, Dan \(Dan\)" , Alexandru Petrescu , "its@ietf.org" Subject: Re: [geonet/its] EtherType for geonet/ITS 0x8947 reflected at IANA (was: What do we need to make ITS WG go forward? - EtherType for ITS) X-BeenThere: its@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "GeoNet BoF discussion list." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2014 16:45:52 -0000 Okay, thanks for clarification. Dino On May 1, 2014, at 9:05 AM, Velt, R. (Ronald) in 't = wrote: > Dino, >=20 >> -----Original Message----- >> From: its [mailto:its-bounces@ietf.org] On Behalf Of Dino Farinacci >> Sent: donderdag 1 mei 2014 17:26 >> To: Alexandru Petrescu >> Cc: Romascanu, Dan (Dan); its@ietf.org >> Subject: Re: [geonet/its] EtherType for geonet/ITS 0x8947 reflected = at IANA >> (was: What do we need to make ITS WG go forward? - EtherType for ITS) >>=20 >> This sounds like the cart before the horse. >>=20 >> Why does geonet have to run at the link-layer? >>=20 >> Now if you have to run any geonet protocol over a layer-3 network, = you are >> required to stretch a subnet and use layer-2 overlays. >>=20 >> Can someone justify this request? >=20 > This is the EtherType that was requested by ETSI Technical Committee = ITS for their *non-IP-based* GeoNetworking protocol, which runs over = IEEE 802.11 OCB mode (or "G5" in their parlance). It has nothing to do = (yet) with any existing or proposed IETF protocol/activity. >=20 > This action merely means that IANA's table now holds an entry that was = added to IEEE's own table early last year. >=20 > Best regards, > Ronald in 't Velt >=20 >>=20 >> Dino >>=20 >>> On May 1, 2014, at 4:24 AM, Alexandru Petrescu >> wrote: >>>=20 >>> Hello geonetters, >>>=20 >>> I would like to inform you that, following our discussions about = EtherType >> for geonet, and per my request, and per designated reviewer for this = entry - >> IANA has added an entry in the table of EtherTypes for 0x8947 for >> GeoNetworking, as to reflect the IEEE allocation of same EtherType. >>>=20 >>> http://www.iana.org/assignments/ieee-802-numbers >>>=20 >>> This is a good allocation which should help software designers in = writing >> interoperable implementations of geonetworking code over link layers = of >> type Ethernet, and in some cases, links dedicated to ITS vehicular >> communications. >>>=20 >>> Yours, >>>=20 >>> Alex >>>=20 >>>> On 23/10/2013 17:41, Romascanu, Dan (Dan) wrote: >>>> Hi Alexandru, >>>>=20 >>>> The authority for allocation is with the IEEE, and the list to be >>>> referenced and used in specifications is the one at IEEE. >>>>=20 >>>> The IANA list is informational and includes as specified on the = page >>>> 'contributed unverified information from various sources'. It would >>>> be good I think to have the new ethertype mentioned on the IANA = page >>>> as well, because some IETF-ers may go first to that list. I suggest >>>> that you just send an email to IANA asking for the change = (additional >>>> row in the table) be made according to the IEEE allocation. We can >>>> talk about this with the IANA folks in Vancouver if this is not >>>> solved until then. >>>>=20 >>>> I am not sure who needs to be asked about the linux kernel patches, = I >>>> can guess that a query to the apps-discuss@ietf.org may result on >>>> useful information from people involved with that layer. >>>>=20 >>>> I hope this helps. >>>>=20 >>>> Regards, >>>>=20 >>>> Dan >>>>=20 >>>>=20 >>>>=20 >>>>> -----Original Message----- From: Alexandru Petrescu >>>>> [mailto:alexandru.petrescu@gmail.com] Sent: Wednesday, October 23, >>>>> 2013 6:28 PM To: Romascanu, Dan (Dan); its@ietf.org Subject: Re: >>>>> [its] What do we need to make ITS WG go forward? - EtherType for = ITS >>>>>=20 >>>>> Hi Dan, >>>>>=20 >>>>> Let me bring back this topic. >>>>>=20 >>>>> Since our last discussion the EtherType for ETSI GeoNetworking >>>>> 0x8947 has been set at IEEE: >>>>> http://standards.ieee.org/develop/regauth/ethertype/eth.txt >>>>>=20 >>>>> However, it is absent at the IANA website: >>>>> http://www.iana.org/assignments/ieee-802-numbers/ieee-802- >> numbers.xm >>>>> l >>> Where should we ask at IANA about this type? >>>>>=20 >>>>> Also, this ethertype 0x8947 seems absent from the linux kernel >>>>> sources. >>>>>=20 >>>>> Where should we ask a patch? >>>>>=20 >>>>> Alex >>>>>=20 >>>>>=20 >>>>> Le 30/01/2013 11:00, Romascanu, Dan (Dan) a =C3=A9crit : >>>>>> Hi, >>>>>>=20 >>>>>> If the PDF letter is dated 1/29 (yesterday) than we may see the >>>>>> IEEE RA list updated soon. >>>>>>=20 >>>>>> There is no need for IANA to make an allocation (if we are >>>>>> discussing EtherTypes). The responsibility for EtherTypes >>>>>> assignment is with the IEEE RA and the file at IANA is only >>>>>> informational. See the note at >>>>>> http://www.iana.org/assignments/ieee-802-numbers/ieee-802- >> numbers.xml. >>>>>=20 >>> Regards, >>>>>>=20 >>>>>> Dan >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>>> -----Original Message----- From: its-bounces@ietf.org >>>>>>> [mailto:its-bounces@ietf.org] On Behalf Of Alexandru Petrescu >>>>>>> Sent: Wednesday, January 30, 2013 11:54 AM To: its@ietf.org >>>>>>> Subject: Re: [its] What do we need to make ITS WG go forward? >>>>>>> - EtherType for ITS >>>>>>>=20 >>>>>>> In private I got hold of a pdf letter from IEEE to ETSI dated >>>>>>> January 29th, 2013, which says that the EtherType is #8947. >>>>>>> (not sure hexa or decimal). >>>>>>>=20 >>>>>>> See that letter attached to this email. >>>>>>>=20 >>>>>>> One would say that things unfold as we speak. >>>>>>>=20 >>>>>>> I still think that IANA should also allocate it as well. (maybe >>>>>>> I'll get another pdf in private telling me it's already >>>>>>> done...) >>>>>>>=20 >>>>>>> Alex >>>>>>>=20 >>>>>>> Le 30/01/2013 10:39, Alexandru Petrescu a =C3=A9crit : >>>>>>>> Le 30/01/2013 10:11, Thierry Ernst a =C3=A9crit : >>>>>>>>>=20 >>>>>>>>> Alex, >>>>>>>>>=20 >>>>>>>>> IEEE have assigned Ethernet Type Field number #8947 for ITS = use >>>>>>>>> (ETSI TC ITS's GeoNetworking). Check the following document >>>>>>>>> available on the ETSI server: >>>>>>>>>=20 >>>>>>>>> ITS(13)000020 >>>>>>>>> > CONTRIBUTIONS/2013/ITS%2813%2 >>>>>>>>> 900 >>> 00 >>>>> 20_Ethernet_Type_Field_number_for_GeoNetworking.pdf> >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> Ethernet Type Field number for GeoNetworking >>>>>>>>> http://docbox.etsi.org/ITS/ITS/05- >> CONTRIBUTIONS/2013/ITS(13)0000 >>>>>>>>> 20_ >>> Et >>>>> hernet_Type_Field_number_for_GeoNetworking.pdf >>>>>>>>=20 >>>>>>>> Thierry, >>>>>>>>=20 >>>>>>>> I >>>>>>>> may be wrong, but here are my thoughts. >>>>>>>>=20 >>>>>>>> I am trying to access these URLs you provide above but they are >>>>>>>> password protected. What is the username and password? >>>>>>>>=20 >>>>>>>> The URL indicates ETSI, not IEEE. >>>>>>>>=20 >>>>>>>> The IEEE URL for EtherTypes is the following, I believe: >>>>>>>> http://standards.ieee.org/develop/regauth/ethertype/eth.txt >>>>>>>>=20 >>>>>>>> That eth.txt file does not contain 0707 nor 8947. But it does >>>>>>>> contain, for example 86DD which is 'IPv6'. >>>>>>>>=20 >>>>>>>> The 0x0707 EtherType is present in an implementation which is >>>>>>>> supposed compliant with ETSI ITS (plugtests). Wireshark dump >>>>>>>> available upon request. >>>>>>>>=20 >>>>>>>> Besides, if this is to be about IPv6, I think it should be >>>>>>>> reserved at IANA as well, in addition to reserving it at IEEE. >>>>>>>> The IANA URL for IEEE 802 Numbers is at: >>>>>>>> http://www.iana.org/assignments/ieee-802-numbers/ieee-802- >> numbers >>>>>>>> .xm >>> l >>>>> (the #8947 that you mention above does not seem to figure in this >>>>>>>> IANA URL). >>>>>>>>=20 >>>>>>>> This is why I believe this number should be reserved both as an >>>>>>>> EtherType at IEEE and at IANA. >>>>>>>>=20 >>>>>>>> Yours, >>>>>>>>=20 >>>>>>>> Alex >>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> Regards, Thierry. >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>> On 28/01/13 14:28, Alexandru Petrescu wrote: >>>>>>>>>> Le 28/01/2013 14:16, Joe Klein a =C3=A9crit : >>>>>>>>>>> I really dislike the fact that ISO is charging for the ISO >>>>>>>>>>> 21217 - Architecture & ISO 21210 - IPv6 Networking. >>>>>>>>>>>=20 >>>>>>>>>>> Does this make it any better? Safer? Should ISO now have >>>>>>>>>>> cybersecurity and safety liability if the specification = leads >>>>>>>>>>> to deaths and damage to property? >>>>>>>>>>=20 >>>>>>>>>> Does it make any better interoperable as well? >>>>>>>>>>=20 >>>>>>>>>> EtherType 0x0707 described in ITS documents, implemented, but >>>>>>>>>> not specified by IEEE nor reserved at IANA - does not make it >>>>>>>>>> interoperable. >>>>>>>>>>=20 >>>>>>>>>> One wouldn't think that this 0x0707 ethertype be reserved by >>>>>>>>>> somebody who is not IANA nor IEEE? >>>>>>>>>>=20 >>>>>>>>>> (see a good example of interoperability: IPv6 0x86dd = ethertype >>>>>>>>>> is reserved at IEEE and at IANA >>>>>>>>>> http://www.iana.org/assignments/ieee-802-numbers/ieee-802- >> numbers. >>> xm >>>>> l) >>>>>>>>=20 >>>>>>> Alex >>>>>>>>>>=20 >>>>>>>>>> Or should these standards remain in >>>>>>>>>>> the public domain, for researches to review and validate? >>>>>>>>>>>=20 >>>>>>>>>>> Just my 2 cents. >>>>>>>>>>>=20 >>>>>>>>>>> Joe >>>>>>>>>>>=20 >>>>>>>>>>>=20 >>>>>>>>>>>=20 >>>>>>>>>>> On Mon, Jan 28, 2013 at 6:31 AM, Thierry Ernst >>>>>>>>>>> wrote: >>>>>>>>>>>>=20 >>>>>>>>>>>> Dear all, >>>>>>>>>>>>=20 >>>>>>>>>>>> At this stage, I don't think a new working group is needed. >>>>>>>>>>>> First, it would need a charter, and support from the >>>>>>>>>>>> industry. But more importantly, IETF WGs are not usually >>>>>>>>>>>> sector-driven, so it means the different issues pertaining = to >>>>>>>>>>>> ITS should be brought to VARIOUS existing WGs, and a WG >>>>>>>>>>>> should only be created if there is an important issue for >>>>>>>>>>>> which there is no existing WG that could work on it. >>>>>>>>>>>>=20 >>>>>>>>>>>> This said, as mentioned earlier, ITS is not only about >>>>>>>>>>>> vehicular communications, though the issues listed by >>>>>>>>>>>> Alexandru below mostly consider vehicular communications. >>>>>>>>>>>>=20 >>>>>>>>>>>> What ITS really needs is the definition of a common >>>>>>>>>>>> communication architecture and the definition of what >>>>>>>>>>>> features should be comprised for an IPv6 networking stack >>>>>>>>>>>> deployed for ITS use cases. This cannot be done at IETF, = and >>>>>>>>>>>> actually already exists at ISO: - ISO >>>>>>>>>>>> 21217 - Architecture - ISO 21210 - IPv6 Networking >>>>>>>>>>>>=20 >>>>>>>>>>>> As an input to the discussion, please consider reading >>>>>>>>>>>> documents D2.1 and D2.2 available on the >>>>>>>>>>>> ITSSv6 project web page: >>>>>>>>>>>> http://www.itssv6.eu/documentation/ D2.2 provides an = analysis >>>>>>>>>>>> of the currently published version of ISO 21210, but new = work >>>>>>>>>>>> items have been launched since then to address remaining >>>>>>>>>>>> issues. >>>>>>>>>>>>=20 >>>>>>>>>>>> Regards, Thierry. >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>>> On 28/01/13 11:08, Alexandru Petrescu wrote: >>>>>>>>>>>>>=20 >>>>>>>>>>>>> Le 28/01/2013 05:02, Stan Ratliff (sratliff) a =C3=A9crit = : >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> All, >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> This is just one opinion, but I'd like to understand why >>>>>>>>>>>>>> ITS would need its own IETF group. >>>>>>>>>>>>>> The work here is the same (IMO) as what is taking place = in >>>>>>>>>>>>>> MANET. I would vote that this work be taken up in MANET. >>>>>>>>>>>>>=20 >>>>>>>>>>>>>=20 >>>>>>>>>>>>> Stan, >>>>>>>>>>>>>=20 >>>>>>>>>>>>> Thank you for the offer. I considered this offer since = some >>>>>>>>>>>>> time. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> I try to understand whether some of these items on which I >>>>>>>>>>>>> have interest could be brought in in MANET >>>>>>>>>>>>> WG: - V2V using prefix exchange - VIN-based IP addressing >>>>>>>>>>>>> scheme - ND Prefix Delegation - PMIP-based network = mobility >>>>>>>>>>>>> - IPv6 single-address connecion 'sharing' with a cellular >>>>>>>>>>>>> operator and a vehicular moving network (type '64share' = of >>>>>>>>>>>>> v6ops). - Default Route with DHCPv6. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> Please let me know. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> Yours, >>>>>>>>>>>>>=20 >>>>>>>>>>>>> Alex >>>>>>>>>>>>>=20 >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> Regards, Stan >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> On Jan 26, 2013, at 9:34 AM, Abdussalam Baryun >>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> Hi Nabil, >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> I think we already done some steps but not sure how far >>>>>>>>>>>>>>> now. We will need to propose the WG and provide the WG >>>>>>>>>>>>>>> charter, as use cases and work to be done in this group. >>>>>>>>>>>>>>> This charter needs to be approved by the IESG. I have = not >>>>>>>>>>>>>>> attended the last meeting so not sure about the status >>>>>>>>>>>>>>> now, >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> AB >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> On 1/26/13, Nabil Benamar >>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>> Hi All, >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>> I'm still interested in this list and want to join = voices >>>>>>>>>>>>>>>> previously heard to make it a working group. So what >>>>>>>>>>>>>>>> should we exactly do, to achieve this goal ? >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>> 2013/1/26 Abdussalam Baryun >> >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>> Hi All, >>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>> I was interested in this group but not sure where are = we >>>>>>>>>>>>>>>>> so far. Is there progress, or is there issues/efforts >>>>>>>>>>>>>>>>> that need to be completed and volunteered. >>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>> AB >>>>>>>>>>>>>>>>>=20 >> _______________________________________________ >>>>>=20 >>> its mailing list its@ietf.org >>>>>>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>> -- * * *=D8=AA=D8=AD=D9=8A=D8=A7=D8=AA=D9=8A =D8=8C = **Cordialement, Regards* * * >>>>>>>>>>>>>>>> * * *=D9=86=D8=A8=D9=8A=D9=84 =D8=A8=D9=86=D8=B9=D9=85=D8= =B1=D9=88 Nabil Benamar* Professor of computer >>>>>>>>>>>>>>>> sciences Simulation and Modelisation Laboratory Human >>>>>>>>>>>>>>>> Sciences Faculty of Meknes Moulay Ismail* *University* >>>>>>>>>>>>>>>> Meknes, Morocco >>>>>>>>>>>>>>>> *GSM: * *+ 212 6 70832236 http://nabilbenamar.com/ >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>> * >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>> = --------------------------------------------------------- >>>>>>>>>>>>>>>> --- >>> -- >>>>> ------------------ >>>>>>>>>>>>>=20 >>>>>>>>>> * >>>>>>>>>>>>>>>=20 >> _______________________________________________ >>> its mailing list its@ietf.org >>>>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> its mailing list its@ietf.org >>>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>>>>>>>>>=20 >>>>>>>>>>>>>=20 >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> its mailing list its@ietf.org >>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>> _______________________________________________ its >> mailing >>>>>>>>>>>> list its@ietf.org https://www.ietf.org/mailman/listinfo/its >>>>>>>>>>> _______________________________________________ its >> mailing >>>>>>>>>>> list its@ietf.org https://www.ietf.org/mailman/listinfo/its >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>> _______________________________________________ its >> mailing >>>>>>>>>> list its@ietf.org https://www.ietf.org/mailman/listinfo/its >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> _______________________________________________ its >> mailing list >>>>>>>>> its@ietf.org https://www.ietf.org/mailman/listinfo/its >>>>>>>>=20 >>>>>>>>=20 >>>>>>>> _______________________________________________ its >> mailing list >>>>>>>> its@ietf.org https://www.ietf.org/mailman/listinfo/its >>>=20 >>>=20 >>> --- >>> Ce courrier =C3=A9lectronique ne contient aucun virus ou logiciel = malveillant parce >> que la protection avast! Antivirus est active. >>> http://www.avast.com >>>=20 >>> _______________________________________________ >>> its mailing list >>> its@ietf.org >>> https://www.ietf.org/mailman/listinfo/its >>=20 >> _______________________________________________ >> its mailing list >> its@ietf.org >> https://www.ietf.org/mailman/listinfo/its >=20 >=20 >=20 > Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien = u niet de geadresseerde bent of dit bericht abusievelijk aan u is = toegezonden, wordt u verzocht dat aan de afzender te melden en het = bericht te verwijderen. TNO aanvaardt geen aansprakelijkheid voor de = inhoud van deze e-mail, de wijze waarop u deze gebruikt en voor schade, = van welke aard ook, die verband houdt met risico's verbonden aan het = elektronisch verzenden van berichten. >=20 >=20 >=20 > This message may contain information that is not intended for you. If = you are not the addressee or if this message was sent to you by mistake, = you are requested to inform the sender and delete the message. TNO = accepts no liability for the content of this e-mail, for the manner in = which you use it and for damage of any kind resulting from the risks = inherent to the electronic transmission of messages. From nobody Fri May 2 01:43:27 2014 Return-Path: X-Original-To: its@ietfa.amsl.com Delivered-To: its@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AFA81A0A7F for ; Fri, 2 May 2014 01:43:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham 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 ftN3tBaEZTL4 for ; Fri, 2 May 2014 01:43:23 -0700 (PDT) Received: from out42-ams.mf.surf.net (out42-ams.mf.surf.net [145.0.1.42]) by ietfa.amsl.com (Postfix) with ESMTP id 145731A0371 for ; Fri, 2 May 2014 01:43:22 -0700 (PDT) Received: from EXEDGE02.ad.utwente.nl (exedge02.ad.utwente.nl [130.89.5.49]) by outgoing2-ams.mf.surf.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id s428hIUf029079; Fri, 2 May 2014 10:43:18 +0200 Received: from EXHUB01.ad.utwente.nl (130.89.4.228) by EXEDGE02.ad.utwente.nl (130.89.5.49) with Microsoft SMTP Server (TLS) id 14.3.181.6; Fri, 2 May 2014 10:43:24 +0200 Received: from EXMBX23.ad.utwente.nl ([169.254.3.47]) by EXHUB01.ad.utwente.nl ([130.89.4.228]) with mapi id 14.03.0181.006; Fri, 2 May 2014 10:43:18 +0200 From: To: Thread-Topic: [geonet/its] minutes of the 'geonet' meeting in London IETF89 Thread-Index: AQHPPTTkurza8oDpb0CGflOo8FdR8Zrb/BMAgFFNeRM= Date: Fri, 2 May 2014 08:43:17 +0000 Message-ID: References: <531F1B5A.70107@gmail.com>, <25E2FC42-6C9C-41F7-8433-E94B902EADBD@gmail.com> In-Reply-To: <25E2FC42-6C9C-41F7-8433-E94B902EADBD@gmail.com> Accept-Language: nl-NL, en-US Content-Language: nl-NL X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [86.91.134.3] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Bayes-Prob: 0.0001 (Score 0, tokens from: utwente-out:default, base:default, @@RPTN) X-CanIt-Geo: ip=130.89.5.49; country=NL; region=Provincie Overijssel; city=Enschede; latitude=52.2195; longitude=6.8912; http://maps.google.com/maps?q=52.2195,6.8912&z=6 X-CanItPRO-Stream: utwente-out:default (inherits from utwente:default, base:default) X-Canit-Stats-ID: 0vLUUHixA - d674f187f713 - 20140502 (trained as not-spam) X-Scanned-By: CanIt (www . roaringpenguin . com) Archived-At: http://mailarchive.ietf.org/arch/msg/its/MtySel1FMSI8fresHOEw9nbnZ9g Cc: alexandru.petrescu@gmail.com, farinacci@gmail.com Subject: Re: [geonet/its] minutes of the 'geonet' meeting in London IETF89 X-BeenThere: its@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "GeoNet BoF discussion list." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 May 2014 08:43:25 -0000 Dear all, Please note that I have started working on the geonet problem statement dra= ft. For the ones that have not send the information discussed/agreed during the= 'geonet' meeting in London IETF89, can you please do that asap! Dino, thank you very much! Best regards, Georgios ________________________________________ Van: its [its-bounces@ietf.org] namens Dino Farinacci [farinacci@gmail.com] Verzonden: dinsdag 11 maart 2014 17:04 Aan: Alexandru Petrescu CC: its@ietf.org Onderwerp: Re: [geonet/its] minutes of the 'geonet' meeting in London IETF8= 9 > Drafts on use-cases have to be written and volunteers for writing them > are about to be identified (Dino said he'd be interested). Here is a description of the use-case I gave verbally at the ad-hoc get tog= ether. It was labeled by Alex as "the Shell case". This was a requirement f= rom the oiler riggers in Texas. (1) The oil companies want to track employees in the field. The conditions = can be dangerous so they want to verify their safety. (2) They are each equipped with a mobile device. (3) The management knows their phone numbers but needs to send packets to t= hose phone numbers. We (cisco), suggested that that register E.164 telephon= e numbers as EIDs in the LISP mapping database. When a lookup is performed,= what is returned is an RLOC-record which contains the IP address of the mo= bile device. (4) Adding geonet specific mechnanisms to this use-case, say an oil rigger = explodes. They wan to send recovery instructions to all E.164 addresses in = the geo radius of the explosion. (5) So you store in the LISP mapping database the geo-coordinates of the po= int of explosion with say a radius value of 1 mile. All EIDs that are in th= e circle of geography are notified. That is each E.164 address (or IP addre= ss) of the mobile device is registered with the circle EID. (6) Management detects explosion and sends packet to each IP address that i= s in the mapping database record for the circule EID as the key to the look= up. Dino _______________________________________________ its mailing list its@ietf.org https://www.ietf.org/mailman/listinfo/its= From nobody Fri May 2 08:15:07 2014 Return-Path: X-Original-To: its@ietfa.amsl.com Delivered-To: its@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 805791A6F27 for ; Fri, 2 May 2014 08:15:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.383 X-Spam-Level: X-Spam-Status: No, score=-6.383 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, GB_I_LETTER=-2, HELO_EQ_FR=0.35, J_CHICKENPOX_72=0.6, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham 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 RWDovGuZCg9b for ; Fri, 2 May 2014 08:15:02 -0700 (PDT) Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) by ietfa.amsl.com (Postfix) with ESMTP id 817641A0A0D for ; Fri, 2 May 2014 08:15:01 -0700 (PDT) Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id s42FEsxE031161; Fri, 2 May 2014 17:14:54 +0200 Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 6FC1F201F55; Fri, 2 May 2014 17:15:30 +0200 (CEST) Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 5E66F201E05; Fri, 2 May 2014 17:15:30 +0200 (CEST) Received: from [127.0.0.1] ([132.166.86.13]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id s42FEnvT031365; Fri, 2 May 2014 17:14:54 +0200 Message-ID: <5363B669.5050708@gmail.com> Date: Fri, 02 May 2014 17:14:49 +0200 From: Alexandru Petrescu User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "Velt, R. (Ronald) in 't" , Dino Farinacci References: <2ED1D3801ACAAB459FDB4EAC9EAD090C0FFFE9E2@xmb-aln-x03.cisco.com> <51064E08.9020401@gmail.com> <5106619F.7020002@inria.fr> <51067D07.9020409@gmail.com> <5108E3AB.8080205@inria.fr> <5108EA48.90003@gmail.com> <5108EDAA.90700@gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA07A4E4@AZ-FFEXMB04.global.avaya.com> <5267EAFC.9090607@gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA1291358F@AZ-FFEXMB04.global.avaya.com> <53622ED2.7080605@gmail.com> <72FB622921C13746AD6349E70A8D9F307DB5492C@EXC-MBX03.tsn.tno.nl> In-Reply-To: <72FB622921C13746AD6349E70A8D9F307DB5492C@EXC-MBX03.tsn.tno.nl> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Archived-At: http://mailarchive.ietf.org/arch/msg/its/EKhB8Y_HaHiTIoyKBSk0ADD0TaE Cc: "Romascanu, Dan \(Dan\)" , "its@ietf.org" Subject: Re: [geonet/its] EtherType for geonet/ITS 0x8947 reflected at IANA X-BeenThere: its@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "GeoNet BoF discussion list." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 May 2014 15:15:05 -0000 Le 01/05/2014 18:05, Velt, R. (Ronald) in 't a écrit : > Dino, > >> -----Original Message----- From: its [mailto:its-bounces@ietf.org] >> On Behalf Of Dino Farinacci Sent: donderdag 1 mei 2014 17:26 To: >> Alexandru Petrescu Cc: Romascanu, Dan (Dan); its@ietf.org Subject: >> Re: [geonet/its] EtherType for geonet/ITS 0x8947 reflected at IANA >> (was: What do we need to make ITS WG go forward? - EtherType for >> ITS) >> >> This sounds like the cart before the horse. >> >> Why does geonet have to run at the link-layer? >> >> Now if you have to run any geonet protocol over a layer-3 network, >> you are required to stretch a subnet and use layer-2 overlays. >> >> Can someone justify this request? > > This is the EtherType that was requested by ETSI Technical Committee > ITS for their *non-IP-based* GeoNetworking protocol, which runs over > IEEE 802.11 OCB mode (or "G5" in their parlance). It has nothing to > do (yet) with any existing or proposed IETF protocol/activity. Yes, I agree. This ethertype is for ETSI Geonetworking, which is a different thing than 'geonet' as we do at IETF. (yet or never). We can very well come up with a geonet protocol that is not necessarily related to ETSI GEonetworking: it may run on G5 and other links, it may run at layer 7 and not layer 3, it may be IP-based, and so on. Where geonet runs is what we have to clarify in the Charter right now. Alex > > This action merely means that IANA's table now holds an entry that > was added to IEEE's own table early last year. > > Best regards, Ronald in 't Velt > >> >> Dino >> >>> On May 1, 2014, at 4:24 AM, Alexandru Petrescu >> wrote: >>> >>> Hello geonetters, >>> >>> I would like to inform you that, following our discussions about >>> EtherType >> for geonet, and per my request, and per designated reviewer for >> this entry - IANA has added an entry in the table of EtherTypes for >> 0x8947 for GeoNetworking, as to reflect the IEEE allocation of same >> EtherType. >>> >>> http://www.iana.org/assignments/ieee-802-numbers >>> >>> This is a good allocation which should help software designers in >>> writing >> interoperable implementations of geonetworking code over link >> layers of type Ethernet, and in some cases, links dedicated to ITS >> vehicular communications. >>> >>> Yours, >>> >>> Alex >>> >>>> On 23/10/2013 17:41, Romascanu, Dan (Dan) wrote: Hi Alexandru, >>>> >>>> The authority for allocation is with the IEEE, and the list to >>>> be referenced and used in specifications is the one at IEEE. >>>> >>>> The IANA list is informational and includes as specified on the >>>> page 'contributed unverified information from various sources'. >>>> It would be good I think to have the new ethertype mentioned on >>>> the IANA page as well, because some IETF-ers may go first to >>>> that list. I suggest that you just send an email to IANA asking >>>> for the change (additional row in the table) be made according >>>> to the IEEE allocation. We can talk about this with the IANA >>>> folks in Vancouver if this is not solved until then. >>>> >>>> I am not sure who needs to be asked about the linux kernel >>>> patches, I can guess that a query to the apps-discuss@ietf.org >>>> may result on useful information from people involved with that >>>> layer. >>>> >>>> I hope this helps. >>>> >>>> Regards, >>>> >>>> Dan >>>> >>>> >>>> >>>>> -----Original Message----- From: Alexandru Petrescu >>>>> [mailto:alexandru.petrescu@gmail.com] Sent: Wednesday, >>>>> October 23, 2013 6:28 PM To: Romascanu, Dan (Dan); >>>>> its@ietf.org Subject: Re: [its] What do we need to make ITS >>>>> WG go forward? - EtherType for ITS >>>>> >>>>> Hi Dan, >>>>> >>>>> Let me bring back this topic. >>>>> >>>>> Since our last discussion the EtherType for ETSI >>>>> GeoNetworking 0x8947 has been set at IEEE: >>>>> http://standards.ieee.org/develop/regauth/ethertype/eth.txt >>>>> >>>>> However, it is absent at the IANA website: >>>>> http://www.iana.org/assignments/ieee-802-numbers/ieee-802- >> numbers.xm >>>>> l >>> Where should we ask at IANA about this type? >>>>> >>>>> Also, this ethertype 0x8947 seems absent from the linux >>>>> kernel sources. >>>>> >>>>> Where should we ask a patch? >>>>> >>>>> Alex >>>>> >>>>> >>>>> Le 30/01/2013 11:00, Romascanu, Dan (Dan) a écrit : >>>>>> Hi, >>>>>> >>>>>> If the PDF letter is dated 1/29 (yesterday) than we may see >>>>>> the IEEE RA list updated soon. >>>>>> >>>>>> There is no need for IANA to make an allocation (if we are >>>>>> discussing EtherTypes). The responsibility for EtherTypes >>>>>> assignment is with the IEEE RA and the file at IANA is >>>>>> only informational. See the note at >>>>>> http://www.iana.org/assignments/ieee-802-numbers/ieee-802- >> numbers.xml. >>>>> >>> Regards, >>>>>> >>>>>> Dan >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> -----Original Message----- From: its-bounces@ietf.org >>>>>>> [mailto:its-bounces@ietf.org] On Behalf Of Alexandru >>>>>>> Petrescu Sent: Wednesday, January 30, 2013 11:54 AM To: >>>>>>> its@ietf.org Subject: Re: [its] What do we need to make >>>>>>> ITS WG go forward? - EtherType for ITS >>>>>>> >>>>>>> In private I got hold of a pdf letter from IEEE to ETSI >>>>>>> dated January 29th, 2013, which says that the EtherType >>>>>>> is #8947. (not sure hexa or decimal). >>>>>>> >>>>>>> See that letter attached to this email. >>>>>>> >>>>>>> One would say that things unfold as we speak. >>>>>>> >>>>>>> I still think that IANA should also allocate it as well. >>>>>>> (maybe I'll get another pdf in private telling me it's >>>>>>> already done...) >>>>>>> >>>>>>> Alex >>>>>>> >>>>>>> Le 30/01/2013 10:39, Alexandru Petrescu a écrit : >>>>>>>> Le 30/01/2013 10:11, Thierry Ernst a écrit : >>>>>>>>> >>>>>>>>> Alex, >>>>>>>>> >>>>>>>>> IEEE have assigned Ethernet Type Field number #8947 >>>>>>>>> for ITS use (ETSI TC ITS's GeoNetworking). Check the >>>>>>>>> following document available on the ETSI server: >>>>>>>>> >>>>>>>>> ITS(13)000020 > CONTRIBUTIONS/2013/ITS%2813%2 >>>>>>>>> 900 >>> 00 >>>>> 20_Ethernet_Type_Field_number_for_GeoNetworking.pdf> >>>>>>>>> >>>>>>>>> >>>>>>>>> Ethernet Type Field number for GeoNetworking >>>>>>>>> http://docbox.etsi.org/ITS/ITS/05- >> CONTRIBUTIONS/2013/ITS(13)0000 >>>>>>>>> 20_ >>> Et >>>>> hernet_Type_Field_number_for_GeoNetworking.pdf >>>>>>>> >>>>>>>> Thierry, >>>>>>>> >>>>>>>> I may be wrong, but here are my thoughts. >>>>>>>> >>>>>>>> I am trying to access these URLs you provide above but >>>>>>>> they are password protected. What is the username and >>>>>>>> password? >>>>>>>> >>>>>>>> The URL indicates ETSI, not IEEE. >>>>>>>> >>>>>>>> The IEEE URL for EtherTypes is the following, I >>>>>>>> believe: >>>>>>>> http://standards.ieee.org/develop/regauth/ethertype/eth.txt >>>>>>>> >>>>>>>> >>>>>>>> That eth.txt file does not contain 0707 nor 8947. But it does >>>>>>>> contain, for example 86DD which is 'IPv6'. >>>>>>>> >>>>>>>> The 0x0707 EtherType is present in an implementation >>>>>>>> which is supposed compliant with ETSI ITS (plugtests). >>>>>>>> Wireshark dump available upon request. >>>>>>>> >>>>>>>> Besides, if this is to be about IPv6, I think it should >>>>>>>> be reserved at IANA as well, in addition to reserving >>>>>>>> it at IEEE. The IANA URL for IEEE 802 Numbers is at: >>>>>>>> http://www.iana.org/assignments/ieee-802-numbers/ieee-802- >> >>>>>>>> numbers >>>>>>>> .xm >>> l >>>>> (the #8947 that you mention above does not seem to figure in >>>>> this >>>>>>>> IANA URL). >>>>>>>> >>>>>>>> This is why I believe this number should be reserved >>>>>>>> both as an EtherType at IEEE and at IANA. >>>>>>>> >>>>>>>> Yours, >>>>>>>> >>>>>>>> Alex >>>>>>>> >>>>>>>>> >>>>>>>>> Regards, Thierry. >>>>>>>>> >>>>>>>>> >>>>>>>>>> On 28/01/13 14:28, Alexandru Petrescu wrote: Le >>>>>>>>>> 28/01/2013 14:16, Joe Klein a écrit : >>>>>>>>>>> I really dislike the fact that ISO is charging >>>>>>>>>>> for the ISO 21217 - Architecture & ISO 21210 - >>>>>>>>>>> IPv6 Networking. >>>>>>>>>>> >>>>>>>>>>> Does this make it any better? Safer? Should ISO >>>>>>>>>>> now have cybersecurity and safety liability if >>>>>>>>>>> the specification leads to deaths and damage to >>>>>>>>>>> property? >>>>>>>>>> >>>>>>>>>> Does it make any better interoperable as well? >>>>>>>>>> >>>>>>>>>> EtherType 0x0707 described in ITS documents, >>>>>>>>>> implemented, but not specified by IEEE nor reserved >>>>>>>>>> at IANA - does not make it interoperable. >>>>>>>>>> >>>>>>>>>> One wouldn't think that this 0x0707 ethertype be >>>>>>>>>> reserved by somebody who is not IANA nor IEEE? >>>>>>>>>> >>>>>>>>>> (see a good example of interoperability: IPv6 >>>>>>>>>> 0x86dd ethertype is reserved at IEEE and at IANA >>>>>>>>>> http://www.iana.org/assignments/ieee-802-numbers/ieee-802- >> >>>>>>>>>> numbers. >>> xm >>>>> l) >>>>>>>> >>>>>>> Alex >>>>>>>>>> >>>>>>>>>> Or should these standards remain in >>>>>>>>>>> the public domain, for researches to review and >>>>>>>>>>> validate? >>>>>>>>>>> >>>>>>>>>>> Just my 2 cents. >>>>>>>>>>> >>>>>>>>>>> Joe >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Mon, Jan 28, 2013 at 6:31 AM, Thierry Ernst >>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>> Dear all, >>>>>>>>>>>> >>>>>>>>>>>> At this stage, I don't think a new working >>>>>>>>>>>> group is needed. First, it would need a >>>>>>>>>>>> charter, and support from the industry. But >>>>>>>>>>>> more importantly, IETF WGs are not usually >>>>>>>>>>>> sector-driven, so it means the different issues >>>>>>>>>>>> pertaining to ITS should be brought to VARIOUS >>>>>>>>>>>> existing WGs, and a WG should only be created >>>>>>>>>>>> if there is an important issue for which there >>>>>>>>>>>> is no existing WG that could work on it. >>>>>>>>>>>> >>>>>>>>>>>> This said, as mentioned earlier, ITS is not >>>>>>>>>>>> only about vehicular communications, though the >>>>>>>>>>>> issues listed by Alexandru below mostly >>>>>>>>>>>> consider vehicular communications. >>>>>>>>>>>> >>>>>>>>>>>> What ITS really needs is the definition of a >>>>>>>>>>>> common communication architecture and the >>>>>>>>>>>> definition of what features should be comprised >>>>>>>>>>>> for an IPv6 networking stack deployed for ITS >>>>>>>>>>>> use cases. This cannot be done at IETF, and >>>>>>>>>>>> actually already exists at ISO: - ISO 21217 - >>>>>>>>>>>> Architecture - ISO 21210 - IPv6 Networking >>>>>>>>>>>> >>>>>>>>>>>> As an input to the discussion, please consider >>>>>>>>>>>> reading documents D2.1 and D2.2 available on >>>>>>>>>>>> the ITSSv6 project web page: >>>>>>>>>>>> http://www.itssv6.eu/documentation/ D2.2 >>>>>>>>>>>> provides an analysis of the currently published >>>>>>>>>>>> version of ISO 21210, but new work items have >>>>>>>>>>>> been launched since then to address remaining >>>>>>>>>>>> issues. >>>>>>>>>>>> >>>>>>>>>>>> Regards, Thierry. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> On 28/01/13 11:08, Alexandru Petrescu wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> Le 28/01/2013 05:02, Stan Ratliff (sratliff) >>>>>>>>>>>>> a écrit : >>>>>>>>>>>>>> >>>>>>>>>>>>>> All, >>>>>>>>>>>>>> >>>>>>>>>>>>>> This is just one opinion, but I'd like to >>>>>>>>>>>>>> understand why ITS would need its own IETF >>>>>>>>>>>>>> group. The work here is the same (IMO) as >>>>>>>>>>>>>> what is taking place in MANET. I would vote >>>>>>>>>>>>>> that this work be taken up in MANET. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Stan, >>>>>>>>>>>>> >>>>>>>>>>>>> Thank you for the offer. I considered this >>>>>>>>>>>>> offer since some time. >>>>>>>>>>>>> >>>>>>>>>>>>> I try to understand whether some of these >>>>>>>>>>>>> items on which I have interest could be >>>>>>>>>>>>> brought in in MANET WG: - V2V using prefix >>>>>>>>>>>>> exchange - VIN-based IP addressing scheme - >>>>>>>>>>>>> ND Prefix Delegation - PMIP-based network >>>>>>>>>>>>> mobility - IPv6 single-address connecion >>>>>>>>>>>>> 'sharing' with a cellular operator and a >>>>>>>>>>>>> vehicular moving network (type '64share' of >>>>>>>>>>>>> v6ops). - Default Route with DHCPv6. >>>>>>>>>>>>> >>>>>>>>>>>>> Please let me know. >>>>>>>>>>>>> >>>>>>>>>>>>> Yours, >>>>>>>>>>>>> >>>>>>>>>>>>> Alex >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Regards, Stan >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Jan 26, 2013, at 9:34 AM, Abdussalam >>>>>>>>>>>>>> Baryun wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi Nabil, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> I think we already done some steps but >>>>>>>>>>>>>>> not sure how far now. We will need to >>>>>>>>>>>>>>> propose the WG and provide the WG >>>>>>>>>>>>>>> charter, as use cases and work to be done >>>>>>>>>>>>>>> in this group. This charter needs to be >>>>>>>>>>>>>>> approved by the IESG. I have not attended >>>>>>>>>>>>>>> the last meeting so not sure about the >>>>>>>>>>>>>>> status now, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> AB >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On 1/26/13, Nabil Benamar >>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hi All, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I'm still interested in this list and >>>>>>>>>>>>>>>> want to join voices previously heard to >>>>>>>>>>>>>>>> make it a working group. So what should >>>>>>>>>>>>>>>> we exactly do, to achieve this goal ? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> 2013/1/26 Abdussalam Baryun >> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Hi All, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I was interested in this group but >>>>>>>>>>>>>>>>> not sure where are we so far. Is >>>>>>>>>>>>>>>>> there progress, or is there >>>>>>>>>>>>>>>>> issues/efforts that need to be >>>>>>>>>>>>>>>>> completed and volunteered. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> AB >>>>>>>>>>>>>>>>> >> _______________________________________________ >>>>> >>> its mailing list its@ietf.org >>>>>>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -- * * *تحياتي ، **Cordialement, Regards* * * >>>>>>>>>>>>>>>> * * *نبيل بنعمرو Nabil Benamar* >>>>>>>>>>>>>>>> Professor of computer sciences >>>>>>>>>>>>>>>> Simulation and Modelisation Laboratory >>>>>>>>>>>>>>>> Human Sciences Faculty of Meknes Moulay >>>>>>>>>>>>>>>> Ismail* *University* Meknes, Morocco >>>>>>>>>>>>>>>> *GSM: * *+ 212 6 70832236 >>>>>>>>>>>>>>>> http://nabilbenamar.com/ >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> * >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> --------------------------------------------------------- >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> --- >>> -- >>>>> ------------------ >>>>>>>>>>>>> >>>>>>>>>> * >>>>>>>>>>>>>>> >> _______________________________________________ >>> its mailing list its@ietf.org >>>>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> its mailing list its@ietf.org >>>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> >>>>>>>>>>>>> its mailing list its@ietf.org >>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> its >> mailing >>>>>>>>>>>> list its@ietf.org >>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> its >> mailing >>>>>>>>>>> list its@ietf.org >>>>>>>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> its >> mailing >>>>>>>>>> list its@ietf.org >>>>>>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ its >> mailing list >>>>>>>>> its@ietf.org >>>>>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ its >> mailing list >>>>>>>> its@ietf.org https://www.ietf.org/mailman/listinfo/its >>> >>> >>> --- Ce courrier électronique ne contient aucun virus ou logiciel >>> malveillant parce >> que la protection avast! Antivirus est active. >>> http://www.avast.com >>> >>> _______________________________________________ its mailing list >>> its@ietf.org https://www.ietf.org/mailman/listinfo/its >> >> _______________________________________________ its mailing list >> its@ietf.org https://www.ietf.org/mailman/listinfo/its > > > > Dit bericht kan informatie bevatten die niet voor u is bestemd. > Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u > is toegezonden, wordt u verzocht dat aan de afzender te melden en het > bericht te verwijderen. TNO aanvaardt geen aansprakelijkheid voor de > inhoud van deze e-mail, de wijze waarop u deze gebruikt en voor > schade, van welke aard ook, die verband houdt met risico's verbonden > aan het elektronisch verzenden van berichten. > > > > This message may contain information that is not intended for you. If > you are not the addressee or if this message was sent to you by > mistake, you are requested to inform the sender and delete the > message. TNO accepts no liability for the content of this e-mail, for > the manner in which you use it and for damage of any kind resulting > from the risks inherent to the electronic transmission of messages. > From nobody Fri May 16 02:01:05 2014 Return-Path: X-Original-To: its@ietfa.amsl.com Delivered-To: its@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EF9C1A0194 for ; Fri, 16 May 2014 02:01:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.083 X-Spam-Level: X-Spam-Status: No, score=-3.083 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham 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 OCms4yXJRMxp for ; Fri, 16 May 2014 02:01:03 -0700 (PDT) Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C50BA1A018E for ; Fri, 16 May 2014 02:01:02 -0700 (PDT) Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id s4G90ru9030618 for ; Fri, 16 May 2014 11:00:53 +0200 Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 546F920146E for ; Fri, 16 May 2014 11:01:50 +0200 (CEST) Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 4952A200C90 for ; Fri, 16 May 2014 11:01:50 +0200 (CEST) Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id s4G90iGE013309 for ; Fri, 16 May 2014 11:00:53 +0200 Message-ID: <5375D3BD.5040101@gmail.com> Date: Fri, 16 May 2014 11:00:45 +0200 From: Alexandru Petrescu User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "its@ietf.org" Content-Type: multipart/alternative; boundary="------------030206010002070309090300" Archived-At: http://mailarchive.ietf.org/arch/msg/its/wu6LyoguKO5LBtlUjHFMwQodIiQ Subject: [geonet/its] start writing use-case drafts - submit by June 1st. X-BeenThere: its@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "GeoNet BoF discussion list." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2014 09:01:04 -0000 This is a multi-part message in MIME format. --------------030206010002070309090300 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hello geonet/itsers, As we discussed in London - please start writing use-case drafts. Deadline June 1st, 2014. This message is in particular addressed to people having committed to write use-case drafts. The use-case drafts are to be referred to by the Problem Statement draft (Georgios). I remind an excerpt from the London minutes with respect to writing new use-case drafts: > Use cases: determine what characterizes a good use case in the present > context before moving to their development. > > The vehicular use cases are important, but only as an application of a > technology that is developped in a generic way. > > - Use-case1 draft object localization (Dimitri) > - Use-case2 draft goods tracking (Dino) > - Use-case3 draft geo dissemination (Georgios, Geert, Bastiaan) > - Use-case4 draft vehicular (Alex, Georgios, Robert, Geert Heijenk, > Andreas Festag). Please discuss this on the email list, or otherwise contact me and Georgios privately about this request. Thank you in advance. Alex --------------030206010002070309090300 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hello geonet/itsers,

As we discussed in London - please start writing use-case drafts.

Deadline June 1st, 2014.

This message is in particular addressed to people having committed to write use-case drafts.

The use-case drafts are to be referred to by the Problem Statement draft (Georgios).

I remind an excerpt from the London minutes with respect to writing new use-case drafts:

> Use cases: determine what characterizes a good use case in the present
> context before moving to their development.
>
> The vehicular use cases are important, but only as an application of a
> technology that is developped in a generic way.
>
> - Use-case1 draft object localization (Dimitri)
> - Use-case2 draft goods tracking (Dino)
> - Use-case3 draft geo dissemination (Georgios, Geert, Bastiaan)
> - Use-case4 draft vehicular (Alex, Georgios, Robert, Geert Heijenk,
>   Andreas Festag).

Please discuss this on the email list, or otherwise contact me and Georgios privately about this request.

Thank you in advance.

Alex

 --------------030206010002070309090300-- From nobody Wed May 21 09:07:46 2014 Return-Path: X-Original-To: its@ietfa.amsl.com Delivered-To: its@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C44E51A0834 for ; Wed, 21 May 2014 09:07:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.252 X-Spam-Level: X-Spam-Status: No, score=-2.252 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, MANGLED_WRLDWD=2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham 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 hq92cDo2PszL for ; Wed, 21 May 2014 09:07:40 -0700 (PDT) Received: from mail.amsl.com (mail.amsl.com [4.31.198.40]) by ietfa.amsl.com (Postfix) with ESMTP id 2CD331A0899 for ; Wed, 21 May 2014 09:06:59 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 17A901E59CE for ; Wed, 21 May 2014 09:06:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G-p2blc2CdI0 for ; Wed, 21 May 2014 09:06:25 -0700 (PDT) Received: from [192.168.1.21] (c-69-181-66-243.hsd1.ca.comcast.net [69.181.66.243]) by c8a.amsl.com (Postfix) with ESMTPSA id EEA301E59CD for ; Wed, 21 May 2014 09:06:24 -0700 (PDT) From: Alexa Morris Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Message-Id: Date: Wed, 21 May 2014 09:06:57 -0700 To: its@ietf.org Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) X-Mailer: Apple Mail (2.1874) Archived-At: http://mailarchive.ietf.org/arch/msg/its/SqTpZMiKD5SiL57Y2W11QqZZKsI Subject: [geonet/its] Invitation to Participate in IETF 90 Bits-N-Bites: Internet of Things X-BeenThere: its@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "GeoNet BoF discussion list." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2014 16:07:44 -0000 Bits-N-Bites at IETF 90 in Toronto will focus on the Internet of Things, = and the IETF invites you and your organization to participate! The arrival of Things connected to the Internet in recent years has = given life to new applications in both the consumer and industrial = market segments. We are surrounded by products that utilize connectivity = and a growing enthusiasm suggests imminent and impressive deployments: = billions of new connected devices are expected by year 2020. In the = industrial world, wide spread wireless sensoring devices that collect = data and measurements will move us into the next phase of process = optimization. This will require the combination of the best of = Information Technology (IT) and Operational Technology (OT), forming the = IT/OT convergence. When deploying multi-stage Thing topologies, two trends compete: IP = protocols are enhanced and transformed into less end-to-end protocols = (address translation, header compression, 'mesh under' routing and more) = and, alternatively, existing IP protocols are reduced to their bare = minimum such as to fit in reduced Things (reduced CPU frequency and = number of transistors, dimensions and energy consumption). IETF 90 demonstrations should exhibit recent developments of IP = protocols for IoT networks (6lowpan adaptation layers, MANET and RPL = routing protocols, 6tsch time-constrained communications, CoAP app-layer = protocols) as well as demonstrations of the tendency of bringing the = known IPv6 as close as possible to the Thing - minimum set of unmodified = IPv6, Neighbor Discovery, DHCP, HTTP, IKEv2. Demonstrations of = geo-location uses in and for IP networking and the surrounding privacy = issues are also welcome. Does your organization want to reach 1,200 Internet engineers and = demonstrate your IoT technologies and usage of IETF protocols? This is = your opportunity to show leading industry professionals the latest and = greatest of what you do in a social and interactive setting. Examples of demos include, but are not limited, to: =95 home automation controller using SNMP for HVAC and ambient = temperature, electricity counter; =95 industrial-grade Wireless Sensor Network products; =95 scalable wireless designs and existing deployments; =95 IPv6 end-to-end and backbone interconnection; =95 tablet summarizing status of widespread devices through = heterogeneous link connections; =95 smart belt collecting body information with low-energy communication = protocols; =95 vehicle interior connected designs, vehicle-to-road sensor-based = communications; =95 sensor-assisted autonomous mobile Things (mono-, bi-, quad- wheeled = or propelled devices); =95 vehicular communications (e.g. dead-reckoning enhancements for = enhanced GPS localization, geo-dissemination); =95 smartphone applications relying on geo-localization. There many ways to configure your demo, such as:=20 =95 Things deployed on a table, relying on local connections and = alternatively exhibiting remote access across the Internet; =95 a poster describing a demo; =95 video sequence showing a lab demonstration. For information about IETF 90 Bits-N-Bites, please see = http://www.ietf.org/meeting/90/90-bits-n-bites.html or send email to = bnbsg@ietf.org. Regards, Alexa ---------- Alexa Morris / Executive Director / IETF 48377 Fremont Blvd., Suite 117, Fremont, CA 94538 Phone: +1.510.492.4089 / Fax: +1.510.492.4001 Email: amorris@amsl.com Managed by Association Management Solutions (AMS) Forum Management, Meeting and Event Planning www.amsl.com From nobody Wed May 21 10:21:02 2014 Return-Path: X-Original-To: its@ietfa.amsl.com Delivered-To: its@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0137D1A084A for ; Wed, 21 May 2014 10:20:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.983 X-Spam-Level: X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham 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 fctyk4Y6tk46 for ; Wed, 21 May 2014 10:20:49 -0700 (PDT) Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59F6B1A0875 for ; Wed, 21 May 2014 10:20:31 -0700 (PDT) Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id s4LHKS6w022101 for ; Wed, 21 May 2014 19:20:28 +0200 Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id BBD9720508D for ; Wed, 21 May 2014 19:21:33 +0200 (CEST) Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id A9317204FBF for ; Wed, 21 May 2014 19:21:33 +0200 (CEST) Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id s4LHKCSL020358 for ; Wed, 21 May 2014 19:20:28 +0200 Message-ID: <537CE04C.6020705@gmail.com> Date: Wed, 21 May 2014 19:20:12 +0200 From: Alexandru Petrescu User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "its@ietf.org" References: <5433bfe3845e4fc2adb418a29efbdc4f@xMail.etsihq.org> In-Reply-To: <5433bfe3845e4fc2adb418a29efbdc4f@xMail.etsihq.org> X-Forwarded-Message-Id: <5433bfe3845e4fc2adb418a29efbdc4f@xMail.etsihq.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Archived-At: http://mailarchive.ietf.org/arch/msg/its/ExwmACg7XcknuYnkEKooFNhuYJM Subject: [geonet/its] Fwd: IPv6 Anycast Address for GeoNetworking X-BeenThere: its@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "GeoNet BoF discussion list." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2014 17:20:52 -0000 For your information - below, reservation of an IPv6 anycast address for GeoNetworking at IANA. I am wondering how is this anycast address used. Alex -------- Message original -------- Sujet: IPv6 Anycast Address for GeoNetworking Date : Mon, 19 May 2014 07:46:08 +0000 De : Martin Arndt Répondre à : Martin Arndt Pour : Dear all, Please be informed that IANA has assigned an IPv6 Anycast Address for GeoNetworking: http://www.iana.org/assignments/ipv6-anycast-addresses/ipv6-anycast-addresses.xhtml Kind regards, Martin ############################## Martin ARNDT Technical Officer ETSI Operations (OPS) Committee Support Centre (CSC) Telephone: +33 4 92 94 42 49 Skype: Mr Wavelength Email: martin.arndt@etsi.org Web: http://www.etsi.org ##############################