profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/stpeter/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Peter Saint-Andre stpeter @mozilla Parker, Colorado, USA https://stpeter.im/ Technologist. Philosopher. Musician. Senior Director at Mozilla.

mozilla-extensions/secure-proxy 126

Firefox Private Network Web Extension

mozilla-services/topsites-proxy 7

Proxy server to track Top Sites default tile campaign attribution

stpeter/json-vcard 7

A JSON representation for vCard4

abetterinternet/ppm-specification 6

Design documents and other documentation related to the Prio family of projects

metajack/xmpp-websocket 6

XMPP over WebSocket specification

MonadnockValleyPress/monadnock 6

Public-domain works published by The Monadnock Valley Press

rfc-format/draft-iab-xml2rfc-v3-bis 5

-bis document for the RFC format xml2rfc v3 draft

linuxwolf/xmpp-fed 4

XMPP Federation specifications

stpeter/ismbook 4

Source files for The Ism Book: A Field Guide to Philosophy

emcho/cusax 3

cusax

push eventstpeter/stpeter.github.io

Peter Saint-Andre

commit sha 8b6c2b2bf6a4ba11324211aeb11a31bd75a2f7bc

small correction

view details

push time in 12 hours

push eventstpeter/stpeter.github.io

Peter Saint-Andre

commit sha e91e81643c77898ed5a82f1d637e6020eaea85f3

readings and notes

view details

push time in 12 hours

push eventstpeter/stpeter.github.io

Peter Saint-Andre

commit sha 1440eaab07bbac2d29bec25986294a50fcf3d899

add Aeon and Psyche

view details

push time in 14 hours

push eventintarchboard/program-rfced-future

Peter Saint-Andre

commit sha 5789a52257ac318983f4d67ddaf181eadbac9c8e

proposed text for updating RFC 7841

view details

push time in 15 hours

issue commentintarchboard/program-rfced-future

Contract monitor(s) outside LLC?

Section 4.2 reads:

Periodically, the IETF LLC will evaluate the performance of the RSEA, including a call for confidential input from the community. The IETF LLC will produce a draft performance evaluation for the RSAB (not including the RSEA), which will provide feedback to the IETF LLC.

On list, Joel wrote "If we remove the various text directing that the LLC do x, y and z for evaluations, this can be removed." Since we've removed the various text, I think we're good.

elear

comment created time in 15 hours

push eventstpeter/stpeter.github.io

Peter Saint-Andre

commit sha 94737576f6c6ce9f98769f9bcfb6caf1269b3f82

more readings

view details

push time in 2 days

push eventMonadnockValleyPress/monadnock

Peter Saint-Andre

commit sha f1b9163c2932f3b24b5365395adda50c2c85ecb4

Goethe

view details

push time in 4 days

push eventMonadnockValleyPress/monadnock

Peter Saint-Andre

commit sha 0345707cd271b49ff76ba6caf2babb63cbc09d75

putting files under source control

view details

push time in 4 days

issue commentintarchboard/program-rfced-future

Contract monitor(s) outside LLC?

Version -02 of the I-D has text addressing this point; shall we issue a consensus call?

elear

comment created time in 4 days

issue commentintarchboard/program-rfced-future

Do we need to update any stream boiler plate?

We certainly need to modify (i.e., create) boilerplate for the Editorial Stream. Should we lodge a separate issue for that?

elear

comment created time in 4 days

issue commentintarchboard/program-rfced-future

What is success?

Based on comments from Brian Carpenter, I'm not sure we need to keep this one open: https://mailarchive.ietf.org/arch/msg/rfced-future/h0TOz6z5a4ET2qUGWh6YgWG1jYY/ - he suggests that this issue might be covered by https://github.com/intarchboard/program-rfced-future/issues/31

elear

comment created time in 4 days

push eventintarchboard/program-rfced-future

Peter Saint-Andre

commit sha b800cbc8b10ccc53948f7ce37e03e3394ffdfd0f

more provisional modifications on the way to -03

view details

push time in 4 days

push eventstpeter/stpeter.github.io

Peter Saint-Andre

commit sha cd47e91b986939c0b110ec660f8d110aad045e53

typo

view details

push time in 4 days

push eventintarchboard/program-rfced-future

Peter Saint-Andre

commit sha 61a391a9f53366ed402bbc59a51a1de4c0b7a979

address ISSUE 55

view details

push time in 5 days

issue commentintarchboard/program-rfced-future

Suggestions for ongoing RS[EA] evaluation (Jay Daley)

ACK

