Re: [Rfced-future] Model proposal

[Larry Masinter <[e-mail]>]

... My concern is that
> this needs to be facilitated and informed by someone with relevant
> knowledge and experience in the editing/publishing/library/archival world
> and that is not us


You keep on making this assertion that the skills of editing, publishing, archival world "is not us".  I think being versed in the engineering considerations of those properties SHOULD be "us".

The reason we have an archival series of specifications is not that we want to build a memorial Ozymandias altar to our golden words, but because these are the archival records of how things worked. It's a serious problem when buildings and bridges last longer than the documents that describe them.   How else can you make all of these paper-based archival solutions into all electronic worlds?


But all of this is an engineering problem, within the range of what I'd expect an engineer to deal with.

We're spending a lot of time engineering a person-to-person protocol. The unique parts of IETF is that we treat person-to-person protocols at layer 7.5 with checks and balances, without any work on writing down the Security Considerations.