[P4-design] Possibility of making P4 spec repository public?

Anirudh Sivaraman anirudh at csail.mit.edu
Mon Jan 9 09:23:50 EST 2017


On Sun, Jan 8, 2017 at 2:12 PM, Changhoon Kim
<chang at barefootnetworks.com> wrote:
> Hi Anirudh,
>
> Thanks for the reminder. As people started to come back to work after the
> holidays, the board members and the WG chairs have just started discussions
> on a spec-maintenance process, which include whether and how to make p4-spec
> public. The feedback on this mailing list so far has been useful in that
> regard.
>
> Once we have a draft proposal, we'll discuss it within p4-design and seek
> approval. I believe the board members might want to review a few other
> issues as well, including the roadmap for each WG for this year.
>
> -- Chang
>

Thanks for the update on this!

Anirudh

> On Sun, Jan 8, 2017 at 6:12 AM, Anirudh Sivaraman <anirudh at csail.mit.edu>
> wrote:
>>
>> I wanted to bump up this thread because I sent this out during the
>> break, when many people on the mailing list may not have seen it.
>>
>> Anirudh
>>
>>
>> On Thu, Dec 22, 2016 at 2:55 PM, Jennifer Rexford <jrex at cs.princeton.edu>
>> wrote:
>> > totally agree…
>> >
>> > On Dec 22, 2016, at 12:28 PM, Nick McKeown <nickm at stanford.edu> wrote:
>> >
>> > makes sense to me....
>> >
>> > On 12/22/16 7:24 AM, Nate Foster wrote:
>> >
>> > +1
>> >
>> > On Thu, Dec 22, 2016 at 8:06 AM, Ben Pfaff <bpfaff at vmware.com> wrote:
>> >>
>> >> I'm in favor of this (I doubt this surprises anyone).
>> >>
>> >> ________________________________
>> >> From: P4-design <p4-design-bounces at lists.p4.org> on behalf of Anirudh
>> >> Sivaraman <anirudh at csail.mit.edu>
>> >> Sent: Thursday, December 22, 2016 7:40:22 AM
>> >> To: p4-design at lists.p4.org
>> >> Subject: [P4-design] Possibility of making P4 spec repository public?
>> >>
>> >> Now that P4_16 is out in the wild, I wanted to float the idea of
>> >> making the P4 spec repository publicly readable, with write access
>> >> limited to a few maintainers. I wonder what people think of this.
>> >> Given that the P4_16 compiler itself is public, we only stand to
>> >> benefit if there are more eyes on the spec, especially for small bug
>> >> fixes. For larger changes like a new language feature, as Mihai
>> >> suggested many weeks ago, we could have people change the spec, modify
>> >> the compiler to support the spec change, and then use both to make a
>> >> stronger case for the new language feature.
>> >>
>> >> Anirudh
>> >>
>> >> _______________________________________________
>> >> P4-design mailing list
>> >> P4-design at lists.p4.org
>> >>
>> >>
>> >> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.p4.org_mailman_listinfo_p4-2Ddesign-5Flists.p4.org&d=DgICAg&c=uilaK90D4TOVoH58JNXRgQ&r=ddEKXJXvRqA0_bUMvEuj2TB41DoP73cXR3aaYos3gFM&m=RKxUVR5oylK76NVkZZhyg54pewbMW-SevKOcgen_1cY&s=sIIWXms5AC_NrvyKRmC2fU7eUL57n6nbktbM-CblVHQ&e=
>> >>
>> >>
>> >> _______________________________________________
>> >> P4-design mailing list
>> >> P4-design at lists.p4.org
>> >> http://lists.p4.org/mailman/listinfo/p4-design_lists.p4.org
>> >>
>> >>
>> >
>> >
>> >
>> > _______________________________________________
>> > P4-design mailing list
>> > P4-design at lists.p4.org
>> > http://lists.p4.org/mailman/listinfo/p4-design_lists.p4.org
>> >
>> >
>> > _______________________________________________
>> > P4-design mailing list
>> > P4-design at lists.p4.org
>> > http://lists.p4.org/mailman/listinfo/p4-design_lists.p4.org
>> >
>> >
>> >
>> > _______________________________________________
>> > P4-design mailing list
>> > P4-design at lists.p4.org
>> > http://lists.p4.org/mailman/listinfo/p4-design_lists.p4.org
>> >
>> >
>>
>> _______________________________________________
>> P4-design mailing list
>> P4-design at lists.p4.org
>> http://lists.p4.org/mailman/listinfo/p4-design_lists.p4.org
>>
>




More information about the P4-design mailing list