GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Notices by Patrick Mevzek (pmevzek@framapiaf.org)

  1. Embed this notice
    Patrick Mevzek (pmevzek@framapiaf.org)'s status on Wednesday, 22-Jan-2025 12:50:56 JST Patrick Mevzek Patrick Mevzek
    in reply to
    • sahilister

    @sahil Depends authoritative on what kind of zones :-) If "critical" and you need 99.9999% reliability, then no. Otherwise, maybe. Theoretically, you need either solid anycast, OR at least 2 separate IP blocks in separate AS in separate datacenters with separate routing (+ ideally different OS and nameservers software). Plus the usual (power source, monitoring, etc.). But to do it at home on some toy zones, absolutely, to learn things!

    In conversation about 4 months ago from framapiaf.org permalink
  2. Embed this notice
    Patrick Mevzek (pmevzek@framapiaf.org)'s status on Friday, 03-Jan-2025 17:12:42 JST Patrick Mevzek Patrick Mevzek
    in reply to
    • sahilister

    @sahil "If I understand correctly, NS for aws.amazon.com is a chain of CNAME(s) to actual NS domain?". No. It tells you `aws.amazon.com` has NO `NS` records, because it is a CNAME, and CNAME can not coexist with anything else. It then tells you the final destination of the CNAME, as there are 2, aka `dr49lng3n1n2s.cloudfront.net.` and then tells you that this name is delegated because it has `NS` records. So `aws.amazon.com` is not delegated (has no NS records), just pointed out externally.

    In conversation about 5 months ago from framapiaf.org permalink

    Attachments

    1. Domain not in remote thumbnail source whitelist: a0.awsstatic.com
      Cloud Computing Services - Amazon Web Services (AWS)
      Amazon Web Services offers reliable, scalable, and inexpensive cloud computing services. Free to join, pay only for what you use.
  3. Embed this notice
    Patrick Mevzek (pmevzek@framapiaf.org)'s status on Thursday, 02-Jan-2025 07:15:48 JST Patrick Mevzek Patrick Mevzek
    in reply to
    • Sindarina, Edge Case Detective
    • Travis Briggs

    @audiodude @sindarina Never invent TLDs. You will get burn and get others burn. If you just need examples, see the `.dev` or `.box` fiasco. News at 11: new gTLD round in 2026, so you can expect new TLDs in 2030 or so, and `.fake`, or any other, can certainly be there, and suddenly all your documentation and setups have a big problem!

    In conversation about 5 months ago from framapiaf.org permalink
  4. Embed this notice
    Patrick Mevzek (pmevzek@framapiaf.org)'s status on Friday, 20-Dec-2024 04:32:00 JST Patrick Mevzek Patrick Mevzek
    in reply to
    • Haelwenn /элвэн/ :triskell:
    • Stéphane Bortzmeyer

    @bortzmeyer @lanodan Générer un UUID, le renvoyer de suite dans la réponse DNS, attendre en tâche de fond la réponse du service distant, et après la rendre accessible via requêtes DNS sur un enregistrement nommé par cet UUID?

    In conversation about 5 months ago from framapiaf.org permalink
  5. Embed this notice
    Patrick Mevzek (pmevzek@framapiaf.org)'s status on Friday, 20-Dec-2024 04:31:57 JST Patrick Mevzek Patrick Mevzek
    in reply to
    • Haelwenn /элвэн/ :triskell:
    • Stéphane Bortzmeyer

    @bortzmeyer @lanodan Plus vicieux et pas nécessairement efficace dans tous les cas: en guise de première réponse attendre "un peu" et retourner un CNAME, qui pointe vers nouvel enregistrement pour lequel on attend "un peu" et on retourne un CNAME, etc. jusqu'à ce que séparément on ait récupéré la réponse et alors on peut arrêter le chaîne de CNAME. Mais un client peut se lasser avant, par expiration du temps total entre toutes les requêtes ou du nombre de CNAME. L''état peut être encodé.

    In conversation about 5 months ago from framapiaf.org permalink
  6. Embed this notice
    Patrick Mevzek (pmevzek@framapiaf.org)'s status on Friday, 27-Sep-2024 06:48:54 JST Patrick Mevzek Patrick Mevzek
    in reply to
    • feld

    @feld "And does this mean we can blame ICANN for causing our domain prices to keep increasing?" "ICANN tax" of $0.18 in gTLD hasn't changed. And prices go up in ccTLDs as well I think (who can give $0 to ICANN), so… I don't think most registries could explain their prices go up only because of ICANN. Which doesn't mean it is necessarily a good idea for a "regulator" to manage multi hundreds millions of dollars without maybe the needed oversight.

    In conversation about 8 months ago from framapiaf.org permalink
  7. Embed this notice
    Patrick Mevzek (pmevzek@framapiaf.org)'s status on Friday, 27-Sep-2024 05:01:41 JST Patrick Mevzek Patrick Mevzek
    in reply to
    • feld

    @feld ICANN has lots of constituencies/stakeholders (registries, registrars, LEA, IP, etc.) but barely registrants and even less software developers or open source ones. Aka: that specific funding will never happen.

    In conversation about 8 months ago from framapiaf.org permalink
  8. Embed this notice
    Patrick Mevzek (pmevzek@framapiaf.org)'s status on Friday, 27-Sep-2024 04:46:05 JST Patrick Mevzek Patrick Mevzek
    in reply to
    • feld

    @feld Their PR: https://www.icann.org/en/blogs/details/icann-sets-expected-evaluation-fee-for-new-gtld-applications-in-the-next-round-25-09-2024-en#main ; Fee is said to be "just" to cover the cost to be revenue-neutral (seems in domain names there are no economy at scale… as more gTLDs are expected at this round than previous). As for previous money (gTLDs auctions, etc.) not used a decade after, there is a grant program to see how to dispose of $217 millions :-) https://domainincite.com/29692-icann-opens-217-million-grant-program

    In conversation about 8 months ago from framapiaf.org permalink

    Attachments


    1. Invalid filename.
    2. Domain not in remote thumbnail source whitelist: domainincite.com
      ICANN opens $217 million Grant Program
      from Kevin Murphy
      Ten million bucks of ICANN's money is up for grabs, starting today. The Org has opened the application window for the first stage of its Grant Program, which it hopes to eventually see hand out over the $217 million that it raised auctioning off contested gTLDs during the 2012 new gTLD program application round. In
  9. Embed this notice
    Patrick Mevzek (pmevzek@framapiaf.org)'s status on Friday, 27-Sep-2024 00:29:51 JST Patrick Mevzek Patrick Mevzek

    ICANN: "I'm happy to report that the Internet Corporation for Assigned Names and Numbers (ICANN) has set the expected evaluation fee for the next round of new generic top-level domain (gTLD) applications. The expected fee will be USD $227,000."

    In conversation about 8 months ago from framapiaf.org permalink
  10. Embed this notice
    Patrick Mevzek (pmevzek@framapiaf.org)'s status on Thursday, 21-Mar-2024 06:43:22 JST Patrick Mevzek Patrick Mevzek
    in reply to
    • Stéphane Bortzmeyer

    @bortzmeyer Contacts can be sent through EPP, but publicly redacted by registry so not appearing through (public) RDAP as they were through EPP.

    In conversation about a year ago from framapiaf.org permalink
  11. Embed this notice
    Patrick Mevzek (pmevzek@framapiaf.org)'s status on Thursday, 21-Mar-2024 06:43:19 JST Patrick Mevzek Patrick Mevzek
    in reply to
    • Stéphane Bortzmeyer

    @bortzmeyer It is already dubious, if it appears (and is authoritative there) in DNS, why it has to be in RDAP, as this seems to have more drawbacks (DNS and RDS have no reason to be publishing updates synchronously and at same frequency) than benefits. I doubt the TTL extension will be offered by lots of registries (probably none I would bet - there are already parts of secDNS extension about signature lifetimes NOT offered by any registry), so the point will be mostly solved that way.

    In conversation about a year ago from framapiaf.org permalink
  12. Embed this notice
    Patrick Mevzek (pmevzek@framapiaf.org)'s status on Tuesday, 20-Feb-2024 01:34:22 JST Patrick Mevzek Patrick Mevzek
    in reply to
    • Stéphane Bortzmeyer
    • John Shaft

    @shaft @bortzmeyer Aka `pass` en Python ou `...` en Perl?

    In conversation about a year ago from framapiaf.org permalink
  13. Embed this notice
    Patrick Mevzek (pmevzek@framapiaf.org)'s status on Tuesday, 13-Feb-2024 03:48:42 JST Patrick Mevzek Patrick Mevzek
    in reply to
    • sebsauvage

    @sebsauvage Je pense que ca rentre dans le cas du contrat trop long que personne ne lit (qui déposant un nom en `.ai` a lu le point 12 de http://whois.ai/faq.html précisément et en particulier le sous-point 10.4?), couplé au fait que le fonctionnement (ici sur les aspects gouvernance plus que technique) du DNS est très peu connu (et brouillé par du marketing "discutable"), d'où les régulières "surprises"/(re)découvertes comme ".me" est le Monténegro, ou ".tv" les îles Tuvalu…

    In conversation about a year ago from framapiaf.org permalink

    Attachments

    1. No result found on File_thumbnail lookup.
      http://whois.ai/faq.html
  14. Embed this notice
    Patrick Mevzek (pmevzek@framapiaf.org)'s status on Monday, 23-Oct-2023 16:47:47 JST Patrick Mevzek Patrick Mevzek
    in reply to
    • Stéphane Bortzmeyer
    • Framasoft
    • John Shaft

    @shaft @bortzmeyer @Framasoft ... quand la décision sort de l'équipe marketing, et qu'après elle arrive dans l'équipe technique qui doit alors, étrangement, elle, faire un bilan coût/bénéfice et justifier les dépenses à sa hiérarchie. Il y a des modes. Par le passé tout le monde voulait son serveur racine. Puis on a entretenu l'idée que ca serait pas mal que tout le monde ait son TLD, etc.

    In conversation Monday, 23-Oct-2023 16:47:47 JST from framapiaf.org permalink
  15. Embed this notice
    Patrick Mevzek (pmevzek@framapiaf.org)'s status on Thursday, 05-Oct-2023 04:03:28 JST Patrick Mevzek Patrick Mevzek
    in reply to
    • John Shaft

    @shaft Et c'est débile dans les deux cas, mais ca découle de ce positionnement incorrect de dire "secure DNS = DOH". Alors que pour avoir ECH correctement, il faut DNSSEC, sinon c'est contournable. Les états et gestionnaires de réseau ne vont pas se priver de filtrer ces enregistrements DNS et personne ne verra l'attaque par repli... vu que la majorité des domaines n'utilise pas DNSSEC.

    In conversation Thursday, 05-Oct-2023 04:03:28 JST from framapiaf.org permalink
  16. Embed this notice
    Patrick Mevzek (pmevzek@framapiaf.org)'s status on Tuesday, 26-Sep-2023 01:59:53 JST Patrick Mevzek Patrick Mevzek
    in reply to
    • Stéphane Bortzmeyer
    • John Shaft

    @bortzmeyer @shaft Un train (SNCF) c'est comme un paquet UDP: on a une vague idée quand il part, mais jamais aucune idée de quand il arrive en vrai.

    In conversation Tuesday, 26-Sep-2023 01:59:53 JST from framapiaf.org permalink
  17. Embed this notice
    Patrick Mevzek (pmevzek@framapiaf.org)'s status on Thursday, 21-Sep-2023 02:45:03 JST Patrick Mevzek Patrick Mevzek
    in reply to
    • Haelwenn /элвэн/ :triskell:
    • John Shaft

    @lanodan @shaft This thread might be of interest to you: https://mailarchive.ietf.org/arch/msg/dnsop/3hzGyV9LGnUpw0ncFudWdQ2sZvc/ My understanding of the current trends and global points of view is that after RSA 2048 it is better to focus energy on switching to elliptic curves based algorithms and just shield away from RSA completely. For both reasons on size consequences of what is exchanged as DNS packets, and for fears of strength against quantum computing.

    In conversation Thursday, 21-Sep-2023 02:45:03 JST from framapiaf.org permalink

    Attachments

    1. No result found on File_thumbnail lookup.
      [DNSOP] Whiskey Tango Foxtrot on key lengths...
      Search IETF mail list archives
  18. Embed this notice
    Patrick Mevzek (pmevzek@framapiaf.org)'s status on Saturday, 16-Sep-2023 01:29:55 JST Patrick Mevzek Patrick Mevzek
    in reply to
    • Haelwenn /элвэн/ :triskell:
    • Stéphane Bortzmeyer
    • John Shaft

    @bortzmeyer @shaft @lanodan Page introduction de ietf.org: "All IETF participants are considered volunteers and expected to participate as individuals, including those paid to participate."

    In conversation Saturday, 16-Sep-2023 01:29:55 JST from framapiaf.org permalink

    Attachments

    1. Domain not in remote thumbnail source whitelist: www.ietf.org
      Home
  19. Embed this notice
    Patrick Mevzek (pmevzek@framapiaf.org)'s status on Saturday, 16-Sep-2023 01:27:14 JST Patrick Mevzek Patrick Mevzek
    in reply to
    • Haelwenn /элвэн/ :triskell:
    • John Shaft

    @shaft @lanodan C'est touchy les TLDs... Techniquement sous giron IETF, géré en pratique par l'IANA qui reçoit demandes de l'IETF pour maintenir des registres mais qui aussi donne son avis (review) sur les RFCs, et l'ICANN pour la gouvernance, qui fait officier le service IANA par PTI, filiale de l'ICANN. Il falloir que l'ICANN mette à jour son guide pour le round 2026(?) et explicitement lister le `.alt` comme hors limites. Etc.

    In conversation Saturday, 16-Sep-2023 01:27:14 JST from framapiaf.org permalink
  20. Embed this notice
    Patrick Mevzek (pmevzek@framapiaf.org)'s status on Saturday, 16-Sep-2023 01:27:11 JST Patrick Mevzek Patrick Mevzek
    in reply to
    • Haelwenn /элвэн/ :triskell:
    • John Shaft

    @shaft @lanodan "1 personne = 1 voix" à l'IETF est un mythe à ranger dans la même boiîte que "les startups qui naissent dans un garage avec 2 écus et une miche de pain pour voir 1 milliard 2 ans après". Ca semble superficiellement vrai, mais ne tient pas une analyse approfondie. Pour QUIC, ca a aidé "un peu" que ca vienne de Google :-)

    In conversation Saturday, 16-Sep-2023 01:27:11 JST from framapiaf.org permalink
  • Before

User actions

    Patrick Mevzek

    Patrick Mevzek

    "Do not go gentle into that good night."Flying in registration and resolution planes since 1997.

    Tags
    • (None)

    Following 0

      Followers 0

        Groups 0

          Statistics

          User ID
          93671
          Member since
          1 Feb 2023
          Notices
          23
          Daily average
          0

          Feeds

          • Atom
          • Help
          • About
          • FAQ
          • TOS
          • Privacy
          • Source
          • Version
          • Contact

          GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

          Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.