Skip to content
This repository has been archived by the owner on Aug 1, 2020. It is now read-only.

Details Required Around Traditional PEP Capabilities Specifically Certificate Consensus #13

Open
jb354m opened this issue Feb 6, 2020 · 0 comments
Open

Details Required Around Traditional PEP Capabilities Specifically Certificate Consensus #13

jb354m opened this issue Feb 6, 2020 · 0 comments

Comments

@jb354m
Copy link

jb354m commented Feb 6, 2020

I am working on a project around the next generation of a TIC for AT&T. We need more details around the traditional PEP Capabilities, including Certificate Consensus. I appreciate any more details in helping us better understand the capabilities.
g-hsu added a commit that referenced this issue Feb 7, 2020
@g-hsu
Closing RFC period
3a2917f 
closing issues #15 #14 #13 #12 #11 #10 #9 #8 #7 #6 #5 for adjudication
g-hsu added a commit that referenced this issue Feb 10, 2020
@g-hsu
Closing RFC period
bda9a3a 
closes #18 #15 #14 #13 #12 #11 #10 #9 #8 #7 #6 #5 and reverts #17
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jb354m