IETF
LAMPS
lamps@jabber.ietf.org
Friday, March 23, 2018< ^ >
Jeffpc has set the subject to: LAMPS at IETF-99
Room Configuration
Room Occupants

GMT+0
[11:19:29] metricamerica joins the room
[11:20:18] metricamerica leaves the room
[11:42:39] Yoshiro Yoneya joins the room
[11:42:48] fNthreNt joins the room
[11:45:15] metricamerica joins the room
[11:46:25] Jacob Hoffman-Andrews joins the room
[11:48:04] meetecho joins the room
[11:48:08] Melinda joins the room
[11:48:40] <Melinda> I'll be your jabber scribe today - please preface any comments/questions/etc for the mic with "mic"
[11:48:40] Corey Bonnell joins the room
[11:49:40] Stefan Santesson joins the room
[11:54:24] Jacob Hoffman-Andrews leaves the room
[11:55:13] Jacob Hoffman-Andrews joins the room
[12:11:25] Sean Leonard joins the room
[12:13:42] <Sean Leonard> is it in the ASN.1?
[12:13:47] <Sean Leonard> Mic: Is it in the ASN.1?
[12:13:50] <Sean Leonard> (I'm not defending it)
[12:24:13] <Corey Bonnell> mic: Has there been any discussion on changing the "SHOULD" for querying the authoratative nameserver(s) to a "MUST" in section 6.3?
[12:31:49] <Sean Leonard> Mic: Should the ShakeOutputLen's length requirement be expressed in ASN.1 as a size constraint? And similarly for RSASSA-PSS-params' saltLength, to restrict size to 32 or 64 accordingly?
[12:35:01] <Sean Leonard> Mic: so to be clear, what component(s) enforce the size constraint?
[12:35:42] <Sean Leonard> because it won't be the ASN.1 encoder/decoder
[12:36:16] <Melinda> does that answer your que
[12:36:46] <Sean Leonard> I am more skeptical about disabling variable-length encoding
[12:36:57] <Sean Leonard> but am not adamant about keeping it in (yet)
[12:37:08] <Melinda> I'd probably take that to the mailing list before it gets nailed down
[12:42:24] <Sean Leonard> Mic: probably not necessary
[12:42:27] <Sean Leonard> +1 to EKR
[12:42:39] <Sean Leonard> (to the issue of where to define the salt)
[12:42:44] Satoru Kanno joins the room
[12:42:59] <Melinda> It looks like there's broad agreement on that.
[12:44:04] Jacob Hoffman-Andrews leaves the room
[13:09:24] <Sean Leonard> Mic: digest and a pointer (subject information access)
[13:10:24] <Sean Leonard> like a URI
[13:13:44] <Sean Leonard> I would like to know what the implications are of having multiple public keys with the same certificate subject name and certificate serial number
[13:13:49] <Sean Leonard> (You can mic that)
[13:14:14] <Sean Leonard> because some crypto stacks index public & private keypairs by issuer + serial number. just pointing out additional complication.
[13:14:20] <Sean Leonard> So <-- Mic: prior comment
[13:16:05] <Sean Leonard> <-- see prior comment
[13:16:15] <Sean Leonard> about indexing point
[13:16:55] jyasskin joins the room
[13:21:02] Melinda leaves the room
[13:21:16] Stefan Santesson leaves the room: Disconnected: closed
[13:21:36] meetecho leaves the room
[13:22:19] Corey Bonnell leaves the room
[13:22:19] Satoru Kanno leaves the room
[13:22:19] Sean Leonard leaves the room
[13:22:46] jyasskin leaves the room
[13:23:19] metricamerica leaves the room
[13:32:48] Yoshiro Yoneya leaves the room
[13:49:39] Melinda joins the room
[13:51:20] Melinda leaves the room
[14:48:43] jyasskin joins the room
[15:21:40] Yoshiro Yoneya joins the room
[15:21:52] fNthreNt leaves the room
[15:24:25] Yoshiro Yoneya joins the room
[15:24:48] Yoshiro Yoneya leaves the room
[16:55:52] Yoshiro Yoneya joins the room
[17:06:19] Yoshiro Yoneya leaves the room
[17:16:34] jyasskin leaves the room
[17:30:02] Yoshiro Yoneya joins the room
[17:31:22] Stefan Santesson joins the room
[17:39:49] Yoshiro Yoneya leaves the room
[17:44:59] Yoshiro Yoneya leaves the room
[19:12:31] Stefan Santesson leaves the room: Disconnected: Replaced by new connection
[19:12:31] Stefan Santesson joins the room
[19:16:55] Stefan Santesson leaves the room
[20:00:44] Stefan Santesson joins the room
[22:20:57] Stefan Santesson leaves the room