Re: I-D Action: draft-ietf-mboned-mtrace-v2-23.txt

[ +EKR, Mirja ]

On Tue, Apr 3, 2018 at 2:12 AM, Hitoshi Asaeda <[email protected]> wrote:
> Hi WG and Warren,
>
> We've submitted our revised document for Mtrace version 2.
>
> We believe we had addressed all comments and concerns given during the last IESG review.
> Please kindly check the document and restart the IESG review again if you think it satisfies all.

Dear EKR and Mirja,

I think that this version addresses your DISCUSS points.

As it's been a while (2 1/2 months) I've included some links to try
and make this is bit easier:

Your initial reviews:
https://datatracker.ietf.org/doc/draft-ietf-mboned-mtrace-v2/ballot/
Ballots: https://www.ietf.org/rfcdiff?url1=draft-ietf-mboned-mtrace-v2-22&url2=draft-ietf-mboned-mtrace-v2-23

I've also tried to summarize your DISCUSS points and the fixes here:
https://docs.google.com/document/d/1NZJkqvg504syBUNkhnB9wod20ajoEJhFIusmUbJ0P20/edit?usp=sharing

EKR: I'm not sure if you feel that the Security Considerations section
is now adequate.
Mirja: The document doesn't explicitly instruct IANA to update the
ports registry, but there is a reference to this draft already
(https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?&page=129)
and so I beleive it will be done?

If these address your DISCUSS points, would you be willing to clear?

W

>
> Best regards,
>
> Hitoshi Asaeda
>
>
>> 2018/04/03 15:06, [email protected] wrote:
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>> This draft is a work item of the MBONE Deployment WG of the IETF.
>>
>>        Title           : Mtrace Version 2: Traceroute Facility for IP Multicast
>>        Authors         : Hitoshi Asaeda
>>                          Kerry Meyer
>>                          WeeSan Lee
>>       Filename        : draft-ietf-mboned-mtrace-v2-23.txt
>>       Pages           : 38
>>       Date            : 2018-04-02
>>
>> Abstract:
>>   This document describes the IP multicast traceroute facility, named
>>   Mtrace version 2 (Mtrace2).  Unlike unicast traceroute, Mtrace2
>>   requires special implementations on the part of routers.  This
>>   specification describes the required functionality in multicast
>>   routers, as well as how an Mtrace2 client invokes a query and
>>   receives a reply.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-mboned-mtrace-v2/
>>
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-ietf-mboned-mtrace-v2-23
>> https://datatracker.ietf.org/doc/html/draft-ietf-mboned-mtrace-v2-23
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-mboned-mtrace-v2-23
>>
>>
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> MBONED mailing list
>> [email protected]
>> https://www.ietf.org/mailman/listinfo/mboned
>



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf

_______________________________________________
MBONED mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/mboned