This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[db-wg] Draft Minutes of the RIPE 52 DB-WG meeting
- Previous message (by thread): AW: AW: [db-wg] Draft Minutes of the RIPE 52 DB-WG meeting
- Next message (by thread): AW: [db-wg] Draft Minutes of the RIPE 52 DB-WG meeting
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Rob Evans
internetplumber at gmail.com
Fri Apr 28 13:05:49 CEST 2006
Hi Winfried, > I would like to hear some technical reasons why we cant change the current > situation. I dont > see them :-( This is a bit of a "holding" answer. In the routing working group, Andrei presented a summary of the discussion on the lists, but there was very little feedback from the floor, or via Jabber, about which direction to move in. As I recall, Joao said he was going to write a summary of the points to consider and put it out to the routing-wg list, where perhaps there can be some more discussion. One of the reasons to approach this with caution is that the current behaviour is as described in RPSS (RFC2725), and we'd like to get a bit more feedback on why those authentication rules were chosen to make a better decision on how to change them. Regards, Rob
- Previous message (by thread): AW: AW: [db-wg] Draft Minutes of the RIPE 52 DB-WG meeting
- Next message (by thread): AW: [db-wg] Draft Minutes of the RIPE 52 DB-WG meeting
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]