Re: [v6ops] 82nd IETF DRAFT Agenda

Joel jaeggli <joelja@bogus.com> Mon, 31 October 2011 03:17 UTC

Return-Path: <joelja@bogus.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65A2821F8C40 for <v6ops@ietfa.amsl.com>; Sun, 30 Oct 2011 20:17:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.771
X-Spam-Level:
X-Spam-Status: No, score=-100.771 tagged_above=-999 required=5 tests=[AWL=-1.561, BAYES_00=-2.599, CN_BODY_35=0.339, J_CHICKENPOX_13=0.6, MIME_CHARSET_FARAWAY=2.45, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IXLOjAH3eHn9 for <v6ops@ietfa.amsl.com>; Sun, 30 Oct 2011 20:17:48 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 7752121F8C32 for <v6ops@ietf.org>; Sun, 30 Oct 2011 20:17:48 -0700 (PDT)
Received: from Zorch.local (236.sub-166-250-32.myvzw.com [166.250.32.236]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p9V3HfNW083691 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 31 Oct 2011 03:17:41 GMT (envelope-from joelja@bogus.com)
Message-ID: <4EAE1350.2050503@bogus.com>
Date: Sun, 30 Oct 2011 20:17:36 -0700
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Yu Guanghui <ygh@dlut.edu.cn>
References: <519971001.31182@tju.edu.cn> <4EADD509.3090101@bogus.com> <7291EFAC-46CA-423F-B033-F9B0443CC014@cisco.com> <4EAE0A77.8050003@bogus.com> <E09AFC73-EE37-4FD6-B955-AD86F65BC9DF@dlut.edu.cn>
In-Reply-To: <E09AFC73-EE37-4FD6-B955-AD86F65BC9DF@dlut.edu.cn>
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Mon, 31 Oct 2011 03:17:42 +0000 (UTC)
Cc: v6ops@ietf.org, v6ops-chairs@tools.ietf.org
Subject: Re: [v6ops] 82nd IETF DRAFT Agenda
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Oct 2011 03:17:49 -0000

On 10/30/11 20:00 , Yu Guanghui wrote:
> 
> 
> 在 2011-10-31,上午10:39, Joel jaeggli 写道:
> 
>> On 10/30/11 18:50 , Fred Baker wrote:
>>>
>>> On Oct 31, 2011, at 6:51 AM, Joel jaeggli wrote:
>>>
>>>> On 10/30/11 03:32 , 孟少卿 wrote:
>>>>> Hi all I also support draft-xli-v6ops-ivi-icmp-address-00.txt  to
>>>>> be adopted as a WG document in V6ops. A special block of IPv4
>>>>> address mapping for  the non-directly translatable IPv6 address
>>>>> will  helpful for us to troubleshoot. We have deployed the
>>>>> stateless translator for about two years in the campus networks.
>>>>
>>>> What addresses do you presentialy use a the source address for
>>>> icmp messages sent from the stateless translator?
>>>
>>> My understanding is that he doesn't - the message is dropped. The net
>>> effect in a traceroute (IPv4) is to see something that looks like a
>>> routing loop or a black hole on the far side (IPv6) of the
>>> translator. He'd like something that shows that distance is
>>> progressing and it's a state number of hops beyond the translator.
>>> It's not all the information one would like to see, but it's more and
>>> better than "* * *".
>>
>> Why not use a gua v4 address bound to the translator
>>
> 
> From IPv4 side, We can't identify it's a translator or a regular router if use a IPv4 address bound to the translator.

it is a router...

> 
>> It might not be asthetically pleasing but it identifies the source
>> rather well and it's not likely to be filtered.
>>
>>> In the reverse direction, traceroute6 from the IPv6 side, the ICMP6
>>> message can represent the IPv4 address as ::ipv4 or ::FFFF:ipv4. We
>>> see that in the wild now.
>>>
>>>>> Best Regards Shaoqing Meng Tianjin University Information and
>>>>> Network Center
>>>>>
>>>>> -----邮件原件----- 发件人: v6ops-bounces@ietf.org 
>>>>> [mailto:v6ops-bounces@ietf.org] 代表 Xing Li 发送时间: 2011年10月24日
>>>>> 18:37 收件 人: V6ops Chairs 抄送: v6ops@ietf.org WG 主题: Re: [v6ops]
>>>>> Fwd: 82nd IETF DRAFT Agenda
>>>>>
>>>>> Hi, Fred and All,
>>>>>
>>>>> 于 2011/10/14 5:52, Fred Baker 写道:
>>>>>> The initial version of the agenda has been posted. It places
>>>>>> v6ops on Wednesday and Friday mornings, a total of 4.5 hours.
>>>>>> I personally am satisfied with it, but if folks have issues I
>>>>>> can pass them along.
>>>>>>
>>>>>> I'll note that the deadline for -00 drafts is 24 October, and
>>>>>> the deadline for updated drafts is a week later. For discussion
>>>>>> in the working group meetings, I'm looking for a draft posted
>>>>>> after 25 July, with supporting email discussion on the list.
>>>>>>
>>>>>> I'm looking for (and in some cases have seen) commentary on
>>>>>> each of:
>>>>>>
>>>>>> -rw-rw-r--  1 fred  fred  13796 Jul 25 23:59 
>>>>>> draft-xli-v6ops-ivi-icmp-address-00.txt
>>>>>
>>>>> I would like to request that the V6ops WG adopt 
>>>>> draft-xli-v6ops-ivi-icmp-address-00.txt as a WG adoption.
>>>>>
>>>>> The draft describes the operational considerations of mapping
>>>>> ICMPv6 packets through an RFC6145 gateway where the IPv6 address
>>>>> is not directly translatable into an IPv4 address, and requests
>>>>> an IANA Special Purpose IPv4 address allocation (192.70.192.0/24)
>>>>> to allow this address mapping to take place using a
>>>>> protocol-specific designated address block in IPv4.
>>>>>
>>>>> The authors are hopeful that this will not require any valuable 
>>>>> face-to-face WG time at IETF 82 and the WG's consideration of
>>>>> this document can be undertaken entirely on the mailing list.
>>>>>
>>>>> Regards,
>>>>>
>>>>> xing
>>>>>
>>>>>> -rw-rw-r--  1 fred  fred  34974 Sep 14 10:45 
>>>>>> draft-ietf-v6ops-happy-eyeballs-04.txt -rw-rw-r--  1 fred
>>>>>> fred 26625 Sep 27 13:22 
>>>>>> draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-04.txt 
>>>>>> -rw-rw-r--  1 fred  fred  25341 Oct  2 11:39 
>>>>>> draft-jjmb-v6ops-comcast-ipv6-experiences-02.txt -rw-rw-r--  1
>>>>>> fred fred  28127 Oct  6 14:13 
>>>>>> draft-gashinsky-v6ops-v6nd-problems-00.txt -rw-rw-r--  1 fred
>>>>>> fred 45016 Oct  7 12:39 draft-ietf-v6ops-6204bis-00.txt
>>>>>> -rw-rw-r--  1 fred  fred   8877 Oct 10 09:00 
>>>>>> draft-ietf-v6ops-ipv6-discard-prefix-00.txt -rw-rw-r--  1 fred 
>>>>>> fred  15656 Oct 12 20:38 
>>>>>> draft-carpenter-v6ops-label-balance-00.txt
>>>>>>
>>>>>> plus any new drafts that are posted.
>>>>>>
>>>>>> Begin forwarded message:
>>>>>>
>>>>>>> From: IETF Agenda<agenda@ietf.org> Date: October 13, 2011
>>>>>>> 2:13:10 PM PDT To: Working Group Chairs<wgchairs@ietf.org> 
>>>>>>> Cc:irsg@irtf.org Subject: 82nd IETF DRAFT Agenda
>>>>>>>
>>>>>>> The DRAFT agenda is ready for viewing.  Please note the
>>>>>>> cutoff date for requests to reschedule Working Group and BOF
>>>>>>> meetings is October 17, 2011 17:00 PT.  The final agenda will
>>>>>>> be published on October 21, 2011.
>>>>>>>
>>>>>>> https://datatracker.ietf.org/meeting/82/agenda.html 
>>>>>>> https://datatracker.ietf.org/meeting/82/agenda.txt
>>>>>>>
>>>>>>> http://www.ietf.org/meeting/82/index.html
>>>>>>>
>>>>>>>
>>>>>>> Thanks, Wanda
>>>>>>>
>>>>>>> Only 30 days until Taipei, 82nd IETF! Online registration for
>>>>>>> the IETF meeting is at:
>>>>>>> http://www.ietf.org/meeting/register.html
>>>>>>>
>>>>>> _______________________________________________ v6ops mailing
>>>>>> list v6ops@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________ v6ops mailing
>>>>> list v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>>>>>
>>>>> _______________________________________________ v6ops mailing
>>>>> list v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>>>>>
>>>>
>>>
>>>
>>
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
> 
>