[{"author": "Suresh Krishnan", "text": "

:+1:\ud83c\udffc\ud83d\udc4d\ud83c\udffc

", "time": "2023-07-24T20:10:49Z"}, {"author": "Max Hawkins", "text": "

Where should I put the notes I am taking?

", "time": "2023-07-24T20:14:19Z"}, {"author": "Michael Richardson", "text": "

the note taking hedgemd.

", "time": "2023-07-24T20:14:32Z"}, {"author": "Michael Richardson", "text": "

Fourth button from the left.

", "time": "2023-07-24T20:14:41Z"}, {"author": "Michael Richardson", "text": "

https://notes.ietf.org/notes-ietf-117-bpf

", "time": "2023-07-24T20:14:53Z"}, {"author": "Adam Wiethuechter", "text": "

Does IETF/IESG want to host a public github/gitlab instance that is connected via our datatracker accounts?

", "time": "2023-07-24T20:26:19Z"}, {"author": "Adam Wiethuechter", "text": "

I feel that using Github is a meta issue in general, where would that be raised?

", "time": "2023-07-24T20:27:04Z"}, {"author": "Christoph Hellwig", "text": "

I think a bug tracker and hosting tied to datatracker would be very useful. No idea where it would be raised, though.

", "time": "2023-07-24T20:40:20Z"}, {"author": "Michael Richardson", "text": "

I'm told that the IETF LLC already has a commercial gitlab license. I'd like to see that used more.

", "time": "2023-07-24T20:40:31Z"}, {"author": "Anthony Somerset", "text": "

if we referencing anything in the kernel repo - i think its important we reference specific commits/tags rather than the file alone

", "time": "2023-07-24T20:40:33Z"}, {"author": "Christoph Hellwig", "text": "

I don't think we should ever reference the kernel repository from ietf documents

", "time": "2023-07-24T20:40:58Z"}, {"author": "Michael Richardson", "text": "

IANA's registry is not an IETF \"document\", so we could easily point there initially, and later on, to an RFC.

", "time": "2023-07-24T20:42:03Z"}, {"author": "Anthony Somerset", "text": "

Christoph Hellwig said:

\n
\n

I think a bug tracker and hosting tied to datatracker would be very useful. No idea where it would be raised, though.

\n
\n

something as simple as Redmine or equivalent would be great for plain issue tracking

\n

but i would concur with a GitLab instance to allow for code hosting options - also makes for easier governance to manage things like WG's etc - i mean side note - can any random person create an ietf-wg org on github?

", "time": "2023-07-24T20:42:23Z"}, {"author": "Behcet Sarikaya", "text": "

@MCR Maybe that's how Github makes money

", "time": "2023-07-24T20:44:35Z"}, {"author": "Michael Richardson", "text": "

@Anthony Somerset , sure, any random person can register an organization named ietf-wg-foobar. It would be a discourteous thing to do, when you (the WG chairs) ask the secretariat to create one, then they set themselves as admins, and arrange to do backups of the organization.

", "time": "2023-07-24T20:47:33Z"}, {"author": "Anthony Somerset", "text": "

yes thats the potential governance meta issue that exists with github :) that could in theory be \"fixed\" when using gitlab

", "time": "2023-07-24T20:48:20Z"}, {"author": "Amanda Baber", "text": "

A note about early allocation (ignore if irrelevant!) - https://datatracker.ietf.org/doc/html/rfc7120 sets out a procedure for getting \"early allocation\" codepoints (which will be marked \"TEMPORARY,\" but can be renewed until document approval). This policy is available only when the registry requires RFC publication (RFC Required, IETF Review, or Standards Action; can be Specification Required). FCFS and Expert Review registrations can be made early (subject to expert approval in the latter case), but are permanent. (Exception: isis wg's RFC 7370 specifically allows RFC 7120-style temporary/renewable early assignment in their Expert Review registries.)

", "time": "2023-07-24T20:51:03Z"}, {"author": "Anthony Somerset", "text": "

agree option 2 looks cleaner

", "time": "2023-07-24T21:09:12Z"}, {"author": "Daniam Henriques", "text": "

Agreed

", "time": "2023-07-24T21:10:17Z"}, {"author": "Amanda Baber", "text": "

Speaking for IANA, we're OK with Option 1 (looks OK on Github, if I understand correctly) or Option 2. With 1, if you want some kind of sorting beyond the first column, that should be specified in the document. For Option 2, the registry/many subregistries model, the document would need to be clear about what the registration procedure(s) would be for any subregistries created in the future. (If it takes an RFC to make a registration in the main registry, the subregistry registration procedure can be left up to that RFC if you want. If a subregistry can be created for an Expert Review codepoint, we need to know the registration procedure in advance.)

", "time": "2023-07-24T21:20:37Z"}, {"author": "Max Hawkins", "text": "

Can someone else take over writing notes? I have to step out.

", "time": "2023-07-24T21:27:07Z"}, {"author": "Suresh Krishnan", "text": "

@meetecho

", "time": "2023-07-24T21:38:15Z"}, {"author": "Suresh Krishnan", "text": "

Cannot see a slideset

", "time": "2023-07-24T21:38:22Z"}, {"author": "Behcet Sarikaya", "text": "

David Vernet: Focus is on ISA for now, but no reason not to start this, what is ISA?

", "time": "2023-07-24T21:38:43Z"}, {"author": "Lorenzo Miniero", "text": "

Was it uploaded after the session started?

", "time": "2023-07-24T21:38:44Z"}, {"author": "Lorenzo Miniero", "text": "

We just imported a 5th deck, can you let us know if it's the one you were looking for?

", "time": "2023-07-24T21:39:32Z"}, {"author": "Suresh Krishnan", "text": "

Yes. That was it Lorenzo

", "time": "2023-07-24T21:39:50Z"}, {"author": "Suresh Krishnan", "text": "

Thank you!

", "time": "2023-07-24T21:39:53Z"}, {"author": "Suresh Krishnan", "text": "

We found an alternate path to share from chair computer

", "time": "2023-07-24T21:40:03Z"}, {"author": "Lorenzo Miniero", "text": "

Ack!

", "time": "2023-07-24T21:40:11Z"}, {"author": "Christoph Hellwig", "text": "

ISA stands for Instruction Set Architecture

", "time": "2023-07-24T21:41:06Z"}, {"author": "Suresh Krishnan", "text": "

@behcet: this is the document we were talking about https://datatracker.ietf.org/doc/draft-thaler-bpf-isa/

", "time": "2023-07-24T21:42:01Z"}, {"author": "Behcet Sarikaya", "text": "

@Suresh Krishnan Thx

", "time": "2023-07-24T21:42:47Z"}, {"author": "David Black", "text": "

Sounds like there's confidence that there's no \"running code\" use of ELF \"machine\" value 247 for anything other than BPF \"out there\", is that correct?

", "time": "2023-07-24T21:46:27Z"}, {"author": "Christoph Hellwig", "text": "

I think it was formally registered, with the caveat of the ELF psABI registration beeing pretty information for a formal registry. I need to look at my noted because we did some research on that for the BOF.

", "time": "2023-07-24T21:52:53Z"}, {"author": "Christoph Hellwig", "text": "

The odd information way of the ELF psABI machine magic number registrations is a really good argument for why we should go with an IANA registry BTW - life would have been much simpler if the ELF psABI code points were managed by IANA..

", "time": "2023-07-24T21:53:44Z"}, {"author": "Benson Muite", "text": "

Thanks

", "time": "2023-07-24T22:03:14Z"}]