[iot-wg] RIPE document on IoT security solutions
- Previous message (by thread): [iot-wg] RIPE document on IoT security solutions
- Next message (by thread): [iot-wg] RIPE document on IoT security solutions
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nigel Titley
nigel at titley.com
Wed Oct 10 14:47:10 CEST 2018
On 10/10/18 13:40, Peter Steinhäuser wrote: > > >> There’s not much to learn Peter. RIPE doesn’t develop standards. In >> the sense that IEEE or IETF develops standards. RIPE sometimes >> develops policies, usually on the allocation of numbering resources. >> These policies are produced though the process defined in RIPE >> document 710: https://www.ripe.net/publications/docs/ripe-710. >> >> Anything can become a RIPE document, not just policies. The process is >> simple. Someone just says to the NCC “please publish this as a RIPE >> document”. And it is done. >> >> For this case, I think we want something that reflects a consensus >> view of the WG. If you can produce an initial draft or outline and >> post it to the list, we can discuss that, make changes and go through >> a few iterations of the document. Hopefully we then end up with >> something that has broad acceptance from the WG. At that point, >> someone takes the finished article to the NCC and asks for it to >> become a RIPE document. >> >> Over to you... > > Got it - will prepare an initial draft. A volunteer is worth 10 pressed men. Give me a shout if you want proof/sanity checking Nigel
- Previous message (by thread): [iot-wg] RIPE document on IoT security solutions
- Next message (by thread): [iot-wg] RIPE document on IoT security solutions
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ iot-wg Archives ]