Re: [multimob] Polling WG on draft-ietf-multimob-pmipv6-source-07

"Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de> Fri, 10 January 2014 10:34 UTC

Return-Path: <prvs=0808c8da2=schmidt@informatik.haw-hamburg.de>
X-Original-To: multimob@ietfa.amsl.com
Delivered-To: multimob@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6F411A8033 for <multimob@ietfa.amsl.com>; Fri, 10 Jan 2014 02:34:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Level:
X-Spam-Status: No, score=-2.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.538] 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 PkeZ7wK-ZFlW for <multimob@ietfa.amsl.com>; Fri, 10 Jan 2014 02:34:56 -0800 (PST)
Received: from mx6.haw-public.haw-hamburg.de (mx6.haw-public.haw-hamburg.de [141.22.6.3]) by ietfa.amsl.com (Postfix) with ESMTP id BB9271AC863 for <multimob@ietf.org>; Fri, 10 Jan 2014 02:34:55 -0800 (PST)
Received: from mailgate.informatik.haw-hamburg.de ([141.22.30.74]) by mail6.is.haw-hamburg.de with ESMTP/TLS/ADH-AES256-SHA; 10 Jan 2014 11:34:34 +0100
Received: from localhost (localhost [127.0.0.1]) by mailgate.informatik.haw-hamburg.de (Postfix) with ESMTP id B859610679D7; Fri, 10 Jan 2014 11:34:34 +0100 (CET)
Received: from mailgate.informatik.haw-hamburg.de ([127.0.0.1]) by localhost (mailgate.informatik.haw-hamburg.de [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 08490-05; Fri, 10 Jan 2014 11:34:34 +0100 (CET)
Received: from [192.168.178.33] (e178062121.adsl.alicedsl.de [85.178.62.121]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate.informatik.haw-hamburg.de (Postfix) with ESMTPSA id F10B710679CF; Fri, 10 Jan 2014 11:34:33 +0100 (CET)
Message-ID: <52CFCCB6.7030609@informatik.haw-hamburg.de>
Date: Fri, 10 Jan 2014 11:34:30 +0100
From: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: sarikaya@ieee.org, Sebastian Woelke <sebastian.woelke@posteo.de>
References: <CAC8QAcdYk0dioXh7x3_Offq+2Ykg2OhS70Nw9j3TcdHjGg_v+A@mail.gmail.com> <52CF081A.9010608@informatik.haw-hamburg.de> <CAC8QAcctaN7m23iE9oW7NQpPbx3GQ6TF08e4ZVBuiXJZR4_Nbw@mail.gmail.com> <556a93ec289a22d237e5bddbfa0c3ded@posteo.de> <CAC8QAceSmWStkgitwCg4YhhfLVKu7jV9LMU9_x7bAZTwGLrbWg@mail.gmail.com>
In-Reply-To: <CAC8QAceSmWStkgitwCg4YhhfLVKu7jV9LMU9_x7bAZTwGLrbWg@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: by amavisd-new at informatik.haw-hamburg.de
Cc: "multimob@ietf.org" <multimob@ietf.org>
Subject: Re: [multimob] Polling WG on draft-ietf-multimob-pmipv6-source-07
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob/>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 10:35:00 -0000

Hi,

On 10.01.2014 00:11, Behcet Sarikaya wrote:

> Also you did not say which parts you implemented?
>

The implementation "mcproxy" was announced on the list on Dec. 18th, 
2013. It covers those parts of the draft that are not deployable with 
commonly available 'standard' software like MLD-Proxies or PIM daemons:

"
The mcproxy complies to the IGMP/MLD proxy standard (RFC 4605) and 
supports the group membership protocols IGMPv3 and MLDv2 as well.
In additional it meets the requirements of the multicast source and 
listener support in proxy mobile IPv6 
(draft-ietf-multimob-pmipv6-source-06 and RFC 6224).

Key features:
  - supports IPv4 (IGMPv3)
  - supports IPv6 (MLDv2)
  - can be instantiated multiple times
  - dynamically configurable at runtime
  - can be configured to peer data between its instances
  - supports multiple upstreams
"

Cheers,

Thomas


> On Thu, Jan 9, 2014 at 3:58 PM, Sebastian Woelke
> <sebastian.woelke@posteo.de <mailto:sebastian.woelke@posteo.de>> wrote:
>
>     Hello,
>
>     I reviewed pmipv6-source-06 for the WG last call, I implemented
>     parts of it and weeks after the last call I think the draft is still
>     in a good shape and ready for the next step.
>     I also think the draft get a consistency problem if we remove this
>     chapter.
>
>     Kind Regards,
>     Sebastian
>
>
>
>     Am 09.01.2014 21:51 schrieb Behcet Sarikaya:
>
>         Hi Thomas,
>
>         On Thu, Jan 9, 2014 at 2:35 PM, Thomas C. Schmidt
>         <schmidt@informatik.haw-__hamburg.de
>         <mailto:schmidt@informatik.haw-hamburg.de>> wrote:
>
>             Hi,
>
>             I do not think that IETF procedures allow for WG chairs to
>             garble drafts after they had successfully passed WG last call.
>
>
>         This is not garbling the draft.
>
>         Please refer to the shepherd document:
>
>         http://www.ietf.org/iesg/__template/doc-writeup.html
>         <http://www.ietf.org/iesg/template/doc-writeup.html> [6]
>
>
>         In order to answer positively many questions like 2, Working Group
>         Summary, or 4,
>
>         We need to get WG's opinion.
>
>         I personally am confused.
>
>         Regards,
>
>         Behcet
>
>
>             Am I mistaken, Brian?
>
>             Cheers,
>
>             Thomas
>
>             On 09.01.2014 21:12, Behcet Sarikaya wrote:
>
>                 Hi all,
>
>                 Before shepherding this document to IESG we would like
>                 to get consensus
>                 opinion on one issue regarding this document that came
>                 up recently.
>                 Please refer to my conversation with Thomas on the list.
>
>                 ISSUE:
>                 Multimob WG has not worked on PIM at MAG for receiver
>                 mobility, we only
>                 worked on Proxy at MAG as per RFC 6224.
>                 However draft-ietf-multimob-pmipv6-__source-07 covers
>                 PIM at MAG for
>                 source mobility starting with Section 4.3.
>
>                 Question:
>
>                 Do you support covering PIM at MAG for source mobility,
>                 then say YES,
>
>                 if you do not support it then say NO.
>
>                 We need as many people as possible to express opinion on
>                 this issue. The
>                 deadline is one week from today, January 16, 2014.
>
>                 If WG consensus does not exist, we will ask the authors
>                 to remove PIM at
>                 MAG sections (subsections) and we will submit the
>                 revised document to IESG.
>
>                 Regards,
>
>                 Behcet
>
>                 _________________________________________________
>                 multimob mailing list
>                 multimob@ietf.org <mailto:multimob@ietf.org>
>                 https://www.ietf.org/mailman/__listinfo/multimob
>                 <https://www.ietf.org/mailman/listinfo/multimob> [1]
>
>
>             --
>
>             Prof. Dr. Thomas C. Schmidt
>             ° Hamburg University of Applied Sciences
>             Berliner Tor 7 °
>             ° Dept. Informatik, Internet Technologies Group    20099
>             Hamburg, Germany °
>             ° http://www.haw-hamburg.de/inet [2]                   Fon:
>             +49-40-42875-8452 <tel:%2B49-40-42875-8452> [3] °
>             ° http://www.informatik.haw-__hamburg.de/~schmidt
>             <http://www.informatik.haw-hamburg.de/~schmidt> [4]    Fax:
>             +49-40-42875-8409 <tel:%2B49-40-42875-8409> [5] °
>
>
>
>
>         Links:
>         ------
>         [1] https://www.ietf.org/mailman/__listinfo/multimob
>         <https://www.ietf.org/mailman/listinfo/multimob>
>         [2] http://www.haw-hamburg.de/inet
>         [3] tel:%2B49-40-42875-8452
>         [4] http://www.informatik.haw-__hamburg.de/~schmidt
>         <http://www.informatik.haw-hamburg.de/~schmidt>
>         [5] tel:%2B49-40-42875-8409
>         [6] http://www.ietf.org/iesg/__template/doc-writeup.html
>         <http://www.ietf.org/iesg/template/doc-writeup.html>
>
>
>         _________________________________________________
>         multimob mailing list
>         multimob@ietf.org <mailto:multimob@ietf.org>
>         https://www.ietf.org/mailman/__listinfo/multimob
>         <https://www.ietf.org/mailman/listinfo/multimob>
>
>     _________________________________________________
>     multimob mailing list
>     multimob@ietf.org <mailto:multimob@ietf.org>
>     https://www.ietf.org/mailman/__listinfo/multimob
>     <https://www.ietf.org/mailman/listinfo/multimob>
>
>
>
>
> _______________________________________________
> multimob mailing list
> multimob@ietf.org
> https://www.ietf.org/mailman/listinfo/multimob
>

-- 

Prof. Dr. Thomas C. Schmidt
° Hamburg University of Applied Sciences                   Berliner Tor 7 °
° Dept. Informatik, Internet Technologies Group    20099 Hamburg, Germany °
° http://www.haw-hamburg.de/inet                   Fon: +49-40-42875-8452 °
° http://www.informatik.haw-hamburg.de/~schmidt    Fax: +49-40-42875-8409 °