Note that we have the same text in §5.1:

The exact relationship is a matter for the IETF LLC and the IETF Executive Director to determine.

Presumably we should make that change in both places?

elear

comment created time in 5 days

pull request commentxsf/xmpp.org

Replaced defunct tracker for Trademark applications.

Trademark applications are so rare these days that I don't think we need a tracker.

guusdk

comment created time in 5 days

push eventMonadnockValleyPress/monadnock

Peter Saint-Andre

commit sha 6a4de27e2c95d7d8ddb26814f78d08cb2b65e641

monetization experiment

view details

push time in 5 days

push eventintarchboard/program-rfced-future

Peter Saint-Andre

commit sha e0c75e47e5524b5377b11985499f28aa4b8f0499

improve traceability

view details

push time in 8 days

push eventintarchboard/program-rfced-future

Peter Saint-Andre

commit sha 896f3f194433fdf0dd2af9cb1f4afdd6f80ea40a

copy edit and consistency check

view details

push time in 8 days

push eventintarchboard/program-rfced-future

Peter Saint-Andre

commit sha a0b7f8b9003fa9bcb80beee43d6d9949929c8d5e

more pre-02 fixes

view details

push time in 8 days

issue commentintarchboard/program-rfced-future

What counts as "community consensus"?

Right, see comment there.

stpeter

comment created time in 8 days

issue commentintarchboard/program-rfced-future

When do the WG chairs call rough consensus and what happens next?

I'll have text on this in the next version. I checked in a few changes to address this and can share it on list:

  1. The RSWG shall then further develop the proposal. Members of the RSAB are expected to participate in discussion relating to such proposals so that they are fully aware of proposals early in the policy definition process and so that any issues or concerns that they have will be raised during the development of the proposals and will not be left until the RSAB review period. The RWSG chairs are also expected to participate as individuals.
  2. At some point, if the RSWG chairs believe there may be rough consensus for the proposal to advance, they will issue a last call for comment within the working group.
  3. After a comment period of suitable length, the RSWG chairs will determine whether rough consensus for the proposal exists (taking their own feedback as individuals into account along with feedback from other participants). If comments have been received and substantial changes have been made, it is expected that additional last calls may be necessary.
elear

comment created time in 8 days

push eventintarchboard/program-rfced-future

Peter Saint-Andre

commit sha 9b7ef65fb0713dbabd7b94bbd05281d0e74fde82

a few changes on the way to -02

view details

push time in 8 days

issue commentintarchboard/program-rfced-future

What counts as "community consensus"?

I think this is covered by Section 3.2.3: https://datatracker.ietf.org/doc/html/draft-iab-rfcefdp-rfced-model-01#section-3.2.3

stpeter

comment created time in 8 days

push eventstpeter/stpeter.github.io

Peter Saint-Andre

commit sha 0d0a446ca0f95c7d7c4590f57b1584774fd9fc2e

tweak

view details

push time in 9 days

push eventstpeter/stpeter.github.io

Peter Saint-Andre

commit sha 1a4d152242468a83f0dfa2d4dbe67d6c39f8f8fd

readings and notes

view details

Peter Saint-Andre

commit sha 7ce304d1cbfcb85058ffad5f28eadcb688e59906

add peras

view details

Peter Saint-Andre

commit sha 9d62c61f150ff3df2a4f70ee5089de0f50bcbe73

typo

view details

Peter Saint-Andre

commit sha 7e5ecc804a48f9d674969377ed6c54a2ef3937b2

typo

view details

Peter Saint-Andre

commit sha 1e2ca91f4fa22933fe97b1f7759626a81749b9df

text tweak

view details

Peter Saint-Andre

commit sha 5c00d5a293a816941eb6866113460cc2b2386533

1678

view details

push time in 9 days

push eventstpeter/stpeter.github.io

Peter Saint-Andre

commit sha 603aafb0d60c749419e94e3f5aae31eed7d8026c

readings and fixes

view details

push time in 9 days

push eventstpeter/stpeter.github.io

Peter Saint-Andre

commit sha 664e4b2daa5d3ce90a3403782b78169f9e87217e

more readings

view details

push time in 10 days

issue commentrichsalz/draft-ietf-uta-rfc6125bis

Make spec work for peer-to-peer not just client-server

The terminology of client and server in RFC 6125 refers to TLS clients and servers, which seems perfectly appropriate. Even in a peer-to-peer architecture, for any given TLS interaction one entity will be the TLS client and one will be the TLS server.

richsalz

comment created time in 11 days