That's the thing, JSSE is an add-on encryption component in Java. If the product requires it, you have to register it.
Ideally the product shouldn't require it and make it an optional feature to enable. The latter is just my $0.02 John On May 4, 2016 21:30, "Ted Dunning" <ted.dunn...@gmail.com> wrote: I am pretty dubious that simply building a credential store using standard JSSE requires registration. Same for HTTPS support. On Wed, May 4, 2016 at 6:23 PM, Ted Dunning <ted.dunn...@gmail.com> wrote: > > My guess is that this would fall to me. > > There is considerable analysis to be done to determine whether filing is > required. > > Are you guys documenting the decision points? > > > > On Wed, May 4, 2016 at 4:45 AM, Stian Soiland-Reyes <st...@apache.org> > wrote: > >> On 2 May 2016 at 03:23, Stian Soiland-Reyes <st...@apache.org> wrote: >> >> > Formally - would it need to be the Incubator PMC chair sending the >> > ECCN encryption email? >> >> Could anyone from IPMC (e.g. our mentors) do it, or just Ted Dunning? >> >> -- >> Stian Soiland-Reyes >> Apache Taverna (incubating), Apache Commons RDF (incubating) >> http://orcid.org/0000-0001-9842-9718 >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> >
