Re: [trill] Should we make draft-mrw-trill-over-ip-01 a WG document?

["Tissa Senevirathne (tsenevir)" <[e-mail]>]

Hi James 

I am not clear with your point though, you indicated lead to "too many
solutions", which is exactly the issue. 

please see my comments in-line

-----Original Message-----
From: James Carlson [mailto:[e-mail]] 
Sent: Monday, May 14, 2012 5:56 AM
To: Tissa Senevirathne (tsenevir)
Cc: Erik Nordmark; [e-mail]
Subject: Re: [trill] Should we make draft-mrw-trill-over-ip-01 a WG
document?

Tissa Senevirathne (tsenevir) wrote:
> I do not think we should rush this document to WG status. We should 
> look in a bigger picture i.e. what sorts of TRILL interconnects are 
> needed and then proceed accordingly.
> 
> We do not want too many solutions that implement subsets. It is a pain

> for vendors and confusion for customers. What we need is a single 
> comprehensive solution that covers the problem spaces.
> 
> My vote is "NO" to move this document to WG status.

That sounds a bit backwards to me.

[Answer] Doing small piecemeal work, is not the right approach. 
 
The document is clearly in scope of the working group, and I believe the
only other question regarding adoption is whether the wg wants (and the
authors want) to steer the document by the working group consensus
process.

[Answer] Good point, I re-read the charter one more time and there is no
where it says TRILL over IP or other encapsulation, so it seems the
document is not in charter. Please could you point to the WG, which line
item in charter that qualifies this work to be in scope ?

https://datatracker.ietf.org/wg/trill/charter/


Determining whether it's needed or the right technical solution is
further down the road.  If the wg determines that it's not right and
can't fix it, then it can terminate the work that it steers.  Adoption
doesn't mean "we're committed to publishing this."

I think leaving work that is in the scope of the working group outside
the wg merely because some higher-level planning is contemplated is not
a good idea, and not keeping with IETF tradition.  It invites exactly
the sort of "too many solutions" problems that the poster refers to, as
the rejected authors seek out other venues -- including individual
submission -- to pursue the work.

[Answer] IETF tradition has been to start with a problem space and
create a common solution not making every draft that is in scope of
charter a WG document. Your point on "too many solutions" exactly that
is my point having subset of solutions finally leads to too many small
pieces.
-- 
James Carlson         42.703N 71.076W         <[e-mail]>