IETF
NFSV4
nfsv4@jabber.ietf.org
Tuesday, July 26, 2022< ^ >
Room Configuration
Room Occupants

GMT+0
[19:00:48] <zulipbot> (Richard Scheffenegger) I'll relay questions posted to chat on the Mic...
[19:02:27] <zulipbot> (Richard Scheffenegger) can remote participants hear us?
[19:02:40] <zulipbot> (Rui Paulo) yes
[19:02:41] <zulipbot> (Benjamin Coddington) Yes!
[19:04:15] <zulipbot> (Benjamin Coddington) Sound is good.. thanks for moving closer.
[19:04:46] <zulipbot> (Rui Paulo) volume is still a bit low IMO
[19:05:38] <zulipbot> (Richard Scheffenegger) let me know
[19:09:58] <zulipbot> (Rui Paulo) volume is great on the floor but not as good on the table
[19:18:20] <zulipbot> (Benjamin Coddington) hmmm
[19:18:52] <zulipbot> (Tom Talpey) In favor
[19:19:36] <zulipbot> (Jeffrey Layton) in favor
[19:20:04] <zulipbot> (Richard Scheffenegger) objections against WG doc on standards track?
[19:20:04] <zulipbot> (Richard Scheffenegger) but i see none..
[19:23:38] <zulipbot> (Benjamin Kaduk) RFC 9266 on Channel Bindings for TLS 1.3 was just published.
[19:32:38] <zulipbot> (Tom Talpey) Why wouldn't transport security be considered a transport matter (i.e. RDMA needs to implement it)?
[19:33:17] <zulipbot> (Richard Scheffenegger) @Tom want me to echo this? or go yourself into the queue?
[19:33:30] <zulipbot> (Tom Talpey) I can queue
[19:49:37] <zulipbot> (Chuck Lever) I asked about allowing expiry because these are already WG docs rather than personal drafts
[19:52:25] <zulipbot> (Jeffrey Layton) which document is it?
[19:53:38] <zulipbot> (Chuck Lever) Rpcrdma-version-two and nfs-ulb-v2
[19:54:32] <zulipbot> (Tom Talpey) Chuck, it's my understanding that WG documents do not expire, they remain until the WG moves them forward or drops all work on them. So if these are all WG docs, we simply note that work is suspended.
[19:54:45] <zulipbot> (Benjamin Kaduk) WG documents do still expire.
They will disappear from the main "documents" view on the WG webpage.
[19:55:12] <zulipbot> (Tom Talpey) Individual docs can expire and be reanimated at any time by the individual author(s) publishing an update.
[19:55:12] <zulipbot> (Benjamin Kaduk) You can use the datatracker to change the WG state to something like "dead" or "parked" to indicate this was a deliberate change.
[19:55:25] <zulipbot> (Tom Talpey) I like "parked" in that case
[19:56:48] <zulipbot> (Tom Talpey) Ben, what triggers a WG to expire, if not actually set to that state? Inaction for how many months?
[19:57:01] <zulipbot> (Benjamin Kaduk) A WG draft expires after 6 months, the same as an individual draft.
[19:57:14] <zulipbot> (Tom Talpey) Ok I stand clued. Thanks
[19:59:49] <zulipbot> (Benjamin Kaduk) E.g., if I go to https://datatracker.ietf.org/doc/ and use the advanced search options to limit to just **Expired** I-Ds that are from the nfsv4 WG, I get some 26 results.  Many of them are 15+ years old, but draft-ietf-nfsv4-internationalization-01 is pretty recent.
[20:00:43] <zulipbot> (Benjamin Kaduk) I'll also note that, because -internationalization is expired, it does not appear on the listing at https://datatracker.ietf.org/wg/nfsv4/documents/ and the I-D search for expired drafts is the only way I know of to discover it, if you didn't already know about it.
[20:16:39] <zulipbot> (Benjamin Kaduk) I'm listening to two streams at once, so I can't tell if that was beepee or David asking Zahed to identify himself, but I appreciate it.
[20:36:31] <zulipbot> (Benjamin Kaduk) OpenSSL recently discovered the Turkish 'i' topic, due to an (IMHO) misguided use of case-insensitive string comparison and some bugs that resulted in re-running the lookups thousands of times, such that strcasecmp() showed up near the top of the performance traces.
[20:53:31] <zulipbot> (Benjamin Coddington) Thank you