[Data-modeling] RFCs that define a protocol

[Vishal Talwar]

There is an open request for adding an "RFCs that define this protocol" property to the Internet Protocol type. Since I know almost nothing about the subject matter, I'd like to open this up for input from everyone here. Specifically,

1. Should this property be limited to the Internet Protocol type, or can RFCs define other types of protocols?

2. There should be a new type to model RFCs, and I'm considering the following properties:
   - Status (informational|experimental|...)
   - Date published (/type/datetime)
   - Published by (/people/person)
   - Obsoleted by (rfc)
   - Specifies protocol (internet protocol)

   Am I missing anything?

3. Should RFCs be assigned keys that correspond to their serial numbers? We could then easily generate URL-template-based links to RFCs themselves, assuming the IETF URLs are regular.

The original discussion took place here:
http://www.freebase.com/discuss/threads/guid/9202a8c04000641f8000000009f237f8?domain=/computer

Thanks!
Vishal