Hi Joe On Tue, Jan 27, 2015 at 7:28 PM, Joe Touch <[email protected]> wrote:
> > > On 1/27/2015 10:10 AM, Emmanuel Baccelli wrote: > > Hi Joe > > > > Le 27 janv. 2015 18:08, "Joe Touch" <[email protected] > > <mailto:[email protected]>> a écrit : > >>... > > but you are arguing that it is unuseful > > because it should include architectural considerations. Others say it is > > useful without architectural considerations. > > > > This is not necessarily a conflict. Why not have architectural > > considerations in another, subsequent draft? > > This draft is - at best - setup to an arch considerations doc. It's a > preface, an intro - maybe just a definitions section. > > Glad to see you finally recognize some informational value to the draft ;) And by the way: the draft is not going for experimental or standards track, but for informational. > There's no point to it without the arch part. > > >> Please tell us something we haven't known and dealt with for decades. > >> > > > > If everything is common knowledge since ages, why don't we have an > > obvious ref to point to, with a link model people agree on? > > We do (PILC and some of the other docs already cited). You claim that > it's insufficient, so again the onus is on you to *prove* that's true. > > > I'm not talking about 100 references that kind of fit, but not really, because people don't agree on a link model (as shown by this discussion so far). I understand your point of view about wanting to bundle both informational and architectural aspects in the document. However, I have a different experience: in AUTOCONF we tried to do exactly that (i.e. bundle both informational and architectural aspects in the document), but never converged, partly because we did not have such an informational document to refer to -- to keep the discussion "grounded". I say: let's not make the same mistake twice. Let's first agree on how to describe what we observed, then publish a document on that. Until then, experience shows we are not ready to debate on applicable architectures. Best, Emmanuel
_______________________________________________ Int-area mailing list [email protected] https://www.ietf.org/mailman/listinfo/int-area
