Re: [mpls] Barry Leiba's Discuss on draft-ietf-mpls-ipv6-only-gap-03: (with DISCUSS and COMMENT)

[Loa Andersson <[e-mail]>]

Barry,

I don't know how much more I have to after Adrian's mail, it seems
cover the issues.

We never had the ambition to find every gap, but believed that
that documenting for the future that we made the effort and also that
the gaps we found would be a good enough idea.

I differ from Adrian on one point, I think it is very likely that we'll
find new gaps, however they will be few and with low impact.

This begs the question how we'll maintain the management of the gaps
and the recommendations around for each gap should be done. An idea
that has been circualted it to use a wiki page, but so far there is no
decision. But - as our ADs have said - with a wiki we don't really need
a decision, just someone that takes on the task to do it.

As for the references I agree that it is possible to take a pass on
them, the thing with how (other than normative informative) one prefer
to have references sort are very personal.

/Loa


On 2014-11-23 15:07, Adrian Farrel wrote:
> [Adding the MPLS WG]
>
> That's a pretty fine question, Barry.
>
> I'd say that, despite the care and work of the working group, it is possible that another gap will be identified. However, I think that might be a lowish possibility and that any new gaps might form a small percentage of the total gaps analysed.
>
> So, my judgement is that this is a bridge to cross when we get there, but others might comment.
>
> And, yes, we can take a pass on the references.
>
> A
>
>> -----Original Message-----
>> From: iesg [mailto:[e-mail]] On Behalf Of Barry Leiba
>> Sent: 23 November 2014 06:49
>> To: The IESG
>> Cc: [e-mail]; [e-mail]
>> Subject: Barry Leiba's Discuss on draft-ietf-mpls-ipv6-only-gap-03: (with DISCUSS
>> and COMMENT)
>>
>> Barry Leiba has entered the following ballot position for
>> draft-ietf-mpls-ipv6-only-gap-03: Discuss
>>
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>
>>
>> Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>>
>>
>> The document, along with other ballot positions, can be found here:
>> http://datatracker.ietf.org/doc/draft-ietf-mpls-ipv6-only-gap/
>>
>>
>>
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>>
>> This is a DISCUSS in the truest sense: I'd like to discuss a question
>> with the shepherd and/or AD, and I fully expect to resolve the question
>> satisfactorily from that.
>>
>> The first thing I wondered was why this shouldn't be something maintained
>> in a place other than an RFC, and I found that covered well in the
>> shepherd writeup. Thanks for that!
>>
>> What I continue to wonder is whether, in having that discussion, the
>> working group considered what the likelihood is of discovering more gaps
>> as they (and other working groups) work on dealing with these.  If so, I
>> wonder what the working group's plan is for documenting those.
>>
>>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>> I submit that a good number of the references really are normative, in
>> that understanding them is necessary in order to understand this
>> document.  I'd like to see the authors sort that out, and make an
>> appropriate split in the references, so readers can know which ones truly
>> do just add extra detail (informative), and which provide necessary
>> background (normative).  That said, I don't consider that important
>> enough to this document to block on it, so this is a non-blocking
>> comment.  Please consider doing this, but there is no need to respond to
>> me about it.  Thanks.
>
>

-- 


Loa Andersson                        email: [e-mail]
Senior MPLS Expert                          [e-mail]
Huawei Technologies (consultant)     phone: [phone]