Re: [v6ops] 82nd IETF DRAFT Agenda

Yu Guanghui <ygh@dlut.edu.cn> Mon, 31 October 2011 04:53 UTC

Return-Path: <btv1==285d2b06b48==ygh@dlut.edu.cn>
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 A554D21F8C6E for <v6ops@ietfa.amsl.com>; Sun, 30 Oct 2011 21:53:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.575
X-Spam-Level: ***
X-Spam-Status: No, score=3.575 tagged_above=-999 required=5 tests=[AWL=0.718, BAYES_00=-2.599, CN_BODY_35=0.339, J_CHICKENPOX_13=0.6, MIME_CHARSET_FARAWAY=2.45, RCVD_NUMERIC_HELO=2.067]
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 QjxAa+-gSRfl for <v6ops@ietfa.amsl.com>; Sun, 30 Oct 2011 21:53:12 -0700 (PDT)
Received: from mx2.dlut.edu.cn (mx2.dlut.edu.cn [202.118.66.81]) by ietfa.amsl.com (Postfix) with ESMTP id E930821F8C6D for <v6ops@ietf.org>; Sun, 30 Oct 2011 21:53:11 -0700 (PDT)
X-ASG-Debug-ID: 1320036782-021f9e0983d7430001-b2NLKh
Received: from mail1.dlut.edu.cn (mail1.dlut.edu.cn [202.118.66.77]) by mx2.dlut.edu.cn with SMTP id IRjENeLupYNgQKoY for <v6ops@ietf.org>; Mon, 31 Oct 2011 12:53:02 +0800 (CST)
X-Barracuda-Envelope-From: ygh@dlut.edu.cn
X-Barracuda-Apparent-Source-IP: 202.118.66.77
X-Barracuda-Registry: Level1 [dlut.edu.cn/202.118.66.77]
X-Barracuda-Registry: Level1 [dlut.edu.cn/202.118.66.77]
YmailServer-SMTP-Logined: ygh@dlut.edu.cn
Received: from 111.117.110.101 (HELO [111.117.110.101]) ([111.117.110.101]) by mail1.dlut.edu.cn (STD Ymailserver v3.2 ESMTP) with SMTP ID 164; Mon, 31 Oct 2011 12:53:02 +0800 (CST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
X-ASG-Orig-Subj: Re: [v6ops] 82nd IETF DRAFT Agenda
Content-Type: text/plain; charset="GB2312"
From: Yu Guanghui <ygh@dlut.edu.cn>
In-Reply-To: <4EAE1350.2050503@bogus.com>
Date: Mon, 31 Oct 2011 12:53:01 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <0630F413-A258-4FDA-B42C-776923241E20@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> <4EAE1350.2050503@bogus.com>
To: Joel jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.1251.1)
X-Barracuda-Connect: mail1.dlut.edu.cn[202.118.66.77]
X-Barracuda-Start-Time: 1320036782
X-Barracuda-URL: http://202.118.66.81:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at dlut.edu.cn
X-Barracuda-Spam-Score: 1.43
X-Barracuda-Spam-Status: No, SCORE=1.43 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests=CN_BODY_138, CN_BODY_332, CN_BODY_499, RCVD_NUMERIC_HELO
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.78885 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 1.25 RCVD_NUMERIC_HELO Received: contains an IP address used for HELO 0.05 CN_BODY_138 BODY: CN_BODY_138 0.00 CN_BODY_499 BODY: CN_BODY_499 0.12 CN_BODY_332 BODY: CN_BODY_332
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 04:53:13 -0000

Here is a example:

ping ivi.dlut.edu.cn   <- it's a pure IPv6 site behind a stateless translator.
PING ivi.dlut.edu.cn (58.200.163.1) 56(84) bytes of data.
64 bytes from 58.200.163.1: icmp_seq=1 ttl=45 time=103 ms
64 bytes from 58.200.163.1: icmp_seq=2 ttl=45 time=106 ms

but when we trace it:

traceroute ivi.dlut.edu.cn
traceroute to ivi.dlut.edu.cn (58.200.163.1), 30 hops max, 40 byte packets
 1  202.118.66.1 (202.118.66.1)  0.399 ms  0.459 ms  0.582 ms
 ...
10  202.112.61.182 (202.112.61.182)  15.579 ms *  15.503 ms  <- what happened here? maybe a firewall, router or translator?
11  * * *
12  * * *
....
29  * * *
30  * * *


We will don't what happened after hop 10.  If we have a special mapping address, for example 192.70.192.0, we will understand there's a translator and have some other helpful information.


Yu Guanghui <ygh at dlut.edu.cn>
Network and Information Center
Dalian University of Technology, China
Tel: +86 411 84708117

在 2011-10-31,上午11:17, Joel jaeggli 写道:

> 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
>> 
>> 
>