Subject: [Masque] Weekly github digest (MASQUE Working Group summary)

From: Repository Activity Summary Bot <[email-masked]>
Date: Sun, 16 May 2021 15:25:59 -0700 (PDT)

Issues
------
* ietf-wg-masque/draft-ietf-masque-h3-datagram (+0/-10/💬9)
  8 issues received 9 new comments:
  - #54 Can intermediaries interact with capsules, contexts and context IDs? (1 by vasilvv)
    https://github.com/ietf-wg-masque/draft-ietf-masque-h3-datagram/issues/54 
  - #45 Is the context ID optional? (2 by ianswett, vasilvv)
    https://github.com/ietf-wg-masque/draft-ietf-masque-h3-datagram/issues/45 
  - #34 Why are flow IDs named? (1 by DavidSchinazi)
    https://github.com/ietf-wg-masque/draft-ietf-masque-h3-datagram/issues/34 
  - #33 Allowing a single flow ID to be associated with multiple requests is brittle (1 by DavidSchinazi)
    https://github.com/ietf-wg-masque/draft-ietf-masque-h3-datagram/issues/33 
  - #32 What guarantees are there against re-using flow IDs (1 by DavidSchinazi)
    https://github.com/ietf-wg-masque/draft-ietf-masque-h3-datagram/issues/32 
  - #31 Is it an error to receive a flow ID greater than 10^15-1? (1 by DavidSchinazi)
    https://github.com/ietf-wg-masque/draft-ietf-masque-h3-datagram/issues/31 
  - #30 Flow ID allocation failures (1 by DavidSchinazi)
    https://github.com/ietf-wg-masque/draft-ietf-masque-h3-datagram/issues/30 
  - #24 Datagram Flow Id parameters should be not be names (1 by DavidSchinazi)
    https://github.com/ietf-wg-masque/draft-ietf-masque-h3-datagram/issues/24 

  10 issues closed:
  - Why are flow IDs named? https://github.com/ietf-wg-masque/draft-ietf-masque-h3-datagram/issues/34 
  - Allowing a single flow ID to be associated with multiple requests is brittle https://github.com/ietf-wg-masque/draft-ietf-masque-h3-datagram/issues/33 
  - What guarantees are there against re-using flow IDs https://github.com/ietf-wg-masque/draft-ietf-masque-h3-datagram/issues/32 
  - Is it an error to receive a flow ID greater than 10^15-1? https://github.com/ietf-wg-masque/draft-ietf-masque-h3-datagram/issues/31 
  - Flow ID allocation failures https://github.com/ietf-wg-masque/draft-ietf-masque-h3-datagram/issues/30 
  - Datagram Flow Id parameters should be not be names https://github.com/ietf-wg-masque/draft-ietf-masque-h3-datagram/issues/24 
  - Pick mechanism to register context IDs (header vs message) https://github.com/ietf-wg-masque/draft-ietf-masque-h3-datagram/issues/44 
  - Ability to accept or reject registration of context IDs https://github.com/ietf-wg-masque/draft-ietf-masque-h3-datagram/issues/43 
  - Directionality of flow/context IDs https://github.com/ietf-wg-masque/draft-ietf-masque-h3-datagram/issues/42 
  - 2-layer design https://github.com/ietf-wg-masque/draft-ietf-masque-h3-datagram/issues/41 

* ietf-wg-masque/draft-ietf-masque-ip-proxy-reqs (+0/-1/💬1)
  1 issues received 1 new comments:
  - #30 Is Route Negotiation a requirement? (1 by chris-wood)
    https://github.com/ietf-wg-masque/draft-ietf-masque-ip-proxy-reqs/issues/30 

  1 issues closed:
  - Is Route Negotiation a requirement? https://github.com/ietf-wg-masque/draft-ietf-masque-ip-proxy-reqs/issues/30 

Pull requests
-------------
* ietf-wg-masque/draft-ietf-masque-h3-datagram (+0/-1/💬0)
  1 pull requests merged:
  - Two layer design with CAPSULE
    https://github.com/ietf-wg-masque/draft-ietf-masque-h3-datagram/pull/52 

Repositories tracked by this digest:
-----------------------------------
* https://github.com/ietf-wg-masque/draft-ietf-masque-connect-udp
* https://github.com/ietf-wg-masque/draft-ietf-masque-h3-datagram
* https://github.com/ietf-wg-masque/draft-ietf-masque-ip-proxy-reqs